#1014 – New bug using SP Simple Portfolio

 Hi, now a new 404 error has appeared in a gallery using SP Simple Portfolio:

[Wed Mar 22 12:46:43.353295 2023] [proxy_fcgi:error] [pid 3951981:tid 140718442055424] [client 88.17.142.177:0] AH01071: Got error 'PHP message: PHP Warning: Attempt to read property "id" on null in /home/xnapaado/public_html/plugins/route66/content/rules/article.php on line 166PHP message: PHP Warning: Attempt to read property "catid" on null in /home/xnapaado/public_html/plugins/route66/content/rules/article.php on line 166PHP message: PHP Warning: Attempt to read property "language" on null in /home/xnapaado/public_html/plugins/route66/content/rules/article.php on line 166', referer: https://www.xn--apaados-6za.es/galeria2

For this component is it necessary to assign a particular rule with Route 66?

La URL is: https://www.xn--apaados-6za.es/galeria2

Hi Jesus,

Route 66 should only affect components that it supports (Joomla articles, K2 items etc).
I just checked the link you provided and it seems to work fine now. Have you resolved the issue?

Regards

It works because I had to go back to version 1.9.7 of Route 66, before the gallery also worked correctly. It's the latest versions that mess everything up.

Are you sure you didn't change anything else?
Route 66 does not change URLs of this component.

If you are completely sure that you didn't change anything else and that Route 66 caused that issue, please create a new private ticket and provide SFTP and administration access to your site so I can troubleshoot this.

Regards

Nothing else was changed. With version 1.9.7 everything worked fine, with the new ones it doesn't work. You have the error generated by Apache with that should be enough. I'm not going to give you access, sorry.

A similar problem has already happened with Route 66 before, the pity is that I cannot do without this component otherwise I would.

Just tested Route 66 1.9.9 and SP Simple Portfolio 2.0.7 under Joomla 4 and everything works fine for me.
Since you are not giving access to your server, there is nothing more I can do. I am closing this issue.
If you change your mind please create a new ticket and let me know.

Regards