WordPress.org

1. mistike
   Member
   Posted 1 year ago #

   Hello,

   I have run into two different errors at plugin activation. This post is both to document both workarounds in case somebody else has the same pbs, and to request a fix in the next release ;-)

   WP 3.0.1 locally installed, running on WAMP w/ PHP 5.3 and 5.2.11

   1) PHP Parse error: parse error in <plugin_path>\feedreading_blogroll.php on line 2569

   This error is due to incompatibility bw plugin and PHP 5.3.
   Workaround : install PHP 5.2.x as a second PHP version in WAMP and switch to it.
   Download additional PHP version for WAMP here : http://www.wampserver.com/en/addons_php.php

   2) PHP Parse error: syntax error, unexpected $end in <plugin_path>\feedreading_blogroll.php on line 2569

   This one is due to <? not being recognnized as PHP tags.
   I found one on line 578 and changed it to <?php, but still got the error. Since I didn't have time to search for any other one, I switched short_open_tag to On in php.ini and restarted WAMP services.

   Now for my requests ;-) :
   - can you please correct the remaining <? tags in next release ?
   - Is it possible to update the plugin so it's compatible with PHP 5.3 ?

   Thanks a lot

   http://wordpress.org/extend/plugins/feed-reading-blogroll/

2. Erunafailaro
   Member
   Posted 1 year ago #

   1) I will test this and will try to find a solution.

   2) Should already be fixed with the development version.

   Thanks for reporting those errors!

3. mistike
   Member
   Posted 1 year ago #

   Hello,

   Thansk ;-)

   The dev version seems to have the same problem. You can for example find the short tag <? I corrected at line 578 :

   <? printf(__("If you have just upgraded to WordPress 2.8, you will have to add the Widget of the WP Social Blogroll plugin to your sidebar again. <a href=\"%s\">Please go to the Widget-Settings-Page</a> to add the widget to your sidebar.","feedreading_blogroll"),get_option('siteurl'). '/wp-admin/widgets.php'); ?>

   If I have some time I'll try to see if there is any other one somewhere.

4. Erunafailaro
   Member
   Posted 1 year ago #

   Line 578 is fixed now in the dev-version.

   The error from line 2569 seems to be a tougher one. 2569 is the very last line, there isn't any code in that line ...

5. mistike
   Member
   Posted 1 year ago #

   This error means some opening/closing tag or bracket, or whatever, is missing somewhere, between lines 1 and 2578 ;-) (that's for case 2)

   For case 1, i'd have to look into it, but there are a good amount of differences between PHP 5.2 and 5.3... It would have to be looked into for next releases, but in my case the pb is not so big since my prod server (hosted) is PHP 5.2. I just had to install this version on my dev platform.

6. Erunafailaro
   Member
   Posted 1 year ago #

   But I think a missing bracket should also be a hard error in PHP 5.2 ...

   Maybe it's something else.

7. mistike
   Member
   Posted 1 year ago #

   That's right, but still it was solved with short_open_tag = On so... i'd vote for another <? instead of <?php (didn't find it because I searched for "<? " with a space after, otherwise the search returns all <?php and there are just too many of them :-))

8. Erunafailaro
   Member
   Posted 1 year ago #

   Ah, I found it in line 777 by searching with a regular expression.

   I searched by the regex <\?[^p], i.e. all occurences of <? that are not followed by the letter p.

   That one is also fixed now in the dev-version.

9. mistike
   Member
   Posted 1 year ago #

   Great (regexp are not my friends ;-)). I just tested on my test blog, and the extension activated ok after this second change, with short_open_tag = Off !

   Thanks ^^

Topic Closed

This topic has been closed to new replies.