Error message

  • Warning: Undefined array key 2 in t18v3z5_preprocess_node() (line 138 of /var/www/html/docroot/sites/all/themes/t18v3z5/template.php).
  • Warning: Undefined array key 2 in t18v3z5_preprocess_node() (line 138 of /var/www/html/docroot/sites/all/themes/t18v3z5/template.php).
  • Deprecated function: Return type of Aws\HandlerList::count() should either be compatible with Countable::count(): int, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in include() (line 32 of /var/www/html/vendor/aws/aws-sdk-php/src/HandlerList.php).
  • Deprecated function: Return type of Aws\Api\AbstractModel::offsetExists($offset) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in include() (line 7 of /var/www/html/vendor/aws/aws-sdk-php/src/Api/AbstractModel.php).
  • Deprecated function: Return type of Aws\Api\AbstractModel::offsetGet($offset) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in include() (line 7 of /var/www/html/vendor/aws/aws-sdk-php/src/Api/AbstractModel.php).
  • Deprecated function: Return type of Aws\Api\AbstractModel::offsetSet($offset, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in include() (line 7 of /var/www/html/vendor/aws/aws-sdk-php/src/Api/AbstractModel.php).
  • Deprecated function: Return type of Aws\Api\AbstractModel::offsetUnset($offset) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in include() (line 7 of /var/www/html/vendor/aws/aws-sdk-php/src/Api/AbstractModel.php).
  • Deprecated function: Return type of Aws\Endpoint\Partition::offsetExists($offset) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in include() (line 13 of /var/www/html/vendor/aws/aws-sdk-php/src/Endpoint/Partition.php).
  • Deprecated function: Return type of & Aws\Endpoint\Partition::offsetGet($offset) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in include() (line 13 of /var/www/html/vendor/aws/aws-sdk-php/src/Endpoint/Partition.php).
  • Deprecated function: Return type of Aws\Endpoint\Partition::offsetSet($offset, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in include() (line 13 of /var/www/html/vendor/aws/aws-sdk-php/src/Endpoint/Partition.php).
  • Deprecated function: Return type of Aws\Endpoint\Partition::offsetUnset($offset) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in include() (line 13 of /var/www/html/vendor/aws/aws-sdk-php/src/Endpoint/Partition.php).
  • Deprecated function: Aws\Credentials\Credentials implements the Serializable interface, which is deprecated. Implement __serialize() and __unserialize() instead (or in addition, if support for old PHP versions is necessary) in include() (line 8 of /var/www/html/vendor/aws/aws-sdk-php/src/Credentials/Credentials.php).
  • Deprecated function: Return type of Aws\Command::offsetExists($offset) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in include() (line 7 of /var/www/html/vendor/aws/aws-sdk-php/src/Command.php).
  • Deprecated function: Return type of & Aws\Command::offsetGet($offset) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in include() (line 7 of /var/www/html/vendor/aws/aws-sdk-php/src/Command.php).
  • Deprecated function: Return type of Aws\Command::offsetSet($offset, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in include() (line 7 of /var/www/html/vendor/aws/aws-sdk-php/src/Command.php).
  • Deprecated function: Return type of Aws\Command::offsetUnset($offset) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in include() (line 7 of /var/www/html/vendor/aws/aws-sdk-php/src/Command.php).
  • Deprecated function: Return type of Aws\Command::count() should either be compatible with Countable::count(): int, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in include() (line 7 of /var/www/html/vendor/aws/aws-sdk-php/src/Command.php).
  • Deprecated function: Return type of Aws\Command::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in include() (line 7 of /var/www/html/vendor/aws/aws-sdk-php/src/Command.php).
  • Deprecated function: Return type of Aws\Result::offsetExists($offset) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in include() (line 9 of /var/www/html/vendor/aws/aws-sdk-php/src/Result.php).
  • Deprecated function: Return type of & Aws\Result::offsetGet($offset) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in include() (line 9 of /var/www/html/vendor/aws/aws-sdk-php/src/Result.php).
  • Deprecated function: Return type of Aws\Result::offsetSet($offset, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in include() (line 9 of /var/www/html/vendor/aws/aws-sdk-php/src/Result.php).
  • Deprecated function: Return type of Aws\Result::offsetUnset($offset) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in include() (line 9 of /var/www/html/vendor/aws/aws-sdk-php/src/Result.php).
  • Deprecated function: Return type of Aws\Result::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in include() (line 9 of /var/www/html/vendor/aws/aws-sdk-php/src/Result.php).
  • Deprecated function: Return type of Aws\Result::count() should either be compatible with Countable::count(): int, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in include() (line 9 of /var/www/html/vendor/aws/aws-sdk-php/src/Result.php).
  • Warning: Undefined array key "nid" in views_handler_field_term_node_tid->pre_render() (line 98 of /var/www/html/docroot/sites/all/modules/views/modules/taxonomy/views_handler_field_term_node_tid.inc).
  • Warning: Undefined array key "nid" in views_handler_field_term_node_tid->pre_render() (line 98 of /var/www/html/docroot/sites/all/modules/views/modules/taxonomy/views_handler_field_term_node_tid.inc).
×

Entertainment

3 Good Things (And 3 Bad Things) About USMNT’s World Cup Group

No, this isn’t some cruel April Fools’ Day joke. The USMNT World Cup group really is one perhaps the most interesting possible group the Americans could have drawn on Friday. 

The U.S. will play England, Iran and the winner of the European playoff — Ukraine, Scotland or Wales — in the 2022 World Cup starting in November. It’s a fascinating group for many reasons, and one from which I think most USA fans will expect their team to advance. 

Here are three good things — and three bad things — about the USMNT World Cup group from a U.S. perspective.

Three Good Things About USMNT World Cup Group

1. This is a navigable group

Aside from drawing Qatar from Pot 1, I think a lot of Americans were hoping to get England in the group stage. While not the weakest Pot 1 team by ranking (fifth), England doesn’t have a great history of success in the World Cup, only winning once, on home soil. The USMNT is undefeated against England in World Cup play, winning in 1950 and earning a draw in 2010 (finishing first in the group that year). That said, England usually makes it out of the group stage, reached the semifinals four years ago and represents the toughest challenge in the group.

By FIFA ranking, Iran was the second hardest in Pot 3 at No. 21 in the world. But Iran has never gotten past the first round of a World Cup with just two wins and four draws in 15 all-time World Cup matches. But one of those wins came against the U.S. in 1998; the other was in 2018.

The UEFA playoff is a wildcard. Wales, ranked 18th in the world, would make Group B the hardest of all the groups by FIFA ranking. Ukraine (27) and Scotland (39) are not easy draws, but teams the U.S. won’t be afraid of playing. 

2. Group B is next to Group A

While you never want to look too far ahead, it’s worth noting if the USMNT makes it through the group stage it would go up against a team from arguably the weakest group in the tournament. 

Group A includes Qatar, Ecuador, Senegal and the Netherlands. The Dutch will be expected to win the group, and they wouldn’t be an easy Round-of-16 matchup if the U.S. finished second. But the other three teams in that group, if the Americans can win the group or the Dutch stumble, represent a winnable game in the Round of 16.

Compare this to Mexico, which if it can get out of a tough group with Argentina, Poland and Saudi Arabia would likely play France or Denmark. 

3. The geopolitics will make this fun

England and the U.S. have a “special relationship.” Iran and the U.S. have a complicated relationship. England, Scotland and Wales all share a common language with the U.S. Ukraine will be a fan favorite if it qualifies by virtue of what its country has been through following Russia’s horrific invasion. 

No matter how the games finish on the pitch, it’ll be fun and interesting off the pitch. 

One more positive note, without teams based too far east geographically, the matches will be scheduled to start at times that aren’t too early for fans to wake up to watch. 

Three Bad Things About USMNT World Cup Group

1. An early start

In most World Cups, teams don’t mind playing one of the early matches because it gives you more rest for the later rounds. In this World Cup, that’s not necessarily the case.

The USMNT will play the UEFA playoff winner on the opening day of the World Cup. While it means fans won’t have to wait to get into the action, it means the Americans won’t have long to prepare for the tournament. 

Because FIFA shoe-horned a World Cup in Qatar played in November, players will only be released from their teams seven days before the World Cup starts on Nov. 14. That’s not a lot of time to get ready for what will be a challenging opponent regardless of who comes through the UEFA playoff. 

Then again, MLS players who make the roster will be able to join up with the USMNT earlier, as the MLS season ends on Nov. 5. Maybe all of the USMNT players should transfer to MLS and tank in the playoffs to give the U.S. an edge.

2. While navigable, the U.S. could also lose every game in this group

I’ve seen a lot of chatter on social media about how this is an easy group but let me tell you: It is not easy. There are rarely easy groups at the World Cup to begin with, and this is not one.

England always has a top team with many of the world’s best players. Iran went 14-3-1 in World Cup qualifying with a plus-41 goal difference. Wales/Ukraine/Scotland play in the deepest confederation and won’t be afraid of anyone.

It’s quite possible the U.S. fails to win a game at this World Cup. There are no gimmes. 

It could have been much worse, but let’s not fool ourselves into thinking this is a cakewalk. 

3. No Thanksgiving Day game

I was hoping the USMNT would be drawn into Group G or H to give the Americans more time to prepare and, in a rare quirk, a USMNT game on Thanksgiving. I think the U.S. could have set ratings records with an afternoon game on Thanksgiving, a day on which Americans are already conditioned to watch football. Additionally, I think a lot of casual soccer fans will be confused by the USMNT be placed in a group with a team that hasn’t yet been determined. 

That said, a Black Friday game against England is pretty enticing. 

Videos you might like