WordPress.org

Ready to get started?Download WordPress

Forums

Custom Content Type Manager
[resolved] Fatal Error on Multiple sites with today's update (18 posts)

  1. desiostudios
    Member
    Posted 12 months ago #

    4 client sites updated plugin today with various hosts all getting

    Fatal error: Class 'FilesystemIterator' not found in /home/content/66/7405366/html/wp-content/plugins/custom-content-type-manager/includes/CCTM_Ajax.php on line 80

    Please help

    http://wordpress.org/plugins/custom-content-type-manager/

  2. oksanaar
    Member
    Posted 12 months ago #

    Same here! Please, have it fixed. Or suggest how I can return to an older version. Thanks!

  3. The Digital Hippies
    Member
    Posted 12 months ago #

    Me too. Arg

    Fatal error: Class 'FilesystemIterator' not found in /home3/public_html/wp-content/plugins/custom-content-type-manager/includes/CCTM_Ajax.php on line 80

  4. Eric McNiece
    Member
    Posted 12 months ago #

    Roll back to 0.9.7.6! Hopefully you have FTP access... I sure didn't, had to get the server tech :S

  5. Eric McNiece
    Member
    Posted 12 months ago #

    Please vote for broken compatibility status on the details page to warn others about this version.

  6. desiostudios
    Member
    Posted 12 months ago #

    OK... replaced plugin with 9.7.6 and all is right with the world again. That's the solution for now. More info here http://code.google.com/p/wordpress-custom-content-type-manager/issues/detail?id=513

  7. The Digital Hippies
    Member
    Posted 12 months ago #

    I was able to fix this TEMPORARLY and hackish. All this will do is restore your website until the dev fixes it.

    Open the file listed in the error: /wp-content/plugins/custom-content-type-manager/includes/CCTM_Ajax.php

    Go to line 80, move everything on line 80 down once by entering a blank line above it.

    On the new blank line 80, add this
    if (class_exists(FilesystemIterator)) {

    Now go to line 91, make a blank line, and on that line, add this }

    You have to do the same thing with the file CCTM.php

    Go to line 819, and make a blank line, and add this
    if (class_exists(FilesystemIterator)) {

    go to line 913, make a blank line, and add this }

    You have to know PHP to do this, but it will get your website back online until the next update.

  8. The Digital Hippies
    Member
    Posted 12 months ago #

    I suggest rolling back rather than doing my code changes. The link to roll back wasn't there when I started my reply.

  9. Eric McNiece
    Member
    Posted 12 months ago #

    Thanks guys for the fast action!

  10. oksanaar
    Member
    Posted 12 months ago #

    I tried deleting the plugin at all, and things still haven't changed.. Re-uploading now the older version via fpt. Hope it works!

  11. oksanaar
    Member
    Posted 12 months ago #

    Re-uploaded the older version via ftp - didn't work. Deleted the plugin completely via ftp - didn't work! What else can I do??? Please, advise. Thank you so much! So stupid of me to update on the live website..

  12. The Digital Hippies
    Member
    Posted 12 months ago #

    What is the error once you remove it fully oksanaar? Can you paste the error for us?

  13. fireproofsocks
    Member
    Plugin Author

    Posted 12 months ago #

    Sorry guys: I had gotten complaints about using scandir, so I replaced directory scanning it with FilesystemIterator but obviously that causes problems on some servers.

    To roll back you need to remove the directory and reinstall 0.9.7.6 from http://wordpress.org/plugins/custom-content-type-manager/developers/

    Will get an update out shortly.

  14. Dirty Bill
    Member
    Posted 12 months ago #

    Is there a risk to existing data and layouts by doing rolling back?

  15. fireproofsocks
    Member
    Plugin Author

    Posted 12 months ago #

    I can't guarantee anything on anyone's site -- I can't even guarantee you have the very common FilesystemIterator class, which should be standard. ALWAYS backup your site and your database. By updating the files, you are not updating the database, but always keep backups. That's the only official response that's sensible with a question like that.

  16. Dirty Bill
    Member
    Posted 12 months ago #

    First: FileSystemIterator Class is PHP 5.3 - not a qualifier you have in your update notes. By no means ubiquitous.

    Second: You know your software, not looking for guarantees, was just looking for a heads up for any known issues.

  17. oksanaar
    Member
    Posted 12 months ago #

    I'm still getting the same error... Some parts of the website work (like home page and individual articles). But the pages which use CCTM like tours page (tour is a custom post type), is not working. The problem is still the same... Fatal error: Class 'FilesystemIterator' not found in ....wp-content/plugins/custom-content-type-manager/includes/CCTM_Ajax.php on line 80

    wp-admin page is getting the same error as well... maybe I need to clean up something somewhere else??? Thanks for asking, THe digital Happiness.

    Stupid me for doing the plugin update live...

  18. fireproofsocks
    Member
    Plugin Author

    Posted 12 months ago #

    Even PHP 5.3 is at end of life. I did write a unit test for the FilesystemIterator class; now I've reverted the functionality back to scandir and I've now ensured that my unit tests run on updates as well as on first installs.

    My tip is to always keep an export of your CCTM definitions (Tools --> Export). Keep a backup of that .cctm.json file -- even if your database options get corrupted, that file will let you restore your content types and custom fields.

    Please update to 0.9.7.10 (the 0.9.7.9 packaging seems to have failed).

Reply

You must log in to post.

About this Plugin

About this Topic

Tags

No tags yet.