Image Viewer

[Tranz]

Thanks everyone for all your help...seems to work ok in I.E. but unfortunetly not in Firefox

Really? I tested in Firefox and it worked fine until I checked in IE. Could you please post a link to your site?

by the way nice looking site TranzNDance-very clean and well thought out...

Thank you.

[dondo521]

Well it's not much of a site right now but here it is:
so the bots wont get this: just do the usual www thing and then
oceanwalkphotographers and then the dot com and then /owo

The only time it works in Firefox is when I refresh the page-but not when I move back and forth with the arrows

dondo521

[rvblog]

@kegobeer:


In response to the question:

Verify you have this line in your theme.php file, in the pageheader function:
Code:
$template_vars = array('{LANG_DIR}' => $lang_text_dir,

Yes, the code that I have in the pageheader function section in the theme.php file is identical to that.


In response to this question:

I don't know if this is related, but if I view source on your page, this is displayed:
<html dir="{lang_dir}">

but it should be this:
<html dir="ltr">

The code that you refer to:

Code Select Expand

<html dir="{lang_dir}">

is located at the top of the template.html file - that piece of code was in there in the original hardwired theme, so I just left it there.

Should I remove it ?

Or, replace it with this:

Code Select Expand

<html dir="ltr">




Thanks

[rvblog]

By the way,

I'm still getting the javascript error - any ideas why ??


On another note:

My content section (div class="content") is a long page under Firefox and a much shorter page under IE - is there a way to have the page appear as equal depth in both browsers ?

[Tranz]

Probably not related, but there were some errors in the code elsewhere:

Code Select Expand

themes/ardwired/images/buttoncenter.gif

Code Select Expand

<meta http-equiv="content-type" content="text/html; charset={charset}" />

If you correct the charset one, you can use W3C to validate the page and it could help pinpoint the issue. http://coppermine-gallery.com/forum/index.php?topic=13604.0

[kegobeer]

For some reason, {lang_dir} and {charset} aren't being parsed.  I'm not sure why, but the culprit is most likely your modified theme.  I think you'll have to compare it line-by-line with another theme to see where the problem may be.

[Tranz]

It's because the parsing function is case-sensitive. If {lang_dir} and {charset} are made all uppercase, it will work. I tried it on my gallery, except went from upper to lower case and got the parsing failure.

[rvblog]

I went to W3C to use the validation feature there.

I checked out my site: www.rvadventure.ca/photos - and got all kinds of validation errors - wow !!


So, I  turned off my theme and turned on the original hardwired theme in the config panel - and W3C showed all kinds of errors as well

So, thinking it was an issue with the hardwired theme itself, I changed over to coppermine's eyeball theme - and guess what? - got all kinds of errors with that theme as well.

Then I changed to cpooermine's classic theme - and the same thing happened.

So, it appears that all of the theme templates that coppermine uses all have problems regarding validation at the W3C site

So what do I do now as far as a theme template - just ignore it ??

I've spent so much time on coppermine - I would hate to have to change to another gallery program.

[rvblog]

I spent some time checking other themes out

In all the packaged themes in coppermine, the template is this kind of doc type:

Code Select Expand

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">

So I went outside of the included themes and checked out other themes like reynolds, forest, 2bornot2b, etc and those templates has this kind of doc type:

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

So, I uploaded those themes, selected each of them in the config panel - and all three themes only got 4 minor errors at the W3C validation site.

So I guess I'll have to change the base for my theme and see what happens.

[Joachim Müller]

validation issues have been discussed elsewhere already. Just a short statement: both the cpg1.3.x core code as well as the themes that come with it will not validate, and it would take a huge effort to make them validate - I wouldn't recommend that. When you try validating some sites of "the big boys" (try MSN for a start ), the same thing happens: currently, there are only very few pages that actually validate properly. However, they stil are correctly displayed in most browsers. Some of the code that keeps them from validating even is in there to provide cross-browser compatibility. The next version of coppermine (the current devel version cpg1.4.x) will be standards compliant by default and will validate (xhtml transitional) - you're welcome to test it.
Bottom line is: I wouldn't worry to much about valid html for now - you will hardly find another gallery app that will actually produce valid code.

Joachim

[kegobeer]

@rvblog:

The hardwired template.html has {lang_dir} and {charset} - change them to {LANG_DIR} and {CHARSET} as Tranz suggests.

[rvblog]

OK then

I'll use what I have with the changes that have been suggested


When 1.4 comes out, will it I have to build a new theme again - or will it be a smooth transition from 1.3.2 to 1.4 ?


Any idea when 1.4 will be ready?

[Joachim Müller]

When 1.4 comes out, will it I have to build a new theme again - or will it be a smooth transition from 1.3.2 to 1.4 ?

There will be instructions on how to update your custom theme to make it work with the new versions.

Any idea when 1.4 will be ready?

No. It currently is in beta stage. No telling when it will be ready as stable.

Joachim

[Tranz]

Sorry, I wasn't saying the whole page should validate. I just thought the validation process could point out an error in the javascript that could help with troubleshooting.

[rvblog]

Second try:

The #topimage code was acting up every now and then, so I dropped that idea and decided to eliminate my header pic in order to move the imageviewer higher up on the screen.

I also dropped "hardwired" as a base for my theme and used the classic theme as my new base - but I stayed with and modified the hardwired template and I used part of the admin_menu layout and css that was in a theme called "forest" (don't remember where I found that theme).

I also got rid of the javascript error (don't ask me what I did - but after some trial and error it disappeared.

Anyways, I wanted my theme to be very simple and easy on the eyes - I also added my site navbar to easy navigation back and forth.

This is the new result: http://www.rvadventure.ca/photos/index.php

Now I can start uploading my photo files this weekend.

Thanks for everyone's help getting me this far.

[snork13]

Looks nice. great work

[danjam]

You could always use a pure-JavaScript solution:

Here is an image viewer, in object-oriented, cross-browser JavaScript. Very easy to plug and play, with "slide show" feature, and fully customisable in CSS and HTML:

http://www.webonweboff.com/widgets/js/image_viewer.aspx

Article includes a demo, source code, explanations.

Hope this helps...

[popersman]

Hi guys,
sorry to bump such an old thread, but I'm having issues with this workaround.
I'm no coder, even less of a designer, and i have a very basic understanding of how a script work.
I am using CPG 1.4.10 with a them called Avalanche.
The theme.php file included in the Avalanche theme is nearly empty, and doesn't contain all the lines of code that have been mentioning.
As an alternative, i tried to modify the theme.inc.php that can be found in the include folder, with no success.
Any idea on how to fix this?

Link to my gallery: http://ed.roquette.free.fr/photo/

Thanks!

[Sami]

I am using CPG 1.4.10 with a them called Avalanche.

Then create a new thread on proper board (cpg1.4 themes/skins/templates)

This one is locked...