Let’s just get this out of the way first… ‘having upgraded everything to the latest versions and having paid a premium for the latest Simple Press.’  Your problem has nothing to do with upgrading otherwise all other users would see this problem but it is, in fact, quite unique to your website at the moment. And Simple:Press is free to use.

And then this one ‘PROVE this isnt a text or formatting issue’  Again I would like to know if this was using MS Word or was it all plain text because if it was Word then it proves nothing of the sort. I can not stress how important this is. Word can quite easily turn a short couple of paragraphs into a full page of hidden text. So we do need to know. 

And if this happening to not just you one thing it might be worth asking your hosting support about would be the max post size and max post variables settings in your php ini file as it might just be that what you are posting is just too big for the server to handle with current settings if they are set quite small.

Hi
100% all typed in the box on simple press, that why I put exactly as I’m doing here, I’m doing EXACTLY the same thing typing now and having no problems after hitting the “submit reply” button. 

–

Can I view that php ini via control panel or something , only I can see it taking some time to get an answer from my hosting? 

I just tried to type “I am having trouble with forum
update soon with todays info”
and it wont accept that.
Maybe someone could access my forum and test it out please?

http://bettingprofitsbulletin.com/forum/football-betting-forum/premier-league-trades/page-2/#spPostForm

On the first point then I very much doubt you can open and view the php ini file.

I have just done a search here on the ‘forum not set’ message as it pops up rarely but every now and then. There seem to be two items that crop up apart from the settings already mentioned which – as I said – might come into play with really large post content.

The first is the use of ‘mod_security‘ on your server. It seems to less commonly used recently – perhaps because of all the problems it causes so many websites – but some hosts probably still like to use it. It looks for patterns in the post data being sent to the server in a search for something malicious. If it finds a match then it essentially destroys the post variables. This fits the experience because the first post variable we check for is the ID of the forum and if it is not there you get the message you see. Basically – it just should not happen unless something has really gone wrong at the server end.

While the use of mod_security sounds useful and good, in practice it is the bane of every web developers life as it causes nothing but problems. If this IS the cause then it will come down to a specific phrase, word or combination of characters being used. But once again – you will need to talk to your host support. If they DO have it installed on your site I would ask them to disable it for you to test the theory.

The second thing that has come up in the past is simply a conflict with another WordPress plugin of some sort. And this may be more common and also something more easily checked. For example, if this problem is relatively new and recent – then does it actually coincide with installing a new WP plugin of some kind. Or maybe one that also got updated. Easy to test of course because you could just disable any other plugins and then try the post again.

Thank you

 I’ve requested my hosts provide information on mod security use.

I have lots of wordpress plugins, but this issue was there a long time ago, and reared its head again recently.
I only updated wordpress and my plugins to try and solve the problem!!

I couldn’t pinpiont a date at which it started, which is why I ask if someone could help me by going into my wordpress and having a look at the settings or otherwise, I cannot possibly go through 29 plugins and try and isolate one of them, that is just insane. 

As I said the problem doesn’t just coincide with anything, it seemed to be just when cutting and pasting but now the forum seems to be taking a dislike any particular posts. 

Maybe you could register on my forum and try and copy and paste a post from this thread for example?

I couldn’t pinpiont a date at which it started, which is why I ask if someone could help me by going into my wordpress and having a look at the settings or otherwise

It is not a matter of settings or otherwise. Something is either destroying or messing with the POST variables when they are sent to the server. This is nothing to do with settings but is, in some way, software related – either by being interrupted before being sent (as some so-called WP ‘security’ plugins have been known to do) – or by being destroyed after arrival.

I cannot possibly go through 29 plugins and try and isolate one of them, that is just insane. 

Then we may never know if one of them is the cause.

As I said the problem doesn’t just coincide with anything, it seemed to be just when cutting and pasting but now the forum seems to be taking a dislike any particular posts. 

Once again please let us get the language correct. The forum is not ‘taking a dislike’ to anything. Your web server is.

Maybe you could register on my forum and try and copy and paste a post from this thread for example?

As a matter of policy we do not register on our users websites. If you wish to create a temporary account for us to use then please PM credentials to both myself and to ‘Mr Papa’. Please include in the PM a link to your site, a link to this thread and brief reminder of the problem. 

But – I am not sure what evidence doing so could provide. If it is a conflict with another WordPress plugin the only way to find out is to disable them. Which you have already discounted as apparently an insane thing to do. Even though, of course, this is the sort of housekeeping that people who run websites have to do from time to time.

Ok, so it wasn’t as bad as I first thought. I turned off (deactivated)every single plugin but simple press.

Still getting same result. 

I will get back to you with login details of guest account etc in a while, thank you.(should it be necessary) 

I just got this response from the host :

Yes, we have a mod_security module installed for increasing the security of our servers. Its activity may cause some issues from time to time, when requests sent to the server match with mod_sec rules. Sometimes such requests are false-positive. It is not recommended disabling mod_security module completely, for it may cause security issues for your account. However, if it is a mod_security, which is causing the issue on your website, we can find certain mod_security rules, and disable them for your account.

In order to find out the caused of the issue, and resolve it, please provide us with more details. Where exactly do you see the error? Please provide us with step-by-step actions to re-produce it from our side.

I am going to provide them with a link to here and ask them to copy and paste my Premier League bets stuff to my forum see if I can make progress on this. 

unfortunately, mod_security is known for false positives and you can find bunch of topics in wp support forum… If mod_security is incorrectly blocking it, they will be able to look at the logs and whitelist the problem…

Got the following reply from the host:

This issue was connected with peculiarities of content of post submitted by you. Content of your post was compared with the patterns stored in the database of the firewall and it was falsely assumed to be a SQL-injection attack. We have turned off a corresponding rule on the server. Please try to submit your post again.

Which appears to have resolved the issue, at least for now.

I appreciate your help on this guys.
May I suggest that this issue is pinned outside the paid for area for future reference?
I cant be the only one with this hosting issue, and its frustrating wasting your time and my money for no reason, updating from a perfectly acceptable and working version of the forum, all to try and resolve an issue which had nothing to do with the forum software or wordpress. 

glad to hear its resolved.  Thanks for the update!