My Blog pages quit working after upgrading to 2024.3.1
Auteur : Alvin L.
Visité 297,
Followers 1,
Partagé 0
After upgrading to the latest version 2024.3.1 I tested on one of my blog sites and my blog pages no longer load. Has anyone else experienced this? I am not converting anymore of my sites until I get this straightened out. I made no other changes but upgrade my software and tested updating one of my sites. Here is the error I get:
This page isn’t working right now
www.theredneckramblings.com can't currently handle this request.
HTTP ERROR 500
Posté le
Auteur
I found the error but this needs to be fixed in WebsiteX5. Previous versions allowed you to use the ' symbol in page titles but 2024.3.1 does not. I found these errors in my blog folder error log. Each occurance I was using 's in both the page title and the page tag title. I know I use 's in the titles of other pages, but it only seems to be an issue on the blog index.php page, although I am not updating any of my other sites until I know this is resolved.
[19-Sep-2024 12:20:21 America/Chicago] PHP Parse error: syntax error, unexpected identifier "s", expecting "," or ";" in /home1/alvinl01/theredneckramblings.com/blog/index.php on line 39 [19-Sep-2024 12:22:10 America/Chicago] PHP Parse error: syntax error, unexpected identifier "s", expecting "," or ";" in /home1/alvinl01/theredneckramblings.com/blog/index.php on line 50
Auteur
Just so I am clear about what I did to fix this. I removed the 's from the properties page of my blog/index.php AND from the main index.html and the issue went away. The 's was not an issue loading the page, nor is it an issue in other pages where I am sure the 's exists. But when loading blog/index.php it's an issue.
The same problem here in Italy: https://helpcenter.websitex5.com/fr/post/266865
Auteur
Thanks for the link. I searched and that post did not show up in the results. Glad to know I am not the only one with this issue.
Hello Alvin,
the issue with some character causing Issues in the special page "Blog: Article page" has been reported a few days ago, and the fix will be included in version 2024.3.2, that will be released today in Beta.
Eric