gd_place redirect from buddypress

This topic contains 5 replies, has 2 voices, and was last updated by  Paul 6 years, 7 months ago.

We have moved to a support ticketing system and our forums are now closed.

Open Support Ticket

Tagged: , ,

  • Author
    Posts
  • October 9, 2017 at 5:44 pm #399655

    Paul
    Lifetime Member
    Post count: 139

    When users are logged in (non-admin) and attempt to go to their profile or any buddypress feature (messages, all members, etc…), it redirects to: https://www.thero.org/?geodir_dashbord=true&stype=gd_place. This URL looks like our home page.

    We have “Buddypress Members Only” to lock down those features for non-logged in members and deactivated that to test, and the redirect resolved.

    We can’t tell if it is “Buddypress Members Only” forcing this redirect, or GeoDirectory, but the fact that it goes to a gd_place was suspicious. We are posing this question/issue to Members Only also.

    Thanks for your thoughts on this.

    October 9, 2017 at 8:01 pm #399675

    Paul
    Lifetime Member
    Post count: 139

    Our site name is https://www.thero.org/

    October 10, 2017 at 12:09 am #399739

    Paolo
    Site Admin
    Post count: 31206

    Hi,

    please provide admin credentials and we’ll have a look at your settings.

    Let us know,

    Thanks

    October 10, 2017 at 12:35 am #399741

    Paul
    Lifetime Member
    Post count: 139
    This reply has been marked as private.
    October 10, 2017 at 12:40 am #399744

    Paul
    Lifetime Member
    Post count: 139

    We’re also experiencing a couple other problems related to geodirectory, such as:

    1) Listings mysteriously being in draft form, even though they have already been published.

    2) Some of the Buddypress profile field titles not showing on profile due to being white.

    Not sure if these are related, but thought I’d mention them just in case.

    October 10, 2017 at 1:06 am #399751

    Paul
    Lifetime Member
    Post count: 139

    Hi Paolo,
    We just realized that this may be a waste of your time right now. It seems the plugin that is causing the conflict may not be supported anymore. We are researching a bit more and testing a new solution. We will get back to you within 24 hours to let you know if our problem persists with the new solution we find.

    Thank you for your patience!

  • Author
    Posts
Viewing 6 posts - 1 through 6 (of 6 total)

We have moved to a support ticketing system and our forums are now closed.

Open Support Ticket