Error log is filling up in MODX3.0.4 (phph8.1) with the message below. I’ve upgraded from MODX2.8.6. On upgrading all Articles had disappeared (front end and back end) and the only way I could get them back was to change each class_key to Articles\Model\Articles. Everything seems to be working ok but I’m worried that these errors are piling up quickly…
[2024-02-01 19:24:43] (ERROR @ /var/www/vhosts/sitedotcodotuk/httpdocs/core/vendor/xpdo/xpdo/src/xPDO/xPDO.php : 473) Path specified for package articles is not a valid or accessible directory: /var/www/vhosts/sitedotcodot/httpdocs/core/components/articles/model/
Yes Harry that’s correct. I followed the specific instructions for upgrading Articles to a newer version in 2.8 and then then Version 2 in MODX 3. The Articles upgrade hung a few times and I was getting an error…
[2024-02-01 12:07:53] (ERROR @ /var/www/vhosts/mysitedotcodotukk/httpdocs/core/components/articles/model/articles/articlescontainer.class.php : 22) PHP warning: require_once(/var/www/vhosts/mysitedotcodotuk/httpdocs/core/model/modx/modprocessor.class.php): Failed to open stream: No such file or directory
…so I actually uploaded the file modprocessor.class.php to that location and it worked. I’m not sure if that was right or wrong but it is working.
I don’t know. Something seems very wrong with your Articles installation.
The path core/components/articles/model/ shouldn’t exist anymore with version 2.0.0-beta. (In MODX 3 extras (including the current version of the Articles extra), the .../model folder is usually moved to .../src/Model.
Also, in MODX 3, the folder core/model/modx/ should only contain the file modx.class.php. The rest of the MODX classes are now in core/src/Revolution/.
Yep I agree with you. I’m wondering whether to delete the modprocessor.class.php file I uploaded now everything is working. The reason I changed the class_key to Articles/Model/Articles was that when no Articles showed up in the back end or front end, I created a new article and this did show up. I then checked the database and noticed the class_key of the new article was Articles/Model/Articles. I changed the existing articles to that class_key and they showed up fine.
That table contains articles, gallery and collections. It has the same creation date as seen in the extension-packages.cache.php. Am I safe to delete Articles from there? Yes that cache does get recreated clearing core/cache.
Thank you for your help Harry - it’s much appreciated. I think ultimately I need to switch this all from Articles to Collections as although there’s some great work been done to bring Articles up to date, it seems so deeply embedded once it’s installed, it’s likely to have more problems going forward.