• Resolved pizzapie79

    (@pizzapie79)


    Hi, I have already used your plugin many times so I’m sure it works pretty well, but now I have an issue on a website in development: when “WP Better Permalinks” is active, every CTP and custom taxonomy page returns 404.

    Now, like I said before I’ve already used your plugin many times on “real” website, but it seems it does not work on my website in development; could it possibly be because the site is in a subdirectory (like https://www.mydomain.com/mywebsite)? Maybe you’ve had a similar problem with sites in subfolders before?

    Thanks in advance ??

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author Mateusz Gbiorczyk

    (@mateuszgbiorczyk)

    Hi @pizzapie79,

    Thank you for your message.

    We haven’t tested this solution, but I assume that after the development phase you change your website URL and the problem will not occur? I’m concerned that directory handling in the plugin code would require major changes and could potentially cause problems for other users.

    I hope you understand – thanks for reporting anyway.

    Best,
    Mateusz

    Thread Starter pizzapie79

    (@pizzapie79)

    Hi, really thank you for your reply.

    I understand your point, and honestly it’s not a big deal if this issue can’t be fixed; I just wanted to know if you had already encountered this problem with other websites in subfolders. But I’ll guess I’m gonna check it by myself at the end of development phase ??

    I’ll let you know if the issue is fixed after moving from subfolder to root, ok?

    Thanks again!

    • This reply was modified 6 months, 2 weeks ago by pizzapie79.
    Plugin Author Mateusz Gbiorczyk

    (@mateuszgbiorczyk)

    @pizzapie79, I’d appreciate your feedback once you’ve moved to your target domain.

    Thread Starter pizzapie79

    (@pizzapie79)

    Hi, it’s me again ??

    I finally moved the website to the production domain and now I can confirm that your plugin is working well as usual. So, it seems the problem was REALLY caused by the fact that the website was in a subfolder.

    In the end, like I said before that’s really not a big deal since the plugin works normally in production, so there’s nothing to fix. However, I suggest posting a note about this small issue in the FAQ section, just to inform other users who might have this same problem.

    Thanks for your support and for your nice plugin ??

    Plugin Author Mateusz Gbiorczyk

    (@mateuszgbiorczyk)

    Thank you for the information @pizzapie79!

Viewing 5 replies - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.