My use case is I want to give the URL for an entity in an email sent by Drupal:

This code:

$entity->toUrl('canonical', ['absolute' => TRUE])->getUri();

causes an exception to be thrown, with the message 'This URL has a Drupal route, so the canonical form is not a URI'.

This code works:

$entity->toUrl('canonical', ['absolute' => TRUE])->toString();

Why can't getURI() call toString() for a routed URL object?

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

joachim created an issue. See original summary.

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.0-beta1 was released on August 3, 2016, which means new developments and disruptive changes should now be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.0-alpha1 will be released the week of January 30, 2017, which means new developments and disruptive changes should now be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.0-alpha1 will be released the week of July 31, 2017, which means new developments and disruptive changes should now be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

geekygnr’s picture

I ran into this problem as well from a Url object that was generated with the Url::fromRoute function.

It looks like the Url::getUri() function is a straight getter function for the variable on the object. I also found a Url::toUriString() function that worked well.

Not sure what the use case is for having these two functions. I would expect the two functions to return the same thing always making them redundant.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.0-alpha1 will be released the week of January 17, 2018, which means new developments and disruptive changes should now be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

ericmulder1980’s picture

I came here after searching for a problem with

Url::fromRoute('route.name')->getUri();

This resulted in the error "This URL has a Drupal route, so the canonical form is not a URI" as stated by the OP.

So when you want to get the Uri (path) for a specific route the code below seems to work.

Url::fromRoute('user.login')->toString();

This returns "/user/login"

‌‌Url::fromRoute('user.login')->getInternalPath();

This returns "user/login"

Why would Url:fromRoute() not use the urlGenerator to create a full Url object?

Kind regards,
Eric Mulder

Version: 8.6.x-dev » 8.7.x-dev

Drupal 8.6.0-alpha1 will be released the week of July 16, 2018, which means new developments and disruptive changes should now be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.7.x-dev » 8.8.x-dev

Drupal 8.7.0-alpha1 will be released the week of March 11, 2019, which means new developments and disruptive changes should now be targeted against the 8.8.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.0-alpha1 will be released the week of October 14th, 2019, which means new developments and disruptive changes should now be targeted against the 8.9.x-dev branch. (Any changes to 8.9.x will also be committed to 9.0.x in preparation for Drupal 9’s release, but some changes like significant feature additions will be deferred to 9.1.x.). For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.9.x-dev » 9.1.x-dev

Drupal 8.9.0-beta1 was released on March 20, 2020. 8.9.x is the final, long-term support (LTS) minor release of Drupal 8, which means new developments and disruptive changes should now be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Blanca.Esqueda’s picture

I'm trying to get the URI schema from an entity.

using: $referenced_entity->toUrl()->getUri();
triggers the error "This URL has a Drupal route, so the canonical form is not a URI".

using: $referenced_entity->toUrl()->toUriString();
returns the route: route:entity.node.canonical;node=16
instead of the uri schema: entity:node/16

I've tried in different ways but it seems like I can not get the URI schema from an entity.

Some help would be appreciated.

Blanca.Esqueda’s picture

As a solution, I propose getUri() to return the URI instead of the error: 'This URL has a Drupal route, so the canonical form is not a URI'

getUri() in https://api.drupal.org/api/drupal/core%21lib%21Drupal%21Core%21Url.php/c...

/**
   * Returns the URI value for this Url object.
   *
   * Only to be used if self::$unrouted is TRUE.
   *
   * @return string
   *   A URI not connected to a route. May be an external URL.
   *
   * @throws \UnexpectedValueException
   *   Thrown when the URI was requested for a routed URL.
   */
  public function getUri() {
    if (!$this->unrouted) {
      throw new \UnexpectedValueException('This URL has a Drupal route, so the canonical form is not a URI.');
    }
    return $this->uri;
  }

would change to something like this:

/**
   * Returns the URI value for this Url object.
   *
   * Only to be used if self::$unrouted is TRUE.
   *
   * @return string
   *   A URI not connected to a route. May be an external URL.
   *
   * @throws \UnexpectedValueException
   *   Thrown when the URI was requested for a routed URL.
   */
  public function getUri() {
    if (!$this->unrouted) {
       // Convert entity URIs to the entity scheme, if the path matches a route
       // of the form "entity.$entity_type_id.canonical".
       // @see \Drupal\Core\Url::fromEntityUri()
       $route_name = $this->getRouteName();
       foreach (array_keys($this->entityTypeManager->getDefinitions()) as $entity_type_id) {
          if ($route_name == "entity.{$entity_type_id}.canonical" && isset($url->getRouteParameters()[$entity_type_id])) {
            $uri = "entity:{$entity_type_id}/" . $url->getRouteParameters()[$entity_type_id];
            return $uri;
          }
       }
    }
    return $this->uri;
  }
Qandeel’s picture

Instead of updated getUri(); I would suggest to have a new public function dealing with this new functionality, I have created a patch for this; drupal core 8.9.2

Version: 9.1.x-dev » 9.2.x-dev

Drupal 9.1.0-alpha1 will be released the week of October 19, 2020, which means new developments and disruptive changes should now be targeted for the 9.2.x-dev branch. For more information see the Drupal 9 minor version schedule and the Allowed changes during the Drupal 9 release cycle.

Version: 9.2.x-dev » 9.3.x-dev

Drupal 9.2.0-alpha1 will be released the week of May 3, 2021, which means new developments and disruptive changes should now be targeted for the 9.3.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.0-rc1 was released on November 26, 2021, which means new developments and disruptive changes should now be targeted for the 9.4.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.0-alpha1 was released on May 6, 2022, which means new developments and disruptive changes should now be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.5.x-dev » 10.1.x-dev

Drupal 9.5.0-beta2 and Drupal 10.0.0-beta2 were released on September 29, 2022, which means new developments and disruptive changes should now be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 10.1.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch, which currently accepts only minor-version allowed changes. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.