Viewing 4 replies - 1 through 4 (of 4 total)
  • I’m the original author of this plugin, and I’m no longer in a position to provide Support (David has adopted this plugin and supports it now), but I did want to comment on one thing in the hopes that it might help you immediately.

    The URLs you show in your post above all include the “#”. The PHP functions used by the plugin would see the “#” as the beginning of the name of a section of a page.

    Whether right or wrong, I know that I never tested any situation like this.

    Plugin Contributor David Gewirtz

    (@dgewirtz)

    I agree with Jon. The standard for URL formatting is that the # symbol looks for an anchor tag on the page. So in the case of foo.com/page#anchor everything after the # is the anchor tag. If you have nothing before the #, it will look on the home/default page of the site.

    –David

    P.S. Marking as resolved because odd URL formatting that the plugin can’t resolve.

    Thread Starter Juan Gray

    (@gramcracker64)

    Thanks, this is what we assumed. Although we came close to getting it to work with some hooks, but in the end, we put the secondary theme in a different installation and linked it to the main site.

    Some diagnostic messages in place of missing divs and blank pages might be good, but as a WP dev, server admin and sometimes plugin-developer, I know of course the origins of the errors are not so easy.

    Plugin Contributor David Gewirtz

    (@dgewirtz)

    As I change code, I’ll be adding more diagnostics. So far, I’ve been avoiding too much code changing because what Jon built is virtually indistinguishable from magic.

    –David

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘Javascript requests causing theme to change’ is closed to new replies.