-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unexpected end of file #5
Comments
That's strange, I'm not able to reproduce it on my end. Maybe try downloading again? |
Of course I did it prior to raising an issue. I have just tried it on another server, seems to be working fine with exactly the same settings that have previously caused the bug -_-. Just one thing it brought the notice: Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method Linkmarklet::assets() should not be called statically in .../wp-includes/plugin.php on line 470 |
Allright did some more testing. It is simply not letting me install it on any local dev server. On my regular hosting I experience no problems... |
I'm not familiar with that local configuration but if it seems to be the culprit I'm not sure that there's anything I can do on my end. |
I'm having the same "end of file" issue. For whatever it's worth, I'm running my site on a Digital Ocean LAMP server (Ubuntu 14.10). I can only guess that there's some PHP module that needs to be enabled (that might otherwise be available on a shared web hosting account). EDIT: I figured out the problem. Abbreviated PHP openings <? instead of the standard <?php |
This is a fix for the "unexpected end of file" issue [jchristopher#5]. The issue was caused by using using <? (which is not supported on all PHP installations) instead of <?php
Hi Jonathan,
I have just downloaded your plugin and when trying to activate it on local dev server I have received following error:
Parse error: syntax error, unexpected end of file in C:\BitNami\path_to_wp\wp-content\plugins\linkmarklet\linkmarklet.php on line 226
It have produced no error on test dev server. both local and dev are running WP 3.9.2
The text was updated successfully, but these errors were encountered: