[Mike Nolan]

@Steven,
Not sure if this is a coincidence or not but, after updating your plug-in my page NoCorkageFees.com/submit now goes to http://nocorkagefees.com/submit/#.U2Nl1Fe27wA which is essentially a redirect to the home page… Odd, no?
I made a copy of the original Submit page here:
http://nocorkagefees.com/submit-it/ (with your submit form)

Any ideas or suggestions?

WordPress: 3.9
Multisite: No
Connections: 0.8.3
Database: 0.1.9

Thanks,

@Mike

[Steven Zahm]

@ Mike

What is the directory home page set to? Can you visit the WordPress Settings Permalinks admin page and without making any changes, click the Save Changes button.

What is adding the id to the query string after your URL/s?

This link is being reserved for Form 2.0:
http://nocorkagefees.com/directory/submit/

So I suspect it has to do with your sites specific configuration causing the conflict.

[Mike Nolan]

@Steven

The home page is set to Permalink: http://nocorkagefees.com/

To ‘see’ the current Permalink settings please see the attached JPG.
It is set to: ‘Post name’

Opened Permalinks setting page, made no changes and clicked Save. (No change)

No idea where the query string is coming from.. hoped you might.

Thanks,

@Mike

Attachments:

You must be logged in to view attached files.

[Steven Zahm]

@ Mike

Can you clarify something? The directory home page? This is different from the front page.

On the Connections : Settings admin page there is an option for the directory home page. What is that set to?

On on the WordPress Reading settings admin page, what is the static front page set to?

I can’t really help with that query string issue. It’s unrelated and likely being added by another plugin. Maybe a Jetpack module or WP Polls.

[Mike Nolan]

@ Steven

Directory home page = Directory
http://nocorkagefees.com/directory/
http://nocorkagefees.com/directory/#.U2PS2ygoYhI

Static Front Page: No Corkage Fees
Posts Page: Blog

Thanks,

@Mike

[Steven Zahm]

@ Mike

Ok, I see now … for users that decide to use Connections on their static front page and I need add url end points off the site’s root. What I’m referring to as the site’s root in the url with no pages. In your instance the root is: http://nocorkagefees.com/

One of the new endpoints is /submit/, which just happened to be a real page on your site. But because my end point rules occur before the base WordPress rules, you landed on your sites home page and since you do not have the Connections shortcode on it, you simply see the normal page contents.

I hope that makes a little sense! … If not, it think of it as name conflict between a WordPress page and a special Connections page and the Connections page just had higher priority.

Now, why did I add the /submit/ end point?

This is to support Form 2.0. So Form will not need a separate page of its own. Form 2.0 will add an action list item link above the directory named “Submit” this will take you to an internal page dedicated to Form.

So, this really isn’t a bug or an anomaly because it is by design. The only way to avoid the name collision is to remove the rule that adds this new endpoint. If you want to do that, here’s how, you need to remove lines 112 thru 114. The go to the Settings Permalink admin page and click the Save Changes button.

I hope all this makes sense and helps!

[Mike Nolan]

@Steven,
OK, this explains why after performing a roll-back on the site (to 4/30) which made the issue disappear and then updating the Connections plug-in to 0.8.3, the issue came back.

Now I could use a little clarification if you don’t mind…

Where (which file) do I remove lines 112 thru 114?

Thanks,

@Mike

[Steven Zahm]

@ Mike

The file path and name was at the top of the page that I linked to. Sorry I should have mentioned that.

../wp-content/plugins/connections/includes/class.rewrite.php

[Mike Nolan]

@Steven

Thank you, removing lines 112 thru 114 AND going to the WP admin page, Settings > Permalinks and clicking the Save Changes button, worked!

@Mike

[Steven Zahm]

@ Mike

Great to hear! I might have to reconsider adding the end points to the site root. I’ll have to see how/if this effects others. Maybe I should at least provide a way to disable the root permalinks since I’m willing to bet only a very small percentage of users actually run their directory on the front page.

[Author]

Posts