Wordpress 3.5 upgrade to 4.0. Theme compatibility - wordpress

I got in charge of some small sites that are running on WP 3.5; they are all using the same theme (a customized version of Bones). I have only used Joomla some years ago so I have no idea if, after the upgrade, the theme will still be compatible. I want to upgrade my WP version because the current one is vulnerable: I keep getting spam links into my articles that are placed inside hidden divs.
How can I know if the template is compatible or how can I fix the security issue. Any of these will do great.
Thanks!

WordPress does a very good job of changing very little with regards to theme tags in a core update. That said, we have no idea how your theme(s) have been made, or what functions they use.
The best, and probably only realistic option here, is to create a test site (a duplicate) and update that site first, then test to make sure all is working as it should.
As for the vulnerability, this is likely due to an insecure admin password or an insecure plugin. You should ensure all your plugins are up to date and that your admin panel is suitably secure.

When you update wordpress, it will not affect the wp-content folder which is having themes and plugins. So, don't worry update it. But for the secure updation, please take the backup of whole website first. Take backup of database and all files before doing any update.

WP 4 hasn't been out that long. I'd hold off on the upgrade unless you absolutely have to, until you know that all of the plugins used on the sites are compatible w/ WP 4.

Try to install the site on your PC creating a local copy using XAMP (for Windows).
In this way, you can:
download the MySQL database to have all the information of the
website locally;
install the latest wordpress platform locally (on your PC);
test the website thorugh common browsers.
At the end, you'll be sure about the compatibility and you can update the main site.
I have built my own theme with the Artisteer software; then i modified many PHP file to manage the loop in some special ways; so, to be sure that everything is working after an update of the site Wordpress version, i test everything on my PC.
For the vulnerability, please verify your plugin and all your theme file.
In some experiences, there are some plugin or simply some codes place somewhere in your theme which can create something like this:
> <div id="headerblock"> <center> <div style="left: -2227px; position:
> absolute; top: -3337px">
The only thing to do is check all the theme file and plugin to see where this code is placed.
Please check here for more information.
If you only change your password, probably it will not solve you problem because the malicious code is already inside your system.
Sometimes the malicious code can be placed directly inside the MySQL database.

Related

Local instance of wordpress edit plugin

I've having an annoying issue with Wordpress.
First I have to say that I'm not very familiar with Wordpress, I’m using it because I agree to take the management of the website of my sport club.
Now let’s me explain the issue. The previous manager of the website found a plugin that he think will be nice for the website.
But now that I’m managing, I want to make some change to this plugin (which is under GNU GPLv3 License so I have the right to do it).
So I install wamp on my computer, then wordpress and then I add the plugin to it in the purpose to test my changes.
I was thinking that when editing the files under “…\wp-content\plugins...” it will take effect instantly but it’s not.
I try to restart wamp after making some changes but it does not solve my issue.
A bit later I found that in wordpress there is a plugin modification interface and when going in it I found that the changes that I made on the files where not taken. Is there a cache of the files or something?
So my question is the following: Is there a way to edit the files in the folders (I’m using Visual Studio Code) and that the changes are applied instantly to the “running” plugin in my local instance?
I hope I was able to be clear enough so you guys can understand me
Thanks in advance

Would one-click installation delete previous website?

I am helping a friend build a simple Wordpress website, their current website is with a hosting and domain service called https://www.icuk.net/.
The website is very poorly built on this platform. I told them I'd make a website for free on WordPress as I have some experience with drag and drop WordPress website builders.
My question is, if I use the platform's one-click WordPress installation, does it automatically delete the website that was previously using the domain and hosting? If so, could anyone explain in layman's terms how I would go about backing it up, as it's always better to be safe than sorry.
I would be hesitant to do this, personally. I believe you can use the one click service to uninstall, at which point you can install WP again. A better option, however, if WP is already installed, would be to just change the theme, deactivate and delete any unwanted plugins, and then delete (or change to draft if you may want any of the content for your new development) any unwanted posts or pages. A current version of WP is a current version of WP, thus there is no reason to reinstall. Once you change the theme, remove the posts and pages, and remove the plugins, you are essentially back to a new install. Maybe do that instead?

