WordPress.org

Ready to get started?Download WordPress

Forums

Custom Content Types
[resolved] Plugin could not be activated because it triggered a fatal error... (11 posts)

  1. ThemeMee
    Member
    Posted 4 years ago #

    Parse error: parse error in C:\wamp\www\mysite\wp-content\plugins\custom-content-types\_include\class.wp-plugins.php on line 463

    Fresh install of WP 3.0.1 on WAMP
    - PHP 5.3.0
    - MySQL 5.1.36
    - Apache 2.2.14

    ??

    http://wordpress.org/extend/plugins/custom-content-types/

  2. ooeygui
    Member
    Plugin Author

    Posted 3 years ago #

    Thanks, I'll take a look at this asap

  3. mononoke
    Member
    Posted 3 years ago #

    Any update? I'm getting this as well with a new install of WP 3.0.1 on WAMP.

  4. jatubio
    Member
    Posted 3 years ago #

  5. fireproofsocks
    Member
    Posted 3 years ago #

    You gotta stop using php short tags. Always use the full "<?php" tag, NOT "<?", otherwise your plugin will be condemned to the trash heap by anyone who must deploy it on a server that has short tags disabled.

    Parse error: syntax error, unexpected $end in /path/to/wordpress3/html/wp-content/plugins/custom-content-types/_include/class.wp-plugins.php on line 463

  6. ooeygui
    Member
    Plugin Author

    Posted 3 years ago #

    fireproofsocks -- Lol, this has been fixed.

  7. mrchristoph
    Member
    Posted 3 years ago #

    Are you sure? I have got the same error, and see there is lots of <?=plugins_url() and such throughout the plugin. I have changed all the php tags to the full version, which very almost works - I can install it, but now it will not let me save any new content types - and there isn't any text on the submit button. It just refreshed the page when I press it.

    Maybe I am looking at a previous version or something?

  8. fireproofsocks
    Member
    Posted 3 years ago #

    ooeygui -- what version of PHP are you using? And do you have full errors being printed and short-tags off? You may need to re-submit changes. The WP repo had some problems with updates, so maybe mrchristoph and others are seeing an older version.

  9. Wessty
    Member
    Posted 3 years ago #

    Hello,

    I am having the exact same error here. Is there anything I can do to resolve this on my end? Or has there been any developments since the last popst?

  10. Wessty
    Member
    Posted 3 years ago #

    Just a quick update. I manually changed the "<?" tags, and it managed to activate itself.

    I thought I would mention it as it might have been a publishing problem for the plugin.

  11. fireproofsocks
    Member
    Posted 3 years ago #

    If any changes were submitted sometime from about 2 months ago to about 3 weeks ago, the WP repository did not update the plugin's download link, so the SVN copy might have had updates, but the forward facing website did not. This was a major screwup in the repo ... any developers may have thought that their changes were properly posted, but instead the changes somehow flew under WordPress' radar.

    ooeygui, if you did submit changes, try re-submitting them and tagging a new version of your plugin.

Topic Closed

This topic has been closed to new replies.

About this Plugin

About this Topic