Welcome to the SR20 Community Forum - The Dash.
Register
SR20 forum logo

Thread: First pics in classified threads

+ Reply To Thread
Posts: 11-20 of 21
2012-04-30 16:30:19
#11
Originally Posted by eggman
Why do we need to put the url in anyway
Because without a specific spot for at least one picture, 75-85% of threads get created with no pictures at all. Most people do not read the rules, and putting that one field in saves the moderators tons of time, herds the users in the right direction because it is nice to think they will read the rules and follow them, but they don't. Or they need reminders.

Originally Posted by eggman
when we put the IMG in the description anyway?? seems redundant.
It is redundant. The field is there to remind people that an image is required. Technically you can not put an image URL in, and as long as we see pic(s) in the thread you won't get any gruff from the mods.

Also, the image URL also gets printed out in plain text. This is a known bug that is getting worked on eventually. That is not working as planned. It shouldn't be there.

Originally Posted by eggman
Also...whats with the "where is the item located?" I always put "in storage" or on my car????
Is that really necessary.
I will let Cliff clarify, but I believe it is there to alert buyers that you either have the item in your immediate possesion, or that it might be in storage or out of country (Ashton in the Middle East for example with his parts in the US). And to be prepared for what that may mean for the timing of the sale.

Originally Posted by eggman
I am not complaining,but I dont see what was wrong with the last format.
The last format did have it's own issues. It was almost polished to a good shine, but it would never have been as easy or as friendly as a proper "form" can be. The form has been something people have been asking for, for a long time. In my opinion and others, it should have been a form begin with. It just took a while to get it done. And now we just need to tweak it to get it right.
Last edited by BenFenner on 2012-04-30 at 16-34-34.
2012-04-30 16:37:06
#12
It seems to be an issue with Internet Explorer at least. IE8 is showing the problem on my XP machine as well. Cliff, it's pretty easy to tell by looking at the HTML source that an HTML comment tag is not terminating properly in Internet Explorer.
2012-04-30 16:39:51
#13
I also have Safari and Firefox at home.

So when it works like it should, the direct image code we enter produces a picture on the thread. So some people are seeing pictures twice if we put it in the thread using image codes?
2012-04-30 16:52:24
#14
I see it now. I almost never use IE products, so it didn't dawn on me to check that when doing the modification :o

I'll work it out when I have time this week. There may be an alternate solution that I can come up with.
2012-04-30 16:55:17
#15
Originally Posted by b13sr20BB
So when it works like it should, the direct image code we enter produces a picture on the thread. So some people are seeing pictures twice if we put it in the thread using image codes?
Yes, exactly. We know it could be better, but yes that is how it "should" work right now.
2012-04-30 17:10:08
#16
Originally Posted by BenFenner
Also, the image URL also gets printed out in plain text. This is a known bug that is getting worked on eventually. That is not working as planned. It shouldn't be there.
That's the issue I'm speaking of. I didn't know it was a know bug, and I assume others don't know either, unless it's been published somewhere.

C
2012-04-30 17:12:13
#17
Originally Posted by b13sr20BB
I also have Safari and Firefox at home.

So when it works like it should, the direct image code we enter produces a picture on the thread. So some people are seeing pictures twice if we put it in the thread using image codes?


Not exactly.

This is what happens:

1. You enter image URL.
2. Server wraps your input text from the field into wrapper.
3. When thread is submitted, image is displayed as picture and not as URL.

Now here is the issue:

When the thread is submitted, the URL entered is not converted to a linkable URL, because it's first wrapped with . This means that the "AltText" still displays when using Chrome or FF. So now you have an image displayed, and immediately following the image you'll see the alttext "http://urlhere"

In IE8, the wrapper is apparently ignored/omitted, as the URL is still produced using the alttext to create a linkable URL.

Clear as mud, yes?
2012-04-30 17:15:45
#18
http://www.sr20-forum.com/miscellaneous/57197-ibm-lenovo-thinkpad-ultra-lightweight-notebooks.html

Chrome is displaying the image, followed by the url. IE8 isn't even showing the image! I can grab screenshots if you like.

C
2012-04-30 17:16:13
#19
lol...not to confusing. my pascal and c++ background helps a little with programming language.
2012-04-30 17:20:45
#20
Originally Posted by b13sr20BB
lol...not to confusing. my pascal and c++ background helps a little with programming language.


Then what I said should be pretty damn easy to comprehend.

HTML/PHP markup is pretty damn simple, yet I still have problems with it from time to time

No screenies needed Chris, I know what's going on
+ Reply To Thread
  • [Type to search users.]
  • Quick Reply
    Thread Information
    There are currently ? users browsing this thread. (? members & ? guests)
    StubUserName

    Back to top