So i have got an issue with Wordpress on my local machine i am running OSX 10.10.5
I am creating a Wordpress theme from the scratch and it seems to be an issue with the database. When i create a new post, it is not added to the database, next when i try to install a plugin, it is also not added to the database. I thought it is down to permissions, but no.
I have recently tried to install php mcrypt on my machine and was playing a lot with Apache/MySQL/PHP config files as well, maybe that affected as well?
I have completely removed mysql, still nothing.
I am running MAMP for local development so i thought it should be all good, but also no
If you have been playing with things that can be causing the issue, I think this will be very difficult to solve for you or any other, without knowing exactly what you have changed when the issue appear.
I recommend to just reinstall MAMP, WordPress and anything you have been playing around.
For self-experience, I recommend you to don't change things you don't know on a site that is a production site. Make a site for testing or at least, take a backup before. I have already learned that the hard way :)
Related
As a self-taught developer I have always worked directly in cPanel to edit websites, which is obviously not the way to go. I am looking to figure out how I can start connecting local folders with cPanel so I can easily try changes locally before deploying them to the live website.
I have heard about FTP and checked out fileZilla but that seems to still be a manual process. I am looking for a way similar to using Git. Run changes locally, and then commit and push them to cPanel when all is good.
If anybody has any suggestions on the best way to go about doing this, that would be greatly appreciated. I'd like to work with node.JS if possible but just running php would also already be great.
I'd recommend using GIT itself. cPanel has now integrated GIT to its updated versions.
You can read more about this from below URL:
https://blog.cpanel.com/git-version-control-series-setting-up-git/
I can download the WordPress website which is already created. So, I need to run that website locally. Please let me know step by step.
I don't know your setup but I'll give you a complete solution now and then we fix any problems afterward.
First thing you need to do is download a local WordPress hosting environment and set up a local host for the website. I prefer to use FlyWheel because it's the easiest so far. Other options include Laragon, XAMP, and WAMP.
After installing Flywheel and setting up a local install you download the "All In One WP Migrator" plugin on both the live website you want to run locally and the local website.
Once you use that to migrate the website to a local setup everything should be fine. If you have the error establishing database connection again I will tell you how to resolve that. It's pretty easy actually.
I would like develop and test my wordpress website on windows xp system.I'm unable to set Wordpress in my system, please help me to find a suitable phpmysql server which supports wordpress on windows xp. I've already used uniserver, phpmyadmin, and esy php but they are not worked well.I am new to this and any help will be appreciated
Thanks
You can try Xamp, Wamp for windows, and if you already have prebuild wordpress then you have to make sure that the migration is done properly.
For migration there lots of plugin available to that use one of them.
Or just change the host file with same domain name, so that you can test your wordpress site without any migration burden.
Bitnami wordpress is a very easy way to get set up on windows. It comes with the whole stack to get you set up and is installed in just a few minutes without any command line usage. https://bitnami.com/stack/wordpress
I was using Magento 1.4.1 and upgrade gracefully to 1.4.2. After testing if the upgrade was Ok, I made some modification in order to have a new home page layout for a store using these instruction. The modifications have been tested on a local version (Ubuntu 10.04, php 5.3.2), and worked great.
When I upload the files to the pre-prod server (Centos 5.5, php 5.2.14), and access the System->Configuration->design tab in the admin backend, my browser seems to keep loading indefinitly.
What I have done:
I copied the app/code/core/Mage/Page/* directory to the app/code/local/Mage/Page/;
I created the app/etc/modules/Mage_Page.xml, and defined the codePool to local;
What I have already checked:
I got no errors in /var/log/httpd/*.log;
I got no errors in magento's var/log/system.log;
The frontend works fine;
The backend can be accessed, except the System->Configuration->design tab;
I tried to revert my modifications to a revision before the modification were made (using svn);
I cleaned up the cache using rm -fr var/cache/mage* var/session/* directly on the server;
I restarted the server multiple time;
I even tried to get a dump of the db in production on the preprod server, with no effect. I still got the same issue.
If someone could point out anything I could have forgot.
I am ready to try anything to make it work, since it would not affect the production server for now.
After a lot of searching, we finally tried to reboot the apache server (we had to force it to reboot, I don't know why?). When we retried, everything was working as expected.
There probably was a corruption on the server that made crash only this tag.
Hope this could 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 :(