Forums / Developer / Renamed main content node (node 2) => system don't work

"Please Note:
  • At the specific request of Ibexa we are changing this projects name to "Exponential" or "Exponential (CMS)" effective as of August, 11th 2025.
  • This project is not associated with the original eZ Publish software or its original developer, eZ Systems or Ibexa".

Renamed main content node (node 2) => system don't work

« 
Previous topic
|
Developer
|
Next topic
 »
Author Message

Atle Pedersen

Thursday 21 December 2006 7:50:09 am

I renamed node 2 to something else than default. And now, whatever system url I'm trying to access (/content/view/... /user/login .. anything), I get the same error message in the log:

Undefined module: name_of_node_2

All I can do is view the content nodes using nice urls. Nothing else works.

Atle Pedersen

Thursday 21 December 2006 9:29:51 am

Sooo.... talking about v3.8.6 in index.php beginning at line 550:

        $translateResult = eZURLAlias::translate( $uri );


        if ( !$translateResult )
        {
            $useWildcardTranslation = $ini->variable( 'URLTranslator', 'WildcardTranslation' ) == 'enabled';
            if ( $useWildcardTranslation )
            {
                $translateResult =& eZURLAlias::translateByWildcard( $uri );
            }
        }

This is were it fails. $translateResult is not set. Then it launches into a wild_card search for the module to load, and loops for the number of times set by the ini setting MaximumWildcardIteration. Each iterations adds the name of node 2 to the beginning of the URL in the $uri object/array. And when done, the URI is messed up.

Sooo....
... except for disabling WildcardTranslation, what can I do to fix this? Is my database broken? If so, can I repair it somehow?

Atle Pedersen

Thursday 21 December 2006 9:55:19 am

Checking the database in table 'ezurlalias' I find this:

mysql> select * from ezurlalias where is_wildcard!=0;
+--------------------+---------------+-----+-------------+-------------+----------------------------------+----------------------+
| destination_url    | forward_to_id | id  | is_internal | is_wildcard | source_md5                       | source_url           |
+--------------------+---------------+-----+-------------+-------------+----------------------------------+----------------------+
| medarbeidere/{1}   |             0 |  71 |           1 |           1 | 0c201dd3d8ed97ed895243a8f5156ec7 | socios_y_asociados/* |
| company_name{1} |             0 | 104 |           1 |           1 | 3389dae361af79b04c9c8e7057f60cc6 | *                    |
| companyname/{1}  |             0 | 106 |           1 |           1 | 038f20fd1f3ac710ce3e2a2bd5cb7772 | company_name/*     |
+--------------------+---------------+-----+-------------+-------------+----------------------------------+----------------------+

The middle one (company_name is node 2) seems to be the the troublemaker. But why are there several wild card url aliases? I have not created any of these manually. Is this a bug? What is the safe way to get rid of these wildcards when they create problems?

Atle