• v 0.31
    Parse error: syntax error, unexpected ‘;’, expecting T_FUNCTION in /home/content/20/8281920/html/wordpress/wp-content/plugins/artistdatapress/inc/adp_widget.php on line 249

    Warning: include_once(/home/content/20/8281920/html/wordpress/wp-content/plugins/artistdatapress/artistdatapress.php) [function.include-once]: failed to open stream: No such file or directory in /home/content/20/8281920/html/wordpress/wp-settings.php on line 192

    Warning: include_once() [function.include]: Failed opening ‘/home/content/20/8281920/html/wordpress/wp-content/plugins/artistdatapress/artistdatapress.php’ for inclusion (include_path=’.:/usr/local/php5/lib/php’) in /home/content/20/8281920/html/wordpress/wp-settings.php on line 192

    http://wordpress.org/extend/plugins/artistdatapress/

Viewing 5 replies - 1 through 5 (of 5 total)
  • ftp to site or use host’s file manager to rename the /artistdatapress folder
    this will deactivate the plugin and let you log in to test

    Thread Starter huntington

    (@huntington)

    was previously using v.2 with WP 3.2.1, and had no problems. upgraded from within the dashboard to v.32 and got this error message:

    Parse error: syntax error, unexpected ‘;’, expecting T_FUNCTION in /home/content/20/8281920/html/wordpress/wp-content/plugins/artistdatapress/inc/adp_widget.php on line 249

    Dashboard wouldn’t even let me activate the plugin.

    was able to back down to v.2, which I was previously using, good for now.

    is there a way to test an upgrade to a plugin before it goes live so that I don’t run into this problem again? or do people just test plugins on a secret identical live site somewhere else?

    they are supposedly tested to be compatible with most recent version of wordpress

    perhaps contact the author and inform him of your problem

    Thread Starter huntington

    (@huntington)

    done (had to find the comment section on his website to do so but he’s aware of the problem and has been working on it…).

    wish there was a way for him to discourage people from uploading til he fixes the issue

    Plugin Author slushman

    (@slushman)

    Hey guys,
    Sorry for the delay and all the errors. ArtistData’s XML feed does a 301 redirect to a Sonicbids URL now, so the feed URL they give you isn’t actually the URL for the XML feed. When I changed to the .3 version of ADP, I started using cURL to get the XML feed, but didn’t tell cURL to follow any redirects, so it gave errors when using the feed URL ArtistData gives you. It should work now, check out the .33 update.
    Thanks for your patience,
    Slushman

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘[Plugin: ArtistDataPress] two versions causing fatal errors!’ is closed to new replies.