I have been trying for several weeks to post a question to the support communities.
No matter what device I use, or what Apple ID, I always get,
"You are not allowed to create or update this content"
I know there have been other discussions, but can't understand why.
MacBook Pro, OS X Mavericks (10.9.4), Intel 2.3 GHZ Core i7
In some cases the red banner is fictitious and can be ignored. In other cases it may be that discussion has been removed by the Hosts, or it is locked. It may also be one that has a subject line that is longer than the software (Jive) allows and the Hosts need to trim it so users can respond to the post.
The interesting thing is that I managed to post this question. Before I had posed a question, and not found an answer - and I was asked to "Submit my question to the community". I got nowhere.
This time I started a new discussion, which seemed to work.
I also managed to post the original question I had, "Can no longer share my screen Mavericks with Yosemite" and again, it may have been by starting from zero, with a new discussion.
That is strange, but a number of regulars on here keep raising questions about just what is Jive doing 😠 There are a lot of inconsistencies and all one can do is keep trying.
Timothy
Ralph is spot on in both his replies...
There are many 'anomalies' with the SiteWare (JiveSoftware.com - if you're interested) that cannot be explained and are often not reproducible.
Another 'glitch' that has been occurring in threads in which I have participated is the 'permanently broken thread' that affects a particular user - here's an example (content is not relevant, just the broken-ness for user CBFilms)
Cannot post - User ' ' is banned from posting.
This required the Original Poster affected to actually start a brand new thread to continue with the discussion - pretty serious hassle, methinks.
Can't reply to the post about my not being able to reply
The implications of my few documented cases of this becomes clear when one multiplies exponentially across all the forums and users. Pretty scary bug if you look at it in that context.
When Ralph said "ignore" - that is literal. If one just 'pushes on' it will generally result in normal behavior.
Another important thing to realize that is not published in any way by Apple/Jive is that there exists a login TimeoutLength of ±30 minutes when, if expired will log one off without any indicator (poor coding and even poorer manners), stored in a cookie that starts with initial login and is reset with HTML hyperlink navigation - seems JavaScript 'links' such as "Like", "^Go to original post", etc. don't reset the timer. There are a couple of workarounds - if interested I will reply with their details. But for most users, just 'knowing' about the timer is enough.
best regards
ÇÇÇ
You are not allowed to create or update this content
