I can't post in the for sale/wanted forum

Forums › Geekzone › I can't post in the for sale/wanted forum

martyyn

1971 posts

Uber Geek
+1 received by user: 772

ID Verified

#318373 11-Jan-2025 22:17

As above, I get the following message:

To post in this sub-forum you must have made 100 posts or have Trust status or have completed our ID Verification

I'm pretty sure I have at least two of the three:)

This is from my Android mobile using Chrome if they helps.

freitasm

BDFL - Memuneh
80646 posts

Uber Geek
+1 received by user: 41029

Administrator

ID Verified

Trusted

Geekzone

Lifetime subscriber

#3330361 11-Jan-2025 22:20

Screenshot please.

The banner message is shown to everyone.

Referral links: Quic Broadband (free setup code: R587125ERQ6VE) | Samsung | AliExpress | Wise | Sharesies

Support Geekzone by subscribing (browse ads-free), or making a one-off or recurring donation through PressPatron.

martyyn

1971 posts

Uber Geek
+1 received by user: 772

ID Verified

#3330362 11-Jan-2025 22:22

I did wonder that. To start with it said my subject wasn't meaningful (WTB Kindle) and then I couldn't press the POST button.

Let me try again...

freitasm

BDFL - Memuneh
80646 posts

Uber Geek
+1 received by user: 41029

Administrator

ID Verified

Trusted

Geekzone

Lifetime subscriber

#3330363 11-Jan-2025 22:24

You need a minimum of three words in the subject.

Referral links: Quic Broadband (free setup code: R587125ERQ6VE) | Samsung | AliExpress | Wise | Sharesies

Support Geekzone by subscribing (browse ads-free), or making a one-off or recurring donation through PressPatron.

martyyn

1971 posts

Uber Geek
+1 received by user: 772

ID Verified

#3330411 11-Jan-2025 22:26

I changed it to (WTB Kindle any gen) but it still wouldn't let me hit the Post button.

I've just tried again and it's worked, put it down to user error as I've no idea what I was doing wrong :)

cddt

1965 posts

Uber Geek
+1 received by user: 1904

#3330433 12-Jan-2025 07:23

martyyn: ... put it down to user error as I've no idea what I was doing wrong :)

No, no, you should definitely blame the technology gremlins!

My referral links: BigPipe | Mercury

Behodar

11090 posts

Uber Geek
+1 received by user: 6069

Trusted

Lifetime subscriber

#3330483 12-Jan-2025 08:24

martyyn: I changed it to (WTB Kindle any gen) but it still wouldn't let me hit the Post button.

I've just tried again and it's worked, put it down to user error as I've no idea what I was doing wrong :)

I think I know what happened, because it's something that's got me in the past. When you click on Post, the button immediately gets disabled so that you don't accidentally post twice. Then you get the "not meaningful" error message. When you click Back, the Post button remains disabled.

I believe this is browser-dependent and that some will re-enable the button when you click Back.

Presumably when you re-tried it you'd opened the page "manually" again, so the button was once again enabled.

Geekzone support

Support Geekzone with one-off or recurring donations Donate via PressPatron.

martyyn

1971 posts

Uber Geek
+1 received by user: 772

ID Verified

#3330541 12-Jan-2025 10:04

cddt:

No, no, you should definitely blame the technology gremlins!

On here ? Yeah, nah :)

martyyn

1971 posts

Uber Geek
+1 received by user: 772

ID Verified

#3330542 12-Jan-2025 10:06

Behodar:

I think I know what happened, because it's something that's got me in the past. When you click on Post, the button immediately gets disabled so that you don't accidentally post twice. Then you get the "not meaningful" error message. When you click Back, the Post button remains disabled.

I believe this is browser-dependent and that some will re-enable the button when you click Back.

Presumably when you re-tried it you'd opened the page "manually" again, so the button was once again enabled.

This sounds like it exactly, I could see the Post button was disabled but couldn't work out why after having updated the subject line. When I went back again I opened a new window just as I always have done, rather than guessing it was a browser issue with the previous attempt.