savedbygrace979

Well I answered my own problem. It appears my .htaccess file somehow was corrupted and the permissions were changed (by the webserver somehow).

I uploaded an old backup copy of my .htaccess file and changed the permissions back to chmod 755 and now the dashboard menus and dashboard are displaying correctly universally.

If I had waited another five minutes I would not have needed to post this. At any rate I’ll close the issue but hopefully if any others have this same issue this will help them in some way.

I’m having this exact same issue as well. Where my forms were working perfectly previous to WP 3.4.1 anc CF 3.2.1 and now after WP update to 3.4.1 it is producing the 404 errors.

I already did that, all the contact forms are there and the id’s are correct. I manually verified that the shortcode contains the id of the correct contact form. I also re copied the shortcode from the forms that were already there and the same problem. Everything was working perfectly fine before the WordPress update, afterwards it is broken. I’m not about to revert back to the previous WordPress version to get this to work.

I fixed this myself and am deactivating and deleting this plugin.

I haven’t done anything wrong with the restrictions. The only thing I have done is to create a new role with the default capabilities as the subscriber role. I also created the special role _Visitor to restrict the category I desire for those visitors who are not logged in. The only restrictions that were modified at all were those for the _Visitor role. While this did hide the post under that category, creating a 404 not found error page. Restricting access to all posts in this category is not inclusive of all posts underneath it in the hierarchy. I tested this by first only restricting the category for _Visitor and navigating to this post in a separate browser window logged out and was able to view the post. Next I restricted one of two posts in the category as well as the category itself, and the one post I manually restricted was hidden the other was view-able. This shows that the category restriction is not inclusive at all.

As for your comment about me rushing to make comments about the plugin before experimenting with comments or looking up documentation. This was the very last thing that I did after finding out that the plugin has very little if any documentation, experimenting with the restrictions and settings to try and fix the problem myself, searching the support forums for others who had the same problem and were able to fix the issue. I have multiple websites that run WordPress and have used it for years, I am no novice at working with WordPress, so I don’t appreciate being treated as such.

The fact that you supposedly haven’t had any complaints regarding your plugin over the last month has nothing at all to do with the problem and questions I have regarding the plugin. I was quite specific in stating what problems I was having with the plugin and had a few simple questions about how your plugin blocked posts, which I had to ask here as you have no real documentation that explains anything about your plugin.

I didn’t contact you directly as any resolution of my particular problem may in the future help another user if documented here and would not help any others if kept in private correspondence.

At this point I see what level of support I would be getting by using this plugin and am deciding to use something else that has better documentation and more cordial support.