Heads up all readers, the plugin has same problem with CSS, PHP and JS.
You can add scripts but not manage or change scripts once saved/activated.
If new user, don’t install and use until fixed.
If old user, you can only access scripts (edit code or activate/deactivate) via back-end database edits which is risky but feasible if mission critical.
Uninstalling plugin may also stop all scripts but will not remove left-over database table as plugin isn’t uninstalling well either.
Appears drop and select database functions have failed with change of WP to 4.2
Update released. Thanks FlipperCOde.
Hi, uninstalling is still not working fine. I can not uninstall it without afecting Gravity Forms. This is not funny.
@janolima
Saw your post. Not enough info for plugin owner to respond.
Q1. Did you load/add a script using the [Custom css-js-php] plugin?
Q2. Did you edit/remove the script you added with this plugin before you attempted to uninstall this plugin?
Q3. When you say uninstall failed, did it partially uninstall (can’t see plugin options in admin menus)?
Q4. The issue with gravity forms… was the problem evident:
a. before you installed the [Custom css-js-php] plugin?
b. after adding/activating a script with this plugin?
OR
c. after trying uninstall of this plugin?
I don’t use Gravity forms myself, but can try and help you.
The script you added via this plugin… What was the purpose of this script?
I assume you tried to edit/remove the script you activated with this plugin and found the issue I reported – i.e not being able to change added scripts? Or were you able to change the script added??
WordPress has been updated since this post so it is not unusual for problems to resurface.
But as I stated at top of this post/issue you can effectively deactivate the loading of all scripts enabled by this plugin by editing the database tables associated with this plugin.
Then you can manually delete the plugin files from WordPress install folder. The only issue in not running a proper uninstall process is the tables abandoned in the database. These do nothing bad, but take up space which can have performance and storage hit long-term.
