After upgrading to ez publish 4.0 problems with URLS

Sunday 27 January 2008 2:17:41 pm

Hi, today I upgraded my system first to from 3.9.2 to 3.10, and then to 4.0.

At first it looked like the system was working correctly, but then I discovered that when I click a link on my interface I get

“Error / kernel (20) Module not found, The requested module 13 could not be found…….”

The Urls are a mixture of node names and node ID
http://www.mydomain.com/magasinet/13/middle-east/afghanistan/experts-urge-regional-cooperation-on-afghanistan

Same problem with my admin interface

When I replace node ID with node name the links does still not work, only urls containing only node ID’s work.

http://www.mydomain.com/magasinet/30

Monday 28 January 2008 3:59:53 am

I ran niceurls again, now the node id is gone from the urls, but one of the nodes names are missing from the urls

Like
http://www.mydomain.com/magasinet/afghanistan/Experts-Urge-Regional-Cooperation-on-Afghanistan

Should be
http://www.mydomain.com/magasinet/news/afghanistan/Experts-Urge-Regional-Cooperation-on-Afghanistan

But If I manually add “news” the URLS will still not work.

I have checked the databases consistency via the admin interface, the result was

To synchronize your database with the distribution setup, run the following SQL commands:

ALTER TABLE ezurl DROP INDEX ezurl_url;
ALTER TABLE ezurl ADD INDEX ezurl_url ( url );
ALTER TABLE ezurlalias_ml DROP INDEX ezurlalias_ml_act_org;
ALTER TABLE ezurlalias_ml ADD INDEX ezurlalias_ml_act_org ( action, is_original );
ALTER TABLE ezurlalias_ml DROP INDEX ezurlalias_ml_action;
ALTER TABLE ezurlalias_ml ADD INDEX ezurlalias_ml_action ( action, id, link );
ALTER TABLE ezurlalias_ml DROP INDEX ezurlalias_ml_par_act_id_lnk;
ALTER TABLE ezurlalias_ml ADD INDEX ezurlalias_ml_par_act_id_lnk ( parent, action, id, link );
ALTER TABLE ezurlalias_ml DROP INDEX ezurlalias_ml_par_lnk_txt;
ALTER TABLE ezurlalias_ml ADD INDEX ezurlalias_ml_par_lnk_txt ( parent, link, text );
ALTER TABLE ezurlalias_ml DROP INDEX ezurlalias_ml_par_txt;
ALTER TABLE ezurlalias_ml ADD INDEX ezurlalias_ml_par_txt ( parent, text );
ALTER TABLE ezurlalias_ml DROP INDEX ezurlalias_ml_text;
ALTER TABLE ezurlalias_ml ADD INDEX ezurlalias_ml_text ( text, id, link );
ALTER TABLE ezurlalias_ml DROP INDEX ezurlalias_ml_text_lang;
ALTER TABLE ezurlalias_ml ADD INDEX ezurlalias_ml_text_lang ( text, lang_mask, parent );

Should I execute these commands via mysqul –u username –p database_name ?

Monday 28 January 2008 4:12:46 am

I execute the commands via mysqul –u username –p database_name, but the following command resulted in this error
ERROR 1170 (42000): BLOB/TEXT column 'action' used in key specification without a key length

ALTER TABLE ezurl ADD INDEX ezurl_url ( url );
ALTER TABLE ezurlalias_ml ADD INDEX ezurlalias_ml_act_org ( action, is_original );
ALTER TABLE ezurlalias_ml ADD INDEX ezurlalias_ml_action ( action, id, link );
ALTER TABLE ezurlalias_ml ADD INDEX ezurlalias_ml_par_act_id_lnk ( parent, action, id, link );
ALTER TABLE ezurlalias_ml ADD INDEX ezurlalias_ml_par_lnk_txt ( parent, link, text );
ALTER TABLE ezurlalias_ml ADD INDEX ezurlalias_ml_par_txt ( parent, text );
ALTER TABLE ezurlalias_ml ADD INDEX ezurlalias_ml_text ( text, id, link );
ALTER TABLE ezurlalias_ml ADD INDEX ezurlalias_ml_text_lang ( text, lang_mask, parent );

I googled "ERROR 1170 (42000): BLOB/TEXT column"

“The solution to the problem is to remove the TEXT or BLOB column from the index or unique constraint, or set another field as primary key. If you can’t do that, and wanting to place a limit on the TEXT or BLOB column, try to use VARCHAR type and place a limit of length on it. By default, VARCHAR is limited to a maximum of 255 characters and its limit must be specified implicitly within a bracket right after its declaration, i.e VARCHAR(200) will limit it to 200 characters long only.” From http://www.mydigitallife.info/2007/07/09/mysql-error-1170-42000-blobtext-column-used-in-key-specification-without-a-key-length/

Please help I am no mysql expert!

Monday 28 January 2008 11:12:46 am

I removed the database and imported my backup dump, then repeated the upgrade instructions skipping the sections with “Multi-language support for URL aliases (optional)”.

Now the website works, but the URLS are “dirty”. And the databases give no error.

So there clearly is a bug in the niceurls script. (not reported?)

As I understand the upgrade to EZ 3.10 destroyed the nice urls, can I upgrade to EZ 4 directly from EZ 3.9.2?

Monday 05 April 2010 6:55:29 pm

Sorry ,I can't understand you ! I follow the instruction of upgading from 3.10.0 to 4.0.0 ,but it is error still of the url

Can you reply clearly ?

Thanks!