1 saunders Jun 01, 2015 22:01
3 fplanque Jun 02, 2015 21:05
This should be fixed on GitHub, specifically in this revision:
https://github.com/b2evolution/b2evolution/commit/9f9f03855ca20e2db4e76dff86bf117dd47e24b2
does that help?
4 saunders Jun 02, 2015 21:40
Thanks; the form is now ok
But after submitting the data, I get the following message
"You don't have permission to access /blogs/htsrv/comment_post.php on this server.
Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request."
The folder attributes are 755, of the php file 644
The same happens when calling the preview.
5 mgsolipa Jun 05, 2015 08:44
6 saunders Jun 05, 2015 10:35
I cleared all caches, the system and browser ones. Nothing changes. I upgraded from a previous version (5.2.2 stable) - there this bug did not happen. I am using bootstrap (before asevo) - you can check the phenomenon: <code>http://www.genba.org/blogs/index.php/politpropaganda/oevp-bernhard-baier-besinnlich</code>
Now there are also problems with plugin sharethis:
Notice: Undefined property: Item::$ptyp_ID in [....]/blogs/plugins/sharethis_plugin/_sharethis.plugin.php on line 126
Thanks and regards, will
7 fplanque Jun 10, 2015 03:37
> You don't have permission to access /blogs/htsrv/comment_post.php on this server.
This is not a b2evolution issue but a linux file permissions issue.
8 saunders Jun 10, 2015 20:32
I checked permissions: 0755 so this should not be responsible
All worked fine in former version 5.2.2 - and I did not change any permissions while updating to 6.4.3.
9 fplanque Jun 10, 2015 21:59
Seriously, you should ask your host about this. This error message is NOT generated by b2evolution but by the webserver. It says you don't have permission to access the PHP file. It is really out of the reach of b2evolution and 100% within the reach of your web host.
(Or it's an old error message that is no longer reflecting the reality but you have it in your browser cache somehow)
10 saunders Jun 11, 2015 16:56
We had to fix the .htaccess file. Tracking by the web host led to it. It is fixed and working.
Thank you very much for your support and excuse me for occupying your time.
And THANKS to your great and awesome work at b2e
will
We'll check this today.