Latest Update Caused Infinite Redirect

  • Resolved Garrett Hyder

    (@garrett-eclipse)


    6 years, 7 months ago

    Hello,

    I just wanted to raise an issue we recently came across with the latest plugin update (2.3.1) as it caused all our property pages to break displaying a infinite loop error.

    Diving into it I found the system had forced the property permalink slug to change from property to properties and it had created 3 pages in the system called Properties;

    View post on imgur.com

    After discovering this I found we had 301 redirect from properties to property, but then WP-Property had introduced a redirect for property pages to properties which explained the infinite loop.

    To resolve this I went into the WP-Property settings and found the ‘Default Properties Page’. Initially, I removed the extra pages from the database leaving one and went to change it’s slug to property and found after doing this returning to WP-Property settings page that yet another Properties page was auto-generated. So to actually stop this and remove the excess pages I had to change the ‘Default Properties Page’ and save. After that I could cleanup the excess pages.

    Hoping that helps others fix their slugs and redirect issues.

    As to avoiding this in the plugin would be advised to prompt before creating pages like that as well as warning admins about this type of change as it’s potentially breaking whenever you change permalink structures.

    Thank you

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Contributor MariaKravchenko

    (@mariakravchenko)

    Hello, Garrett.

    Thank you for sharing your experience. Is that issue still provides you inconvenience? That change was done not to force people using post type for permalinks and we mentioned that change in our changelog.

    Was property page somehow hardcoded in your plugin or theme? We developed that change in a way to softly change property to properties page, so described behavior shouldn’t be common. Let us know.

    Regards.

    Thread Starter Garrett Hyder

    (@garrett-eclipse)

    Hi @mariakravchenko,

    We had a redirect from properties to property from the original configuration so as to use the post_type as the permalinks slug. So with the switch the redirect loop was introduced so sorry we overlooked the note in changelog and hadn’t realized we’d have to update the slug for that page.

    The weird part though was multiple Properties pages were being created by the plugin due to the setup_default_property_page. So it might have been a race condition or something but basically had to ensure I’d specified a page as the base in the new setting before pages would stop being spawned so it seemed the check for that setting worked but the check for does the page already exist wasn’t successful.

    I wouldn’t be surprised if other users have similar experience with this update.

    Thanks for looking at this,
    Cheers

    Plugin Contributor MariaKravchenko

    (@mariakravchenko)

    We had a redirect from properties to property from the original configuration

    You meant something custom on your site or that was you are determining an issue?

    Thread Starter Garrett Hyder

    (@garrett-eclipse)

    Hi @mariakravchenko, Yes the redirect was custom to route users to the original wp-property slug which then changed and required us to go and change. I understand why it was done I was just thinking an alert would be nice for such an impacting change.

    Also the actual bug I was tryign to raise was the fact that multiple Properties pages were spawned by the plugin instead of just the single one needed.

    Plugin Contributor MariaKravchenko

    (@mariakravchenko)

    yea, I also tried to replicate that. But it seems that could happen only if something custom was done with old property page.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Latest Update Caused Infinite Redirect’ is closed to new replies.