이 토론은 잠겼습니다.
Wic 2015년 2월 11일 오후 5시 30분
Can't post a review [SOLVED - write it short and then edit it]
So basically the review I wrote was around 7500 characters long and when I hit the button to post it, the button just disappeared and nothing else happened. Is there any limit to how long it can be or any other explanation to this? (or possibility that's being controled or something?)
Wic 님이 마지막으로 수정; 2015년 12월 30일 오후 6시 00분
< >
94개 댓글 중 61-75개 표시
METAL 2015년 12월 2일 오전 6시 45분 
was having the same issue as well today. but this really worked by just writing something small (i just wrote "test") and post it. then press "edit" and i put in my entire review in and got posted very quickly.
elderbax 2015년 12월 2일 오전 10시 23분 
Solution bump (for visibility on the new page of this thread):

Haki "Grey-Røck" Belegarssøn님이 먼저 게시:
I have a workaround: Just post "testing" or something short in review box, and then edit your review, put the long texts in.

Like METAL says, this really works.
KillerofGods 2015년 12월 2일 오후 1시 54분 
DaRealPeil님이 먼저 게시:
Solution bump (for visibility on the new page of this thread):

Haki "Grey-Røck" Belegarssøn님이 먼저 게시:
I have a workaround: Just post "testing" or something short in review box, and then edit your review, put the long texts in.

Like METAL says, this really works.
Worked for me as well, thanks for highlight his post!

And thanks to Haki for posting it up! :D
crunchyfrog 2015년 12월 6일 오후 2시 06분 
gibbousmoon100님이 먼저 게시:
crunchyfrog님이 먼저 게시:
I'm afraid this is quite common - it's happened as long as reviews have been a thing (and longer).

It's simply the old problem - net/server congestion and/or hiccups.

It's no different to when you try to view the Store page around sale time and it just loops back to the previous page, or you try to make a purchase and it jumps back to the front page.

So, sorry, but for the future ESPECIALLY if you write long reviews, I'd thoroughly recommend highlighting and copying your ENTIRE text before pressing post. Then if it doesn't work, or jumps you to another page, you can simply paste it back in.

That's a trick I quickly learned on here ;)

This may be correct some of the time, but it definitely isn't correct information for many of the posters in this thread.

The problem is (mostly likely) Valve's astounding inability to create a simple line of code that will inform the user when a problematic character is part of his/her review. Furthermore, such problematic characters only seem to affect the initial post; subsequent edits are not affected.

Therefore, the most effective workaround for users experienced with this issue is simply to write and publish a one-word review, edit it, and then paste in the entire review.

If I were Valve, I'd be super-embarrassed by this bug, but Valve thinks they can do no wrong, so really, is anyone surprised that they aren't?

Please don't put words in my mouth.

I offered my few pennorth based on experience and evidence. Please do not make sweeping claims like if you dissent with me, you think Valve do no wrong - that's just silly.

Although I do concur that IF it is as you say - a rogue character(s) - then it is odd it hasn't been sorted, but the downside here is that Valve don't let things be known one way or the other, for right or wrong, and it can be bloody frustrating.

Just out of curiosity, has anyone on this thread made a support ticket detailing the issue, and got past the first filter/canned response?
Xver.Mar 2015년 12월 6일 오후 2시 08분 
Hej
gibbousmoon100 2015년 12월 6일 오후 9시 12분 
crunchyfrog님이 먼저 게시:
Please don't put words in my mouth.

I offered my few pennorth based on experience and evidence. Please do not make sweeping claims like if you dissent with me, you think Valve do no wrong - that's just silly.

Likewise--I make the exact same request of you. By saying that I put words in your mouth, you are putting words in MY mouth. Since I never even *mention* you (I only reply to you), it is impossible for me to have done so. Re-read my post, please.
crunchyfrog 2015년 12월 9일 오전 3시 50분 
gibbousmoon100님이 먼저 게시:
crunchyfrog님이 먼저 게시:
Please don't put words in my mouth.

I offered my few pennorth based on experience and evidence. Please do not make sweeping claims like if you dissent with me, you think Valve do no wrong - that's just silly.

Likewise--I make the exact same request of you. By saying that I put words in your mouth, you are putting words in MY mouth. Since I never even *mention* you (I only reply to you), it is impossible for me to have done so. Re-read my post, please.

Then you're confusing what I said. You responded to me by quoting me in your response. Why would you do that if you weren't referring to me?

In any case, my point stands, as does yours, so best we leave it here
elderbax 2015년 12월 9일 오전 7시 06분 
ffs guys get a room; this is a thread about fixing an issue, not creating new ones.
Mern 2015년 12월 11일 오후 3시 32분 
I tried to post a review, didn't bother copying and pastying it somewhere else because I thought there was no problem in regards to Steam reviews but hey.. lost an entire review. ♥♥♥♥ you Steam.
crunchyfrog 2015년 12월 23일 오전 9시 36분 
Raoul Duke Doctor of Lemonism님이 먼저 게시:
Still no fix yet? I'm having a similar problem, except I'm getting "there was a problem posting your review". Also, for some reason, my other 4 reviews are gone. I can only think that those have to be related in some way. I only hope their not gone for good :steamsad:

If you're having trouble viewing other reviews today then note the date - we're into the Winter Sale. ALL of Steam will be spotty because of the sheer weight of usage.

It's quite common to suffer incorrect viewing of the store page, your profile, your inventory (which can also appear to be completely empty), and much more.

So, I'd urge you to take caution before assuming these are related to THIS issue.
jackd23 2015년 12월 30일 오후 2시 11분 
This is still a thing, ... what the. It's a testament to incompetence, that the simplest things just don't work.

Not saying that the "solution" in the title doesn't work, it's just... you know. It's pretty disappointing that after spending a fair amount of time on a review (saved in Notepad before posting, always a sensible approach), the "Post review" button simply disappears.

Then, frustrated and upset, search for "can't post steam reviews" to find "this", because I have another saved one from weeks before that I couldn't post. Way to say "be less elaborate" ;p

:steamsalty:
gibbousmoon100 2015년 12월 31일 오전 12시 38분 
jackd23님이 먼저 게시:
This is still a thing, ... what the. It's a testament to incompetence, that the simplest things just don't work.

Not saying that the "solution" in the title doesn't work, it's just... you know. It's pretty disappointing that after spending a fair amount of time on a review (saved in Notepad before posting, always a sensible approach), the "Post review" button simply disappears.

Then, frustrated and upset, search for "can't post steam reviews" to find "this", because I have another saved one from weeks before that I couldn't post. Way to say "be less elaborate" ;p

:steamsalty:

+1

This issue has not been solved at all, contrary to the OP's title edit. With bugs, a workaround is not the same thing as a solution.

But we all know Valve moves at the speed of a glacier when it comes to anything that doesn't directly and obviously affect their bottom line. So none of us should be surprised.
isnogood 2015년 12월 31일 오전 12시 53분 
.
McGillicutti 2016년 2월 9일 오전 9시 45분 
This thread is being used to claim the issue is Steam, as a bug or gltich, I am not so sure.

In my case I had a review up, added text to it, couldn't post, deleted the old review, still couldn't post, deleted the whole review, INSTANTLY happened.

This would rule out a database issue, and if it were the code regarding reviews themselves, likely it would not allow you to delete either, as that would amend the database as well. The code wouldn't care about content, sure there might be a word filter, but as far as the actual data is concerned, it's a group of ASCII, possibly EBDIC (old mainframe conversion to bytes) values, likely compressed in some manner but maybe not, it wouldn't matter. Point I am making is that whatever is done, adding a record, deleting a record, would go through the same code, editing a record would use the same code for creating the record, which is where the delete review comand is located as well. Likely coded together and calling the same code to write out the data (+ a record with content, truncate a record without, does nothing if we cancel) after we're done using the editorial function.

Maybe we're all people who posted something unflattering about Steam or a product (or more) we have, and, Steam or the illustrious developers we've kindly shared a piece of our mind with have added to our database a "flag" a value set that disallows us to post reviews, to amend existing ones, etc., with certain products? That's the conclusion I am at without any evidence of an actual glitch affecting every Steam user, as something like this (unless localized to a particular ISP/netork, or operating system) would if it were a Steam glitch.


EDIT: Funny part, I did a line of text without any commentary of the game, and *poof* it let me post that as a review, copied the rest of the review in np. Funny thing is, it was an update to an older review and is shorter than the original in the first place, meaning: It should have just posted in the first place if this is about some length of words. I have been commenting to the developer's pinned threads about my issues posting my review and, it seems to me, the "flag" on my account from another game that I did everything I could to bring to the Developer's attention how they're alienating players, mostly by reporting bugs, that they decided to send a Moderator to silence me, to threated with suspending my from Steam, etc., and every time I post anything since, that Developer's moderatator negatively characterizes what I posted and locks the thread. So if I seem suspicious something else is going on, it isn't without reason.
McGillicutti 님이 마지막으로 수정; 2016년 2월 9일 오전 10시 00분
gibbousmoon100 2016년 2월 9일 오후 4시 48분 
A good rule of thumb is to presume incompetence before malice. 99% of the time your presumption will be correct.

And here as well, I find it highly unlikely that Valve is malicious enough (or stupid enough, since it would be found out eventually) to code such a flagging system.

On the other hand, imagine Valve understaffed (which is of course no excuse at all) and therefore incompetent. Would it surprise you?
< >
94개 댓글 중 61-75개 표시
페이지당 표시 개수: 1530 50

게시된 날짜: 2015년 2월 11일 오후 5시 30분
게시글: 94