Hi there.
To give the full story, we had 1.7.3 of CMS Made Simple installed and I was tasked with updating the version to match our sister site which was on version 1.10.3.
I read a help page on CMS Made Simple's site stating that it's best to update one main version at a time - so I did. I went from 1.7.3 to 1.8 then to 1.9 then to 1.10 and then I got bold and tried 1.11 (since I was updating, I may as well go to the latest I figured).
I tested the site after each update just to see if the main page loads. I hadn't thought to test the news links.
I had experienced errors when updating to 1.11 (regarding the cms_routes table (which was not created as I had the "create tables" checkbox unchecked because it would wipe out my site, right?) So I tried creating the table manually and it populated somewhat and there was trouble trying to insert a record so I said ok I will just revert back to 1.10 and then upgrade to the latest release of that which was 1.10.3 which is good because now both sites were on the same version of CMS Made Simple which was the original goal.
So now my site was working again.
It was then brought to my attention that the URLs that contained .html were working (it seems that there were changes to the config file that wiped out previous settings regarding the "url_rewriting" and "page_extension" values which were previously "mod_rewrite" and ".html" respectively. It seems now that the "page_extension" setting is now an all or nothing value wherein in the past it was optional? I'm not sure how this works, but just explaining that pages worked with or without the .html previously (least to my recollection - I could be wrong).
So anyway, the values that I have in place now are "mod_rewrite" and "/" to match the sister site's values for consistency. I also put into place in the .htaccess a redirect for any URL that contains .html to strip it out so those links that were not working (because they contained ".html" now were working.
It was brought to my attention today though, that none of the live news articles links were working. I am referring to when I go to the news page which has the list of articles in which each article can be clicked to take you to a detail page. It gives me a 404 error.
Here is how my news page is set up:
<h1>News</h1>
{news category="News" summarytemplate="news" detailtemplate="news"}
I had tried searching through the forums for an answer to my question before posting - I had found several things similar, but nothing quite exact (my apologies if this is already answered elsewhere, but I tried). One thing that I had read was checking the spelling of the category and the templates. I noticed that the category on the page was spelled "news" instead of "News" so I made the n uppercase and that didn't change anything (not sure if it is case sensitive, but was worth a try).
My summary and detail templates are practically identical to the sister site's working templates so I don't think that they are to blame here.
Any insight or information would be greatly appreciated. I am curious if upgrading to 1.11 and downgrading to 1.10 and then upgrading to 1.10.3 had broken something?
The news article links seem to have had ended with ".html" which is how we stumbled upon the articles not working because I was scouring the pages for any html code containing ".html" on an internal link and I was removing it for consistency purposes and I mentioned to a coworker that a link was not working (thinking at first that it was due to the article being expired perhaps, but it was not the case).
If I turn "mod_rewrite" off then the news article links work by the way which is very interesting.
The last thing to note here is that we have a 3rd sister site which was on version 1.7 which I upgraded sequentially as well from 1.8 to 1.9 to 1.10 to 1.10.3 and the news article link there correctly links to a new working page.
Let me know if you need any additional information from me - I will be glad to provide it.
Thank you kindly for your assistance.
Regards,
-Michael
[Solved] 404 Error on News Lnks with Mod_Rewrite On - 1.10.3
[Solved] 404 Error on News Lnks with Mod_Rewrite On - 1.10.3
Last edited by msalgo on Tue Feb 12, 2013 7:27 pm, edited 1 time in total.
Re: 404 Error on News Links with Mod_Rewrite On - 1.10.3
Hi there. Is there any additional information that I should look to share on this topic? I've been looking throughout the forum and Google and have not come upon a solution yet.
Thank you,
-Michael
Thank you,
-Michael
Re: 404 Error on News Links with Mod_Rewrite On - 1.10.3
Since / isn't a page extension it may be messing with it...
Re: 404 Error on News Links with Mod_Rewrite On - 1.10.3
I had read that the '/' page extension was not too cooperative, so I had tried setting it to '' and it still provides the same issue. Just now I commented out the page extension line in the config file and the issue still persists. 

Re: [Solved] 404 Error on News Lnks with Mod_Rewrite On - 1.
Well, the issue is resolved now, not solved, but resolved.
What I did was just delete the site and the database and restore back to the backups of each and then proceeded to upgrade to 1.10.3 and not do the 1.11 upgrade like I did last time and everything works now.
It's unfortunate though that we cannot go to 1.11 or higher hereon in since there were issues migrating to 1.11 in the first place (which is why I had to downgrade to 1.10.3 from 1.11).
Thanks for the help though.
Regards,
-Michael
What I did was just delete the site and the database and restore back to the backups of each and then proceeded to upgrade to 1.10.3 and not do the 1.11 upgrade like I did last time and everything works now.
It's unfortunate though that we cannot go to 1.11 or higher hereon in since there were issues migrating to 1.11 in the first place (which is why I had to downgrade to 1.10.3 from 1.11).
Thanks for the help though.
Regards,
-Michael
Re: [Solved] 404 Error on News Lnks with Mod_Rewrite On - 1.
I've never had a problem with News links but I also use a real page extension with mod_rewrite, not leaving it blank, '', or / ...
Re: [Solved] 404 Error on News Lnks with Mod_Rewrite On - 1.
I had the same problem.
That comes owing to the fact that your tables all are not with the MyIsam format.
cms_routes table is deleted when you update it by the administration.
Here a small code which you can use to transform all the tables into MyIsam.
That should solve your problem.
Discussion in french : http://www.cmsmadesimple.fr/forum/viewt ... 532#p32532
bug : http://dev.cmsmadesimple.org/bug/view/8684
The svn 8523 corrected the problem.
That comes owing to the fact that your tables all are not with the MyIsam format.
cms_routes table is deleted when you update it by the administration.
Here a small code which you can use to transform all the tables into MyIsam.
That should solve your problem.
Code: Select all
<?php
/* */
/* Titre : modifier en masse le type de tables mysql en MyISAM */
/* */
/* Auteur : Jean le Chauve */
/* Date édition : 21 Nov 2012 */
/* */
$sql_serveur = "localhost"; // Serveur mySQL
$sql_base = "11121"; // Base de données mySQL
$sql_login = "root"; // Login de connection à mySQL
$sql_password = ""; // Mot de passe pour mySQL
$lk = @mysql_connect($sql_serveur, $sql_login, $sql_password) OR die(mysql_error
());
@mysql_select_db($sql_base, $lk) OR die(mysql_error());
$q = mysql_query("SHOW TABLES") OR die(
mysql_error());
while (($r = mysql_fetch_row($q)) !== false) {
mysql_query("ALTER TABLE " . $r[0] . " ENGINE = MyISAM", $lk)
OR die(mysql_error());
echo "Table " . $r[0] . "=> changée en MyISAM <br />";
}
?>
bug : http://dev.cmsmadesimple.org/bug/view/8684
The svn 8523 corrected the problem.