Forums / Install & configuration / URL translation affects admin pages

URL translation affects admin pages

« 
Previous topic
|
Install & configuration
|
Next topic
 »
Author Message

Conor Murray

Wednesday 13 July 2005 5:08:14 am

eZ Version: 3.6.0 (3.6.0) SVN revision: 11973

URL translations are affecting the admin site! So if a translation is set up for the user site that happens to collide with a URL for the admin site then the admin site breaks for that URL.

Is there a setting in an ini file that allows me to disable URL translations in the admin site?

Language is a virus - William S Burroughs

Łukasz Serwatka

Friday 22 July 2005 12:55:46 am

Hi,

You can disable url translation in site.ini.append.php file. This looks like a bug, can you report it in bug system? http://ez.no/community/bugs

[URLTranslator]
Translation=disabled

Personal website -> http://serwatka.net
Blog (about eZ Publish) -> http://serwatka.net/blog

Nathan Kelly

Sunday 09 October 2005 11:11:34 pm

Hi I have the same problem on the same version.

When I disable translation as suggested I get an error stating:

The requested page could not be displayed. (20)

The requested address or module could not be found.

Possible reasons:

    * The address was misspelled. Try changing the URL.
    * The name of the module was misspelled. Try changing the URL.
    * There is no <module_name> module available on this site.
    * The site is using URL matching to determine which siteaccess
to use, but the name of the siteaccess is missing from the URL.
Try to add the name of the siteaccess, it should be specified before
the name of the module.

Normaly traslation would not be a problem, but if you have a [folder] with a translation attached it makes it imposable to manage the contents of that folder via admin.

Is this a bug?

Pardon me while I burst into flames...

Nathan Kelly

Sunday 09 October 2005 11:37:34 pm

Hmm, ok I think found a temporary workaround but it's not really acceptable for a site editor that has little knowledge of the system nor is it what I would expect for true URL translation.

If you set up your translation using "System URL forwarding" like this for example:

New virtual URL = /myurl
System URL = /content/view/full/42

Its usually nice to add the /content/view/full/(NodeId) of /myurl to point to the desired node just in case /content/view/full/(NodeId) is typed, for example:

New virtual URL = /content/view/full/(nodeID of myurl)
System URL = /content/view/full/42

However this makes the node completely inaccessible from the admin.

If you don't forward the content view you can still access the node via the admin by clicking on the folder icon for that node and selecting [view] from the dropdown list as this method seems to use the content/view/full/(nodeID) as the URL rather than /myurl.

Like I said for a user with little knowledge it could be tricky and it doesn't provide the added protection on the public site.

Any suggestions? Is this the intended function or a bug?

Pardon me while I burst into flames...