WordPress.org

Ready to get started?Download WordPress

Forums

2.8 RC1 Call to undefined function token_get_all() (22 posts)

  1. Evert
    Member
    Posted 5 years ago #

    I just upgraded my site to 2.8 RC1, and when I go to Admin -> Plugins -> Editor, I get Fatal error: Call to undefined function token_get_all() in /var/www/[wordpress-site]/htdocs/wp-admin/includes/misc.php on line 273

  2. petedost
    Member
    Posted 5 years ago #

    same here. when i click on a file on the right side the error occurs

  3. omarac
    Member
    Posted 5 years ago #

    I have the same problem but with the theme editor. My CSS file shows up fine, but any other file gives me that error. I tried deactivating my plugins but that didn't resolve the problem. I'm using version 2.8.

  4. nfxcr3w
    Member
    Posted 5 years ago #

    Yes ive noticed that problem too when i click Editor under Plugins tab
    i get that undefined function token_get_all() could be a bug since it was only released yestaday public so had to go back to 2.7 im glad i did a backup now could this be fixed a.s.a.p?

  5. nfxcr3w
    Member
    Posted 5 years ago #

    This update really messed my site up now. now im gonna have to put my old backup on :(

  6. axemanrio
    Member
    Posted 5 years ago #

    I'm getting the same error with the theme editor after upgrading to 2.8, happens when attempting to edit the .php theme files.

    Exact error: "Fatal error: Call to undefined function token_get_all() in /path/wp-admin/includes/misc.php on line 273"

    anyone found a fix yet?

  7. axemanrio
    Member
    Posted 5 years ago #

    If this helps, my local wordpress site running on xampp does not result in that error after upgrading. I tested the release offline and upgraded live site only because everything seemed alright.

  8. nfxcr3w
    Member
    Posted 5 years ago #

    id say its best to stick with 2.7 has wordpress team need to fix this problem out nd others that users are getting it was rushed out wordpress should of tested it completly before making it public.

  9. axemanrio
    Member
    Posted 5 years ago #

    At least you have an old site to put back on, I only did a db backup because 2.8 worked great offline. In fact, the primary reason I upgraded is because of the performance improvement which is noticeable.

  10. kitsunesniper
    Member
    Posted 5 years ago #

    I'm having this issue too in 2.8 final. What's going on? I thought it was a plugin issue, but now, well, it's pretty obvious it's not. Agh.

  11. axemanrio
    Member
    Posted 5 years ago #

    I switched back to 2.7.1, first time I've had to downgrade.

    Funny that 2.8 still listed as "The latest stable release of WordPress".

  12. petedost
    Member
    Posted 5 years ago #

    yep.. me too.

    this sucks :(

  13. memocodes
    Member
    Posted 5 years ago #

    I have the same problem :\, it appears to be because when php was installed on my server it was compiled with --disable-tokenizer. I am currently rebuilding php with tokenizer support and will report back with my findings after it is done (it takes a while to rebuild php.)

  14. memocodes
    Member
    Posted 5 years ago #

    Well, enabling the tokenizer did the trick, if you have the ability to do so on your server then I guess that's the solution. I'm not to sure what you can do if you can't rebuild/change php settings.

  15. amuletts
    Member
    Posted 5 years ago #

    I have this problem as well. You can edit the files the old fashioned way if you really need to. Just download them with FTP, make your changes then reupload.

    I really hope this problem is fixed soon.

  16. kitsunesniper
    Member
    Posted 5 years ago #

    Not all of us have tokenizer enabled. My web host has a lot of stuff turned off so the server works better, including this. I can't ask them to turn it on.

    Why couldn't they make this optional? Ugh. :(

  17. EasyTarget
    Member
    Posted 5 years ago #

    2.8 is out now, but this still remains. I also got bitten by it; so:
    http://core.trac.wordpress.org/ticket/10262
    Lets see if this can be resolved properly, submitting a ticket is usually the best way to make sure the developers are aware of this sort of thing.

  18. wilzdezign
    Member
    Posted 5 years ago #

    Me too!

    Guess there are other forum topics discussing same thing:

    wordpress.org/support/topic/279102
    wordpress.org/support/topic/281844
    wordpress.org/support/topic/278659

  19. Ryan Boren
    WordPress Dev
    Posted 5 years ago #

    This is fixed in the latest 2.8.1 nightly build. Try it out:

    http://wordpress.org/nightly-builds/wordpress-2.8-latest.zip

  20. wilzdezign
    Member
    Posted 5 years ago #

    Works.. Thanks!

  21. EasyTarget
    Member
    Posted 5 years ago #

    Ryan; many thanks for fixing this!

  22. codestyling
    Member
    Posted 5 years ago #

    I don't know why this is called "fixed" if it removes functionality!
    Sure, to run properly the blog, it should detect, that the PHP Module "Tokenizer" is not installed and disable it usage (which removes the ability to inspect WordPress documentation about WP tags found in code).
    But in my opinion this also needs a statement in this case, that you can get back this documention links (dropdown list of found tags) if you talk to your provider to get the "Tokenizer" installed.

Topic Closed

This topic has been closed to new replies.

About this Topic