Unable to edit post in "Sell"

Jimbo has actually experienced the same thing in one of his threads. At first I thought it was the quantity of images in his thread that was the problem, but maybe it's the quantity of BBCode? You don't seem to have as many images as he did, but you definitely have at least as much BBCode. We haven't been experiencing this problem with any posts that are short or contain little imagery/bbcode.

I'll submit a support ticket, but I'm not sure if there will be a long-term fix. I'm not really sure what the underlying cause is (I'm just hypothesizing).

Does it get better after a while? I still can't edit the OP of my buy or sell threads. I just tried, and it will let me edit that history bump post now but still no luck with either OP.

This is the first time I've run into this problem. That sell thread is a week or so old and has had about that much content since day one. That buy thread is over two years old. Yes, it's a lot of code, but it's been a lot of code for two years without issues before. :/


I know it's not a good thing, but I can't help but feel a little proud to think, "I broke Guru with bullet lists!!!"

Hi,

I'm unable to update my thread (here : http://www.guildwarsguru.com/forum/c...t10486539.html)
Every time I try to update, I get a 500 internal server error.
I was able to update an old bump (end of page 4), but still can't update 1st message.
Is this happening to you ?
I have been trying for 3 hours now, and even if I remove a part of my items list to make the message shorter, I get a 500 error.

Is there a (new?) limit to the size of a message ?
If this is the case, this would need a correction of either the size limit, either the ventary rules that won't allow me to have 2 threads if my items list can't fit in one.


Since I probably won't be able to update until tomorrow, I have another question : I have been updating my thread for 6 months, and my thread has 13 pages.
I am sometimes under the impression that people don't look at it as much as they did, meaning that most of them prefer looking at a brand new threads than at a several-months old, several-pages thread even if that thread has been updated with many new items.
Do you think I should start a new thread instead of updating the old one in order to have a better chance of selling things ?

Yes, the same 500 error is happening to me, too. I asked about it in Site Feedback at this thread earlier today. It's frustrating, as people keep whispering me about stuff that's already bought or sold - I feel bad wasting their time like that, but I can't change the OPs of my Sell or Buy threads.


As far as long-running vs. short threads, I think it's a matter of choice. Personally, I like to keep a long-running buy thread, as I get the impression more people are likely to remember vague things about the weird stuff I'm buying ... at least enough to make them consider finding my thread in their subscription/bookmarks to check details of new loot they get. For Sell threads, I prefer short-running ones. There are a few folks with long-running sell threads that do seem to do well that way. Buyers get used to them and check back there first when they're looking for new stuff. If you're always selling a rolling stock of the same kinds of gear a steady thread might help sales from repeat customers. If what and when you're actively selling varies a bit, I'd think you're better off with shorter threads. When browsing Sell, I will often skip past a thread I've seen in the past few days unless there's something really striking about the title or the mouseover to alert me there is new stuff to see in the OP. Newer threads get lots of new views, but I'm not sure they automatically get lots more sales from all those views.

Curse is looking into it, however they can't identify the cause of these errors.
The most I can offer is to help by splitting posts up so you have an additional post below your OP. If that's something you'd like, please let me know.

It seems to have fixed itself overnight, but please let us know if it starts happening again so that we can poke the devs.