Is there a way to downgrade any Wordpress plugin after upgrade? My client upgraded all plugins and now up-gradation of some plugin creating problem.
YES but it's not a one-click process like upgrading was. You need to delete the folder of the specific plugin from the wp-content/plugins directory and then upload the older version. You should be able to find a copy of each version on the various plugin websites.
No way other than to delete/remove them and re-install the required versions.
No. And neither you can downgrade the WP itself. That's why they always warn us to backup our data :S
PS_ you could download an earlier version, but I guess that's not what you're asking.
Related
When I try to access admin dashbord, an error is displayed. This error is: "Cannot redeclare use_block_editor_for_post()(previously declared in \wordpress\wp-includes\post.php:8067) in \wordpress\wp-admin\includes\post.php on line 2152".But the website is work correctly.
I use PHP 8.1 and Wordpress 6.0.3.
Any Help!!
First, backup all plugins through FTP to your computer.
Second, disabling all plugins or deleting them through FTP
Then check if the issue persists. If so, do the same for your theme. If the issue still persists, your installation might be corrupted.
Reinstalling plugins one by one, you will see which plugin caused the issue. Then you can investigate why. Probably an outdated version not compatible with the newest wp version and not maintained properly.
I have installed Moodle 3.7.1 with XAMPP. The installation had been successful and problem-free. I followed the below video for installation:
https://www.youtube.com/watch?v=Ov2dGoOBmSI&t=436s
Now my main objective is moodle plugin development. Since I am relatively new to this I was exploring plugins and trying to build a simple one first.
But whenever I am trying to install plugin (my own or from Moodle directory) I receive the SUCCESS message but then get 'Page Loading Error' and thereafter I am not able to go to any page
I found this thread on Moodle forums and have tried most of the solutions they offered.
https://moodle.org/mod/forum/discuss.php?d=355930
I dont wish to work on older XAMPP version
My cache folder under Xampp's moodledata folder is empty and i tried clearing my browser cache and restarting the servers.
But the issue still persists
Any ideas what maybe causing this? I have a feeling that its some kind of configuration issue but I dont know where to look and what to look for.
Thanks for all the help. It took me alot of installation and uninstallations but finally when I downloaded the full Windows installer package--it worked.
I guess it was some kind of deeprooted version conflict between xampp and moodle or some configuration issue.
I have purchased Jupiter theme and i have been using it for a number of website. But recently i am not able to work on the theme because the theme default plugin Visual composer is not working properly. When i go to edit page to edit the elements it shows blank and stays idle. I also tried to reduce the version of WordPress to 4.4 but still no use. Can somebody please support to solve this issue. The theme support has expire so no hope on that. And i am not so techie to sort what the exact problem is. If someone can guide me to solve it, it would be much appreciated. Many many thanks in advance.
The following image show the what i have explained
I think it is the compatibility issue of visual composer with the wordpress. If the visual composer installed it not latest there are the chances of conflict with latest versions of wordpress. So you may please confirm that the plugin you are using is compatible with the wordpress version you are using on your site.
I use Easyeclipse for PHP with the Subclipse plugin for a long time without any problem.
This morning I committed my project without any problem. This afternoon I try to commit it again and it gives this error, which concerns only a subfolder.
Unsupported working copy format
svn: This client is too old to work with working copy
'My subfolder'; please get a newer Subversion client
I found several questions where the solution was an update of the client, like the error suggests. But in my case, I didn't change any configuration nor installed anything.
I fear that some files got corrupted.
It could have happened during a manual copy-paste process on my local copy, but I have no indication for this.
Is there a way to know for sure if the problem is with the server side or with the client side.
What are possible steps to restore the situation ?
The problem is with the client side, server is not contacted at this stage. Your local repository checkout might have been silently upgraded by another svn client you use. Or it might also be damaged and Subclipse errorneously reports it as an upgrade it doesn't understand.
If you don't want to upgrade Subclipse, your only way is to do a fresh checkout from server, and copy over your changes from this upgraded repository.
This probably means you used another SVN client that was a newer version and upgraded the working copy to a newer format. Subclipse has versions that support all versions of Subversion. Most likely you need to install Subclipse 1.10.x which contains support for the SVN 1.8 working copy format.
http://subclipse.tigris.org/servlets/ProjectProcess?pageID=p4wYuA
Once you upgrade Subclipse to the right version it will immediately work again. Your existing working copy ought to still be fine.
In my case I move eclipse workspace place to another then problem is occured. For solving problem I checkout project form the svn repo. Then in old project I clean all svn files. (simple search .svn and delete ) then I copy the content to the just checkedout one my changes become visible and my project is up to date. This method can be applied for other annoying errors. Hope help someone
I tried to upgrade our shopsoftware from Ver. 1.3.2.3 to 1.4.1.0 and I used the Magento Connect Manager. It loads all the files and said they has been installed, but they are not. Under “downloader/pearlib/download/” are all these files. Have I forgotten anything or is that maybe a bug in our customized shopversion?
I’m searching for days and hope, someone can help me here.
I'm in your shoes as well. I've got an upgrade to do as well, and trying to do it automatically didn't work out well at all.
Here's the only upgrade path I've gotten to work:
Install a fresh copy of 1.4.1.0
Backup 1.3.2.3 via Magento
Move media files from 1.3.2.3
Bring skin over, convert to 1.4.1.0's new requirements
Bring modules over - turn error reporting on, and check for issues (there were a ton with ours)
Good luck. I'm still having some issues with ours :(