I have a web server running Wordpress 3.3 for a couple of sites and that is fine. I want to put another new website on this webserver but figure I should use the newer Wordpress 3.6 for this one. When uploading the newer version of Wordpress to my webserver my FTP client tells me that some of the Wordpress files already exist in the destination (only a handful). The thing is, I am uploading to a new blank folder. There are no Wordpress files in there.
I am wondering if there is some kind of conflict going on with 3.3 vs. 3.6 on my webserver?
Any help appreciated.
Thank you.
I guess that either you don't know what you are doing or you FTP client is cheating on you :).
If you have a separate directory for each web site (running wordpress or not) together with separate databases for each website then you can run multiple websites using different wordpress versions without any problems.
The only problems you can encounter is that you would need to upgrade you php and/or mysql or other libraries on your LAMP server for new wordpress software to be run, thats normally back-compatible and shouldn't affect your older wordpress installations but its always good to check before an upgrade.
Related
I have a WordPress Multisite running on a relatively new Amazon Web Services (AWS) Lightsail instance, based on a Bitnami image (provided through AWS Lightsail) running a LAMP stack, based on Debian.
Until recently, plugins installed through the WordPress multisite Administrator Dashboard installed and ran good. Worked great before, no problems. Now, for some reason, attempting to install any WordPress plugin surfaces a dialog requiring FTP credentials be provided. There's a screenshot of the WordPress multisite dialog asking for FTP credentials at the end of this message.
I'm thinking this - new - demand to provide FTP credentials when adding a WordPress plugin is happening due to permissions. Naturally, I'd rather not need to install WordPress plugins using FTP.
So, I have two questions:
What settings were accidentally - somehow - changed to cause WordPress to now produce this new requirement asking for FTP credentials when installing any WordPress plugin?
How to I fix WordPress so that plugins can be installed without FTP?
I did see many solutions for fixing permissions on the Internet, except since I'm new to AWS, Linux (Debian) & WordPress I'd like to use this opportunity to learn how this situation happened, while learning how to fix the hiccup. Other than using a few new plugins, which installed & ran fine without FTP, I have not made any edits to any internal WordPress files.
The only chance to change permissions might - maybe - have happened when setting-up users within my AWS account, including setting-up of a Yubico key with key-pairs --> I don't think that security change would influence the LAMP stack running the WordPress multisite, but I wanted to offer information that might - maybe - related to security changes influencing why, now, adding WordPress plugins requests FTP credentials.
Thanks in advance, everybody. Thank you. :)
WordPress multisite dialog asking for FTP credentials
I tried to add many, many WordPress plugins to confirm that every WordPress plugin now asks for FTP credentials for any new plugin.
I have looked at many Internet posts explaining how to change WordPress & Linux permissions, along with posts explaining how to change WordPress configuration files to not ask for FTP when installing new plugins. I have not acted on these many suggestions since I'm cautious & careful --> I'm ready to study months & months becoming a Linux, WordPress, and supporting technologies expert, but at this stage since I'm new to all-of-the-above, I'm reluctant to make any changes until I fully understand the technologies (after making this post, I will make copies of WordPress configuration-files to test changes that can be undone, but I wanted to see whether StackOverflow might help me learn what happened in the first place, while learning how to correctly fix these issues.
I pay for AWS Premium Support --> I've sent a message to AWS Premium Support, but so far have not heard back from AWS.
I am developing a theme for a site usign wordpress as a cms. The site has already more than 2000 posts. I am working locally on my computer and trying to simulate the post types etc here. Almost done. But I am very scared to upload and activate the new theme I have been developing locally.
What is the best way to test it and see everything is OK and be sure that I am on the safe side.
Thanks for your answers.
Not sure what you're asking exactly here but what you should be doing is testing it in an environment that's the same as your production environment. In other words, same operating system version, same web server version, same PHP version, same MYSQL version, etc.
how can I run a Joomla website on tomcat. now I had used XAMPP for creating the website. now I am going to host this on a tomcat5 server whether I can host a Joomla website on tomacat5?
As pointed out in other questions / answers or some documentation you can certainly run PHP on tomcat.
There is also a php-java-bridge you may want to look into.
But I am not sure why you would want to do that. Generally you would want to run Joomla on an Apache server, especially from the support point of view.
I have done a blog in mamp and would like to push into hostgator. Must i recreate everything in hostgator like Installing Wordpress on Hostgator. Is there any way i could just push my stuff straight into hostgator without redoing everything in hostgator. Need some suggestion.. Thanks..
It's quite easy to deploy a local version of Wordpress to a live server. First of all, you are right, I would not bother installing a clean copy of Wordpress on your server, you'd then have to totally rebuild the site.
What you need to do is;
FTP all your files from your local machine to the server.
Transfer the whole database from local phpmyadmin to a new database on the server
Change the database connection details in wp-config.php
Make any necessary changes to your default Wordpress .htaccess. What I mean here is that your MAMP site probably isn't in the root but your live site probably will be. If you have SEO permalinks set up then you would remove the Mamp subdirectory from the rewrite rule and the base in the .htaccess. Your host might also require you to add rules here (ie specifying which version of PHP to use etc). You could always install Wordpress using their installer to see if they add any special rules themselves.
All easy so far - now comes my tip. Moving Wordpress databases from your local development environment to live can be a massive pain because Wordpress (and lots of plugin/theme developers) use serialized arrays to store data. So if you do a find-and-replace on the database to replace your old url with the new one, you will disable lots of things like config settings and widgets (text widgets specifically, but there's loads of stuff you end up having to recreate).
Download this file;
http://interconnectit.com/124/search-and-replace-for-wordpress-databases/
and upload it to the server and access it directly in your browser. Run through the quick form and perform a serialized array-friendly find and replace on your database urls. Job done. Good luck.
I am having a website redesigned. The designers plan to use Wordpress as the CMS and want a development copy to work with. Thing is, I now have Wordpress installed to run a blog (only) on a subdirectory of my current site.
Soooo...question is: Can I create a subdomain, install Wordpress on there, point it at a separate (new) schema on MySQL and have them use that for the development work? I know I can physically do this, but will anything about running the the WP install scripts on the subdomain screw up the existing production install on the main domain?
The install itself should not create any problems. Personally, I always develop WP sites in their own subdomain, allowing me to do away with the wordpress/ subdirectory.
The most significant hurdle will come when you are ready to move the development site to a new domain and/or place in the directory hierarchy. Although the theme files and their associated CSS, JS, etc., files should be using relative-path references, the database itself may contain hundreds of fully qualified URLs that reference the development domain and/or directory.
There are a number of WordPress plugins that address this problems. The one I am most familiar with is BackupBuddy from ithemes.com. (I'm not a shill, just a satisfied customer.) BB is useful both for performing scheduled backups (full or database-only), but it is also very useful during development and during deployment. There is an included script, importbuddy.php, than can not only take a .zip of a full backup and restore the site, it can also move the site from one directory and/or domain to another.
Note: BackupBuddy is not free, but it is released under GPLv2. You are paying for the support necessary to keep it tracking changes in the WP ecosystem. If you are doing any serious WP work then it is money well-spent. You might suggest this to your designers.
Yes you can do it. It doesn't matter. You can install your new blogs to any directory or subdomain (actually they're directories, too). Also you can use new MySQL databases for them, or you can use same database for your all WP installations (by editing wp-config.php manually), thereby you'll have same content for your all WP blogs.
Technically, yes you can do it.
However, if you have a live domain with public people using it, you are best not developing on either the same domain or server, because:
Mistakes happen. You can break the database or other code.
While you develop, you can affect performance of the server.
Develop on a local machine, or a completely different server, and when you are happy with it, push the code live onto the production server.
if you are planning to make a test copy of the current install on a subdomain which includes separate source code and database the answer is NO it will not affect your current installation.