Yes, sir, all three are checked. I've also tried the Show Photo Option "Show html code to display photos?" both ways with the same result. If the text is edited at the "Process" point or after the photo is uploaded, it stays in the proper format, but it refuses to "stick" from the original upload.
K, this is strange. Took a break and came back to find the text is still displaying incorrectly in the Process box, but if I hit Upload anyway it displays correctly, whereas it wasn't doing that before. It had to be edited at Process stage or after upload to stick.
The problem is still sort of the same, though. Users won't know the incorrect display is an interim thing. Plus it looks terrible. Is there another page I can edit to get the process box to display correctly?
well your starting to talk about upload here which is a whole different problem then your reporting so please explain where exactly you have an issue and what script because I dont think I am sure what your trying to report now. Example the lines your talking about are about the description on a photo when viewing the photo but the topic here seems to have jumped.
First example shows the initial upload screen, where user chooses picture, title and description.
Second picture shows "the Process box," where the characters parse incorrectly.
Third picture shows the final upload, where the showphoto fix must have kicked in at some point because the characters render properly.
What I am asking is how to make the Process box display correctly as well. As I said, it looks bad with the incorrect characters and users won't know they *don't* need to edit that in order to have it display correctly.
Okay yes that line your nothing has nothing to do with the issue your really looking at.
I don't even know what that means. Though I surmise I'm being told I don't know what I'm talking about.
. . . things are working fine just your getting on the 2nd upload screen the middle shot the html is not pretty
It's a gallery. It's supposed to be pretty. And support is supposed to be helpful, not disdainful and contemptuous of customers. And to think I paid for this kind of treatment. Maybe I am stupid after all.
All I am saying is your referencing some mod line from code that exists in showphoto.php from some other thread which has nothing to do with the issue your posting. We spend some time here going back and forth about the showphoto script only to discover when you posted attachments that your talking about the upload process in bulkupload.php. Which explains why when you changed the code you where noting that it did nothing.
Now I have looked at the code and I think this should help you for upload
Lines 185 and 186 of that file are this
Content visible to verified customers only.
Simply change those two lines to this and on your second upload screen it should display fine for you.
I was just coming back to say the first fix didn't work. Now I see you've added another change. Just did that and it works great. Thank you! I tested double quotes, the ampersand and brackets. The brackets and text in between them didn't render, but I can certainly live with that.
Not to belabor things, but I/we/any customer wouldn't know you consider this issue to be "apples and oranges" because it involves changes to two page files. To me, it's one process that should work correctly from start to finish. And now it does. Thank you again!
Well I do beleive that solves your actual product support questions.
I think the two things you have left would be a code modifications you want to do to display comments in an alternative format our main template is not designed to do and an issue with a custom style on your menu correct me if I am wrong.
1. You can post about code modifications which fall outside product support here. Pretty much the same rules as vbulletin.com we support the code as written.
If I get some free time I may help out if I can as I would eventually probally be updating the comments display eventually as that hasnt changed since we released the software but product support takes most of my time here and I occassionally look at mods and when time is permitted post some ideas for some people. Example you might want to look at this mod I created for people using vb4 it adds gallery block on the forumhome and whos online definitions as well as profile display stuff for the gallery as well.
2. Your style issue with the actual photo options menu. I really would need to see a direct link to your site and style so I can peek at the actual style and maybe see where that might be going wrong. As I said we specifically coded things to work with the default vb style so your issue is going to exist somewhere in a style change that was made I would suspect. make sure to post a regular test user account so I can see the menu etc
I have a pretty much clean vb4 photopost pro setup here with the default style so you can see what it should look like or change your style back to the default and see on your site.
I agree, technically the gallery seems to be functioning properly now and the remaining issues fall under style. However, since my gallery involves my business, and my business involves design, the styling is equally important to me.
I appreciate the offer of help if/when you have time. This is a very nice change that is very noticed and, again, very appreciated. I took a look at your gallery. The pictures are gorgeous but I'm not fond of the layout. It wouldn't work with my theme, given we're on a fixed width as opposed to fluid.
As far as the integration, my forum is absolutely perfect except for one latent issue that has magnified when carried over to the gallery. I put in a ticket at vBulletin, but they say there's nothing wrong. Okay, sure, if you don't count the big, gaping hole at the bottom of the second tier and below of the gallery pages.
This particular problem only occurs on one page at the forum, an admin page that no one (except admin) sees. I'd posted about it at their forum before even thinking to install Photopost, but couldn't get a resolution. I believe it's due to a body wrapper tag closing too early in one of their thread templates. Or an extra closing tag floating about, etc. But, again, they say there's nothing wrong. I'm waiting for 4.0.2 to arrive before I bother them again. That was my original plan, in fact, until I saw what it had done to the gallery.
Sooo, if you still want to come on over, Red Rover, you're more than welcome. Is there somewhere I can email the information you've asked for?
Edited because I'd forgotten about the mod. Already installed. Mentioned that in an earlier post in fact. Love it! I'd wanted it for the navtab link. Easy to do and it works like a charm. Nice work!
Last edited by Toni3055; February 11th, 2010 at 03:25 PM.
Much like vbulletin we do have to support our code as written and like I said I help users when I can outside the realm of support when I have time. I took a few minutes and while its not exactly like the vb postbit its probally a step in the right direction you can grab that template here
Like I said my gallery is merely a default vb photopost install in every way except for now I modified the comments html portion with the user info on top of the comment some.
vbulletin in general released vb 4.0 way too soon it was beta software to say the least with there gold release. I mean come on 4.01 has over 200 bug fixes. 4.02 is slated to have at least another 100 bug fixes or more.
See when your looking at an issue and your contacting a company whether its here or vbulletin you definately want to have the default style to fall back on as I showed and gave you a test login to even see is that I really see no issues. vbulletin will probally ask something similar.
I will give you an pointers I can after I actually see your site.
I'd bet the template rocks if I could grab it. LOL! Getting a "Not Found" error. Emailed you, as well. Thank you again, Chuck! This was really sweet of you . . . all around!
No worries, I still have the default style installed. I never got rid of it. I just added a new style to work from. However, the body wrapper problem is evidenced even when set to default. I posted a screenshot for them using default styling which shows the premature closing and the Firebug screen verifying it. But it doesn't "look" bad because the default styling has a solid color there. I guess that's why they say there's nothing wrong. With my styling, it's a gaping hole. So I would agree wholeheartedly they probably released it too soon, given they had at least 301 problem to fix.
Their support tech for the ticket said he doesn't see this issue in 4.0.2. Then again, he doesn't see it in 4.0.1 either. Not sure how that's supposed to make me feel better. Reserving final judgment until I have 4.0.2 installed. Should be very soon if they're still on target. Let's hope, and that "free time" comes to your neck of the woods as well.