AlanOldStudent

I forgot to mention this. I can create a test post, and as long as I save it to draft, I can click on “preview” and see it there. But if I try to publish it, the link goes to a 404.

Should I send you the install log? I’m not good at interpreting it, but nothing I saw raised any red flags.

Alan

Cory,

Thank you for going in and checking this out. I agree with you. This is probably an issue with my theme, and a minor one at that.

I appreciate your follow through. You have a super plugin.

Regards,

Alan OldStudent
The unexamined life is not worth living—Socrates
Gracias a la vida, que me ha dado tanto—Violeta Parra

Hi Cory,

I just backed up the site and sent you all the stuff you need to be able to troubleshoot.

For those who are browsing this thread: The delay came about because Cory needed some information to be able to access the CPANEL and administrative panel of this site, and I got slammed with work and was unable to supply those for a while.

Regards,

Alan OldStudent
The unexamined life is not worth living—Socrates
Gracias a la vida, que me ha dado tanto—Violeta Parra

I just submitted a ticket. Thanks for your help

Regards,

Alan OldStudent
The unexamined life is not worth living—Socrates
Gracias a la vida, que me ha dado tanto—Violeta Parra

I posted the above 2 weeks ago, and VIPRE still blocks your site at https://otwthemes.com/. I don’t mean to be a nudge, but perhaps you should look into this. VIPRE is a long-time security suite and firewall, and their support can be reached here.

It’s bad theater to not act on this for two weeks.

Regards,

Alan OldStudentThe unexamined life is not worth living—Socrates
Gracias a la vida, que me ha dado tanto—Violeta Parra

As a quick aside, if you have WordFence installed on a site, be sure to deactivate it before running Duplicator. When I didn’t deactivate WordFence first, I was unable to restore the site on my local WAMP server. You can always reactivate the WordFence plugin on your live site after you’ve created the Duplicator packages.

Regards,

Alan OldStudent
The unexamined life is not worth living—Socrates
Gracias a la vida, que me ha dado tanto—Violeta Parra

Thanks Cory,

This answer is in response to you but also for others who may have a similar problem.

There were 2 problems:

1. The Duplicator plugin seemed to be having problems recognizing paths that I wanted to exclude.
2. I had installed the “Tacoma Socialist Website” using BlueHost’s automatic install facility. So it went into the root directory. When I installed “15 Now Tacoma” website, that went into a subdirectory under the root directory. I developed that site on a WAMP and used Duplicator to make a package, which I used to migrate to the BlueHost shared server. That is where the WordFence plugin was located.

My solution was three-fold

1. I downloaded the developer version of the Duplicator plugin you had advised Goretex 34 to use.
2. When creating a package for “Tacoma Socialist Network” website (which is in the root directory), I carefully excluded the entire path for 2 other sites in 2 separate subdirectories (one of which was the “15 Now Tacoma” website containing the WordFence plugin).
3. When creating a package for the “15 Now Tacoma” website, I excluded the path to the …plugins/wordfence subdirectory.

Lesson learned: If you have your main WordPress site in the root directory and several sites in subdirectories, be sure to exclude the paths to the subdirectories unless you intend to do otherwise.

Regards,

Regards,

Alan OldStudent
The unexamined life is not worth living—Socrates
Gracias a la vida, que me ha dado tanto—Violeta Parra

I came with a related problem. I have a BlueHost account site here: https://www.tacoma-socialist-network.org.

I also have 2 add-on accounts. One of them is https://15nowtacoma.info.

On the 15 Now Tacoma site, I recently installed WordFence. When I backed up that site via Duplicator, I got the large-file warning message. Nevertheless, was able to restore it on my local WAMPSERVER via Duplicator

I didn’t install WordFence on the main Tacoma Socialist Network site, but when I ran Duplicator, I got large-file warnings, referring to my WordFence installation on the add-on site (15 Now Tacoma

Moreover, I am unable to exclude the WordFence directory.

I hope I’m clear. Please advise.

Thanks Buzztone. I appreciate the information and help.

Regards,

Alan OldStudent
The unexamined life is not worth living—Socrates
Gracias a la vida, que me ha dado tanto—Violeta Parra

It looks like I can’t edit posts. I just discovered that I don’t have this problem in Chrome or IE. I cleared my cache and cookies for the localhost (wampserver), and still no joy. I ran FF in safe mode, still same problem.

Hello Anmari,

Thanks for coding this plugin. I’ve gotten it to work for me, and I hope I can put it to good use. It is very clever, and I spent some time looking for something like this.

However, I found the instructions for getting the plugin ID to be confusing.

You wrote:
1) enter some garbage in the shortcode [do_widget wtf] and the plugin will offer you a try debug (if you are admin and logged in that is)
Click on the “try debug”

In a word, “No.” There was no offer to debug and no “try debug” button.

Elsewhere, you suggested hovering over a widget in the widget area to get the ID. That works no better than the suggestion listed above.

You also wrote:

2) else add ?do_widget_debug=1 to the url of the page where the [do_widget] shortcode is [–]
either way you should see a list of stuff

That did work, but it’s really clunky.

You also wrote this:

Lots of effort went into writing up detailed instructions both on the main wordpress page and in the settings page. Please read them before posting a support question – it would be more respectful of peoples time

I’m sure you did put in a lot of time into this. I also put in a lot of time trying to figure out how to use this plugin. After much frustration, I did.

I googled “wordpress assigned ID,” and browsed through your site(s). Then, I happened upon the above message. When I read those words, it felt yucky to me. Not everyone who has trouble understanding your documentation is a blithering idiot.

Maybe you could find some way of making the ID’s more evident by incorporating a bit of your debug code in a future version of this plugin.

<p>Regards,</p>

Alan OldStudent
The unexamined life is not worth living—Socrates
Gracias a la vida, que me ha dado tanto—Violeta Parra

When I click on the green WAMPServer icon, hover over PHP, then hover over PHP extensions, the php_curl has a checkmark next to it. I don’t know about checking if Curl with SSL is enabled.

What I do know is that another installation of WordPress in the same WAMP folder works, but it is version 4.0

So, that leaves me with a few questions:

1. How would I check for SSL?
2. Why does Version 4 of WordPress work but not version 4.1?
3. How can I fix that definitively?

Thank you for the useful link.

Regards,
Alan

Okay, I’ve got several WordPress installations on my WAMP server, one of which is 4.0 and the other 4.1. I am having all the above-mentioned problems on the 4.1 website but not the 4.0.

As far as I can tell, cURL is enabled.

After spending some hours searching various threads and suggestions (including this thread), the problem still exists. I need to get the new website developed and on-line in a week.

Can someone tell me what I can do to fix this definitively? Do I trash my WAMPServer installation and start again? I looked for an old 4.0 installation file, but I can’t seem to find it.

Regards,
Alan

Thanks for the info and the help, Khromov

Regards,
Alan

That seems correct, Khromov. Sometimes Javascript doesn’t work, and I tried your plugin so that I didn’t have to rely on Javascript. What happens if my browser (Firefox, notably weird with JS and Flash) decides not to work?

Regards,

Alan