Restarting a wordpress project

I am a freelance developer, and I normally build sites from scratch without using any code generating sites like WordPress or Square Space. But my current client insists on using WordPress. However, I am rescuing this project from a previous developer who made a big mess because from the looks of it does not seem like they knew what they were doing.
Is there a way for me to restart everything, on a clean slate and template on WordPress? I would like to have none of what the previous developer has done. Also is there a way for me do do direct coding using HTML, CSS, JavaScript etc on a WordPress site?
Yes, you just need to look into how to create a theme, since themes are the basis of the Wordpress structure. Ultimately, if you have the code for a website, it can be broken into separate files that Wordpress can use.
See: http://www.wpexplorer.com/create-wordpress-theme-html-1/
If the previous developer has done all the work in the theme files, then simply switching the theme to a default theme (Like Twenty Sixteen) will give you a nice clean slate to dig in and jump off with. You will want to create a child theme of any existing theme if you want to make any changes. If, however, the developer has messed with other files besides the theme folder, then you will most likely want to export the content only (as a logged-in administrator, go to Tools > Export (here's a screenshot))
Then on a new environment (I prefer testing these things first on a local virtual environment like VVV, and then transition to a development subdomain on the same server that the site will eventually go live on and securing it with an htaccess user/password to block curious eyes), import the content on a fresh installation of wordpress via the same menu (Tools > Import). This will give you a fresh installation with the content that's been created, but without any of the mess.
For more information about importing content - here's the codex article.
I hope that's a good start - but if I've glossed over anything you don't understand, let me know - I'm happy to help.

Wordpress WP Clone plugin is resetting my site

I have a Wordpress site I need to clone for testing purposes. I used Open-Shift to host the scratch site that I will be working on. As for cloning, I am using the WP Clone plugin. When I create a backup file on the real site, it works, and then I paste the URL on the restore for the scratch site. When I go to my scratch site however, none of the content is their, and I have to re-setup Wordpress. Is there another, better, more reliable way to clone a Wordpress site, or am I doing something wrong?
I have used WP-Clone quite a bit, and unfortunately in this scenario, it is the most solid plugin I have found. If you want to go the same route you have been (ie: use a plugin)...you have multiple options. You could check out:
https://wordpress.org/plugins/all-in-one-wp-migration/
And if you don't mind a little bit of complexity - the most comprehensive solution is probably more like:
https://wordpress.org/plugins/duplicator/
I hope that helps. Sometimes those types of plugins can be a little buggy - and it is still a good idea to scan your database to make sure the information was transferred correctly.
Also, have you checked your wp-config file to make sure it is pointing at the correct database on the new site? Sometimes that requires a manual change, as they differ.
Cheers.

Magento CSS not Loading in New Template

I have posted on the template creator's site, as well as Magento support, but no one has responded.
The CSS is not loading at all on the custom theme I have installed, which is supposedly compatible with the current version of Magento.
You can view the page here: shop.dearearth.net
This is a fresh installation of Magento and the theme, with a fresh database.
I have a feeling it should be a relatively quick fix.
Thanks for looking.
All the links in your page referring to the
http://www.shop.dearearth.net/skin/frontend/base/
directory on your site returns 404. Make sure your css files are in fact in there. Also make sure your links aren't being broken by a .htaccess file.
Make sure your CSS is 777 rights by admin.
OR
Please copy the whole code from latest css and take it as a backup and create a new css file as same name and past the code.
Check in admin back-end, System > Configuration > General/Design if your theme is right specified. Also check if after you installed the new theme, the files have the proper rights (normally, they must be accessible by the web server with Write permissions)
For more info please also take a look at Magento Designers Guide for understanding of how Magento read and split template information. Maybe you have put the CSS and images in a wrong directory :)
Solved.. sort of. The version of the template turned out to be quite outdated, and the incompatible with the current version of Magento, which handles things differently in terms of calling styles in the page.xml file.
Thanks for your inputs.

Resources