August 25, 2014 at 8:19 pm 25847
I’m seeing the same error jmdezigns says also without WOOCommerce. For example, I see:
I’m using WP Project Manager PRO 0.5.3 and WP Project Manager – Frontend 1.2.1 with buddypress and other several plugins.
None of the fixes/workarounds suggested on this thread fix them, as they seem to be all applied in these versions (change 10 to 99 in /includes/functions.php is already done in my version, for example).
Do you have any idea how can I further debug this ?
Thanks a lot
September 3, 2014 at 5:44 pm 26247
September 4, 2014 at 9:12 pm 26319
Is that the only option ? I’d like to try some other way first, if possible. I find doing that kind of invasive. I received by email a reply asking for the plugins installed. So, can I just give you that now ? Giving admin access seems like too much as a first step IMHO.
So, just in case the list of plugins is useful, I’ll tell you that I’m using wordpress from debian stable and the plugins installed are:
add-meta-tags/ version 2.4.3
If you want me to test something in particular, just let me know! 🙂
September 7, 2014 at 2:18 pm 26390
If disabling the other plugins help, you’ll have to check one by one to know which one is causing the problem.
September 13, 2014 at 7:14 am 26735
The problem seems to be the WP Project Manager plugin. I disabled all the plugins except for:
WP Project Manager – Frontend (version 1.2.1)
Even then, when I go to a URL like: /\
So it seems the plugin is having problems with wordpress itself. I’m using wordpress 3.6.1+dfsg-1~deb7u4 from debian stable.
Is there some other test that can help you fix the bug in WP Project Manager ?
September 13, 2014 at 8:02 am 26737
Sorry, the URL is not showing. Something like: /how-phplist-helps-you-follow-canadas-new-casl-spam-law/feed/
September 14, 2014 at 6:45 pm 26785
September 18, 2014 at 7:45 pm 26987
It’s not an option for us to upgrade wordpress. We use debian stable and we want to use that. And we are using the latest version of your plugin (check the versions I posted and let me know if it’s not the last one).
What can I do to use the plugin on debian stable without errors ?
September 22, 2014 at 4:25 pm 27182
Go to your permalink settings and set it to post name and hit save; even if you have already set the permalink to “post name”. See if the issue solves or not. And please check you have the latest version of MySQL and PHP.
September 22, 2014 at 8:38 pm 27209
I had it already set the permalink to “post name”. I hit save anyways and didn’t changed a bit (the error is exactly the same). It didn’t resolve the issue.
Any other idea ?
September 24, 2014 at 6:29 pm 27430
Please provide your site login credentials in a private reply. I will have a look about what is going wrong there.
September 25, 2014 at 12:35 am 27468
Again, I’d really like to avoid that. It seems too invasive. Can’t you just tell me what do you want to try or run something with debug so you can further understand what the problem is ?
September 25, 2014 at 8:47 pm 27538
How am I supposed to write about the hundreds of tests we do to check? I can not suggest you anything without having a look.
September 25, 2014 at 9:38 pm 27540
Can you suggest a safe way to do this, then ? Regarding our users (like hashes for passwords, etc.) and general safety