Hi,
Sorry to hear that, is this still with version 1.7.7.1 or did you update to 1.7.7?
Hope to hear from you,
Regards,
Niels
That is strange, it seems that the other users that ran into this don’t have the issue in 1.7.7.1 anymore. Could you give me Your website link, and wp version so I can look into it.
Niels
Thread Starter
xnite
(@xnite)
Well, for now what I have done was just modify the variable to return a blank string and commented out the previous line. I couldn’t just disable the plugin, or leave the wp-admin area broken, so, kind of put a bandaid over it lol.
/*$plugin_data = get_plugin_data( __FILE__ );*/
$plugin_data = '';
but site is http://www.AltSociety.co wp version 4.3.1
Thread Starter
xnite
(@xnite)
followup: leaving $plugin_data as blank just makes options reset to default when I save them. So if I put the word ‘bandaid’ into the variable it seems to function fine. 😐
Hi xnite,
I just double checked the fix from this morning and it should be ok now. As you can see on the other two reports in this support forum it solved the problem for them aswell. Changing the plugin_data to a empty or incorrect value is not a solution. This value is needed to be able to give propper update commands.
There reason it went wrong is because I accidentaly requested it from the frontend, and ofcourse this is not possible. So the best fix is to only requested in on the admin side as it was intented to.
Sure that 1.7.7.1 did not fix it for you?
Sorry for the caused inconvinience, could you please try the updated I just pushed. Version number 1.7.7.2 should hopefully finally fix the issue. I reverted back to the old way.
Please let me know if it’s oké after updating.
Regards,
Niels
I assume this issue is resolved. Topic closed
