I was building a theme for a client of myne on mamp. When time came to update the theme on the development server, under appearances --> themes, I accidentally deleted the theme I was working so hard on! (I thought I was on the development server wordpress site, not on the local one)
I still have everything open as it was. Is there any way to recover wordpress' delete on my local server?
Assuming that the files are not in the Trash can, there are a few utilities available that may be of some assistance.
This article covers two of the most popular http://www.cultofmac.com/67472/how-to-undelete-files-in-mac-os-x-macrx/
In the event the link dies, the two recommended utilities are
SubRosaSoft FileSalvage
Prosoft Data Rescue
Good luck!
Related
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
I have a wordpress website that I maintained entirely through the wordpress admin dashboard. We don't use a staging server or FTP client etc.
I need to make some big upgrades to the the theme version and some plugin versions to fix some bugs.
Is there a way to back up the website or anyway that I can revert to the current setup before I proceed with this? Is there any tools or plugins that I can use for this?
Thanks
You can use this plugin to have backup of your website. Good thing is, it takes backup of db as well. https://wordpress.org/plugins/backupwordpress/
It would be risky on your end to make big upgrades without at least an FTP access, even if you have a backup plugin, when your website breaks up, you can't restore it anyways.
If you really need to do it, just do the updates in small increments, from small plugins to the biggest ones.
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.
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.
In a wordpress installation we want to have our main site, and a staging site separated and different. Where in the admin interface you separate your staging area?
Let's say:
for production you will have: http://www.yourdomain.com/
but for staging we want to have: http://www.yourdomain.com/staging
Staging is the website that will be in production next.
Any ideas?
With Wordpress 3.0+ you might be able to create a network of sites or install multiple sites with an older version of Wordpress. The catch is I don't know of an easy way of moving the staging to production. I'm not entirely sure that will do what you want, but you may want to look into it.
Personally I'd think you'd probably be better off keeping your staging and production sites on 2 different servers and just do a copy over when you move to production.
I don't know of any instant, simple answers, but have you seen this article in the Wordpress support forum? It has some informed discussion and at-least partial solutions:
http://wordpress.org/support/topic/one-wpseveral-servers
If your staging site doesn't need any database modification, or custom forms/widgets for the backend, you can create a new theme, and test it in the preview mode. When done, you can switch the theme to the new one!