johnwp413
Forum Replies Created
-
This isn’t a solution but might be a decent tip until .org can figure out how to flush the subscription list properly. Or at least that sounds like the problem.
Most email apps will let you set up a filter. I filter emails to certain folders. Like the ones from this feedback/support. The folders for emails I don’t really want to spend much time with (like Adobe) I can easily go in and “select all” and just delete the accumulation since the last deletion or actually scan subjects or content if I’m looking for something.
Of course it’s not a total fix. But it at least keeps my Inbox more manageable and makes it a few steps simpler to get rid of things.
Change “overwrite” to “replace” and perhaps that is more clear. When you execute the installer script for a Duplicator package, you are essentially moving all files from one location to another, WordPress and all.
Again, as a user I am not “instructing” you. But in every instance where I use Duplicator to move back and forth from development/staging to a live host, my first step is always to remove the old (delete). Then you “replace” everything with the new, including database entries, etc. So whether or not your “space” for a website was setup or configured with a different version of WP isn’t that important. You are essentially removing it to install what you have packaged with Duplicator.
Hope that helps!
I’m an just a Duplicator user, but am in the process of updating sites over weeks. I think what you are saying is that your host will only allow you to set up a website beginning with the latest WP release – 5.0.1. However, following the best practice for installing a website using Duplicator, you should delete the previous files and run installer.php which will reinstall the version within the package you created – 4.9.9 as you say. When you log into your dash, expect to see WP update nags.
As far as backward compatibility, I have not experienced any WP theme conflicts yet. (Only work with 3 themes across a number of sites and my own custom builds so it isn’t a huge sampling). However, there might be some plugins that get quirky, especially ones that haven’t gotten attention from the authors in a while (over a year?). The main difference for a website user in the newest version is the way you edit posts and pages which you can see here: https://wordpress.org/news/2018/12/bebo/
But as stated there, you can revert to the old style with a plugin.
Thanks Cory. Unfortunately I cannot run Duplicator on the hosted site because I have no access.
My challenge is that I have –
1) A 4 week old Duplicator package that is missing 4 new pages and minor other differences on existing pages.
2) Something “odd” that is corrupted in WP core that ONLY affects hosted site admin and not site function.
3) Conformed both the most recent duplicator package and the current site are running WP 4.9.8. I launched the most recent referenced above package on my localhost.So, not being able to access the dashboard (start /wp-admin.php) and simply reinstall/repair WP, I was hoping to be able to find some path between the 4 week old Duplicator files (in the zip) and the still running website. My customer’s host will help but there has to be a more or less open ended check to get support from their WP “experts.” You buy “credits” that are only good for 30 days. Each action takes a credit, or something. Very convoluted.
At this point I have saved the currently running files (ftp) and I am looking to see if any files look different in what I assume is core WP. That is, comparing files pulled recently to the files in the last Duplicator package. It is proving too tedious at this point. Lots of files. Next step is to backup the hosted mysql db and run the existing hosted version I downloaded. I will then start by taking a directory from the Duplicator package (e.g. /wp-admin/) and replacing it in the local version to see if anything breaks in running the site (localhost) and then if it fixes the admin access. If it does eventually lead to a solution, I may come back and leave another “review” with brief details as it will be a secondary benefit for the tool! At least in my eyes.
Just making a suggestion: I cannot be 100% certain because it has been a couple of years, but when I first starting using Duplicator I think I encountered that issue (local path was appended to my localhost domain or folder name). I simply made sure the Path was left blank in Step 3, and the URL has been working ever since.
It may not be your solution but I thought I’d offer it as it’s a quick test to run.
I am offering this comment simply because my understanding of what you want to accomplish is a sequence I follow perhaps 50% of the time I use the plugin. Very often when making substantial changes to an existing website, I create a subdomain that is easy for people to remember (e.g. domain_name/test) and move (duplicate) a full copy of the original website for further development or changes. Often that subdomain is password protected.
When complete and approved, I move the new site to the original domain as you describe. Tips from my experience: delete everything from the domain site folder EXCEPT the subdomain (folder); make sure you are using two unique databases for each. Often I even leave the /test domain live for a short period for comparison. More than once I’ve had someone tell me they “remembered” something different between the test and live sites, so having the test site continue to be available for a while is a good way to keep the peace without finger pointing. Sometimes they are right, too. If your sites are very big and especially with lots of assets/content, perhaps having two full sites and databases exceeds a limit. I haven’t reached that situation yet even with economy hosting, but I have no doubts it can happen.
Thanks Ethan.
I am familiar with blocking.
My challenge will be to find the exact IP address for the one person of many who visit around the time the form is submitted. Would your PRO version track this for any form submitted?
In my experience SSL only interferes with browsers in rendering pages. And all browsers typically throw up a specific error message.
How are you using the term “local host”? Do you mean one that isn’t public (e.g. would not load in a browser using a domain name URL like http://www.mywebsite.com)? If so, it sounds like you are running some form of an intranet for limited use within a network, or something.
- This reply was modified 7 years, 10 months ago by johnwp413.
Here is my experience that may or may not be helpful. I’m just a user, but it sounds urgent for you.
I’ve moved locally developed sites to a number of different hosts where no site existed. Simply created a folder for the site (cPanel) and made sure I had a fresh database. In my experience, the installer.php has rarely failed under those circumstances. So I wonder if simply creating a fresh folder/location and database might get you to where you need to be quickly.
Have you tried installing the site backup as if new like that? My assumption is that you duplicated everything for the site without excepting media, files, etc.
Hope that helps.
- This reply was modified 7 years, 10 months ago by johnwp413.
Some feedback for your benefit – As a portion of services I provide for my clients I build and maintain websites. It may be about 25% of what I provide to them, so I am not doing it all day every day. Duplicator is a great tool, but like you say it requires at least some comfort with using cPanel and the like to set up a database. Not much more, however.
For a lot of my customers for whom I’ve built a site I suggest they use either basic backup services or managed backup services provided by their host for any routine backup. Of course, this is suggested whenever I am not routinely managing their site. These are usually accomplished without any interaction and reverting to a past backup usually requires one button click or two. So, for those who are not comfortable with the technology used in website building, it is a great option. Even discount hosts tend to have a reasonably priced solution. A few, however, I thought were too high.
Hope that helps.
I’m sure the author will have more precise suggestions, but I thought I’d share something I’ve done although not because of FTP speed issues. I often transfer the archive and the installer FIRST and immediately before activating domain.com/installer.php I delete all old files except those two.
But also in the past I have installed the localhost version in a folder or a subdomain first. That was more to have clients compare old and new. (e.g. domain.com/test_area). Once approved, it was simply a matter of deleting files and copying over all within the server environment. Very fast.
Just sharing options.
Not that I know exactly what the problem is, but here is my experience in case it helps:
When moving from hosted to local in the past I found it matters exactly how I setup my localhost. More specifically, manually for WP sites when manually installing, 7zip automatically placed the installation in a folder /wordpress/ and even when that was appended to the path there were still problems with asset/content items. By making sure all files were unzipped to a root (e.g. using XAMPP I have xampp/htdocs/Sitename ) and installing WP everything works well. In step 3 when I transfer from server to local I simply delete the path as you mentioned. All assets work or are accessible.
This has been the case on 2 separate sites for me, and perhaps a dozen or more duplication efforts as I develop the sites.
Thanks for the speedy reply.
It worked after I did the following:
- omitted the addon domain (which has always been there), which means I filtered the directory /home/originaldomain/public_html/addondomain.com (found out my client had added 2 big posts/pages to the other domain)
- ran the archive scan again and only got warning for unicode symbols (again) and not for size
- out of curiosity checked this newest archive with 7-zip and it was able to access
- ran the installer script on my local machine and it worked this time
For what it’s worth the offending characters appear to somehow be a part of a plugin called Simple Cache. It was only used as a quick fix for something, so I may revert the site to perhaps a more advanced method to improve loading/caching. Although I selected the offending files before and rescanned, for some reason it didn’t work.
Is there any other cache that is either recommended or advised against for compatibility? I will probably advance the site to something like WP Super Cache or W3 Total Cache. It will just require a little more education for the users/client.
Okay. Thanks for the reply. The standard not-a-robot reCAPTCHA is working fine for now.
Good point. I selected OceanWP because I wanted to experiment with Elementor and there is an organic tie between the two – it may not be the same team, but they seem to collaborate and recommend back and forth. As if optimized for each other. And it’s a little late to change themes at this point. At least to do so quickly.
Too bad I’ve hit this snag so far. Just cannot find the right place to discover someone who may have addressed this exact theme + tool (Duplicator) + Xampp issue before.