jon

This is not a WordPress question. And the answer depends on where the Mail Server is hosted.

You need to contact your web hosting company to get an answer on this. They likely have this described in their support documentation on their web site.

Now that I’ve had a chance to review your problem, there are two ways that we can work together to resolve it:

1. Change how you do the Redirection to one more compatible with the plugin; or
2. Get enough detail from you to exactly re-create your situation on my test system and see if it is feasible to fix the plugin

Choice 1 would involve you switching to this method of using a Folder to look like at Root install: http://codex.wordpress.org/Giving_WordPress_Its_Own_Directory#Using_a_pre-existing_subdirectory_install

I have used this method for years and strongly prefer it to other methods, based on how compatible it appears to be with “everything else”.

If that is not an acceptable solution, please respond here and we’ll work together on Choice 2.

So glad it works. These are only workarounds and they don’t work for all Themes.

The plugin was not designed with this much flexibility, so it will require a little more work on your part.

But first, I must make sure that you ONLY want to look for a Word when it is the FULL directory/folder name. For example, /1warmup/, /warmup1/ and /1warmup1/ would not be selected using this approach.

Here is how you would it. For each word, you would need multiple entries. In the “For An Individual Page, Post or other non-Admin page; or a group of pages, specified by URL Prefix, optionally with Asterisk(s)” section of the Settings for the plugin, select “URL Prefix with Asterisk (“*”)”, the desired Theme, and:

1. http://mysite.com/*/warmup for the first entry;
2. http://mysite.com/*/*/warmup for the second entry;
3. http://mysite.com/*/*/*/warmup for the third entry;
4. and so on, as deep as you want to go

Obviously, if /course/ is always the first level folder/subdirectory, then replace the first asterisk in each of those entries, making #1 “URL Prefix” since there is no asterisk in the entry.

Version 2.14 has been released. It includes this and some improvements to the Settings page.

Please let me know if you run into any issues.

One word of warning: wpengine.com seems to disable caching and perhaps some other functionality in its wpengine-common plugin on the staging system you are on. That means you will also need to do some testing on the live site, too, to be sure that caching will not change anything.

I have found a solution that works during initial testing on the test site that you provided. It appears that the “template_redirect” Action is either not being triggered or my plugin’s registered action is someone being deleted by one of the wpengine mandatory plugins. I simply switched to the next Action in time sequence, get_header, and that works.

I will release a new version of the plugin in the next few hours, and encourage you to test it more fully.

As always, if you or anyone else reading this runs into any problems, please let me know.

After a quick search, I could only find one plugin that has this functionality: https://wordpress.org/plugins/prevent-concurrent-logins/

But don’t let me discourage you from looking in more detail.

One word of warning: my experience with WordPress is that the majority of users do not logoff. This creates a problem if that user uses multiple “devices”. For example, I could easily see me turning off my Desktop computer (without explicitly logging off), going somewhere and not being able to access my WordPress site from my smartphone, because WordPress still considers me logged on at home on my powered-off Desktop.

In other words: are you sure you want to do this?

I have been unable to re-create this error on my test system using all of the plugins (except wpengine-common) you list. Obviously, I cannot be sure that all of the settings of all the plugins are the same, but I made an effort to put in “real life” settings into each.

The two most obvious ways to go at this point are one of the following:

1. I approach wpengine.com for a free account for testing now and into the future; or
2. You provide URL, ID and password for BOTH your site’s WordPress AND FTP (I need FTP so that I can easily change the code in my plugin to rapidly add and remove debug statements (var_dump() typically))

Please respond through this contact form: http://jonradio.com/contact-us/

That will avoid any possibility of posting information that could pose either security or annoyance risk.

Again, thank you for your patience, but it gets very difficult when I cannot re-create a reported error on my test systems.