Description, Title and filmstrip should divided from Gallery-table Description, Title and filmstrip should divided from Gallery-table
 

News:

cpg1.5.48 Security release - upgrade mandatory!
The Coppermine development team is releasing a security update for Coppermine in order to counter a recently discovered vulnerability. It is important that all users who run version cpg1.5.46 or older update to this latest version as soon as possible.
[more]

Main Menu

Description, Title and filmstrip should divided from Gallery-table

Started by khan2002, April 16, 2007, 10:59:42 AM

Previous topic - Next topic

0 Members and 2 Guests are viewing this topic.

khan2002

Hello Everyone!

I'm just looking to create a new Coppermine Template, but one of the most importanat things for me is to find a way to divide the image title, the image description and the filmstrip from the Gallery table. I want to bring these fields in a div-container, which i created in the template.html. Ok I think it would be possible, to create in the theme.php div containers, which i can bring where i want with absolute positions, but this is not the way I want to solve this. I would be great if someone has an idea, because at the moment I find no way....  :'(

Joachim Müller

All of the blocks you mention are not being defined in template.html, but in theme.php. You can wrap them into div containers. For details, post details: a link to your coppermine-gallery, a screenshot of what you would like to accomplish and what the code that you have come up with so far would be extremely helpful. Post the link and attach the screenshot and the zipped custom theme folder to your posting (using "additional options" when composing your message).

khan2002

Hello

at the moment I am working on the hmtl file and positioning the div containers in css - so there is still no theme.php available, but in the design.jpg you can see in which way I want to place these items.
thanks in advance. (I want start with the sample/theme.php)

Joachim Müller

Quote from: khan2002 on April 16, 2007, 02:27:42 PM
I want start with the sample/theme.php
That's the wrong approach. Start with themes/classic/theme.php instead and add only the stuff that you actually want to see changed from themes/sample/theme.php

khan2002

Hello

thanks fpr the hint!

but my central question is, how can I wrap elemtents in a div container?
Is there anywhere  tutorial?

khan2002

Ì want to specify the question:
Is there a way, I can give an element from theme.php a {placeholder} to bring it in a position I want in theme.html?

khan2002

Ok, now I've found out the way and  I solved it. Now I've the problem, that I need the "powered by" element not in a div class but in a div container. Until now I can not find a way to change this!
Olease help me - I've nearly finished my template, but this problem is very very hard to solve for me....

Joachim Müller

From the FAQ:
QuoteNote: PLEASE don't ask idiotic questions on how to remove this line in the Coppermine Photo Gallery Support Board - your posting will be deleted!
The same thing applies for questions on editing the "Powered by Coppermine" tag: telling you how to edit it would actually mean telling you how to delete it.
Additionally, we have a "one question per thread" policy that you agreed to respect when signing up. Locking.

Joachim Müller

khan2002 by PM:
Quote from: khan2002 on April 18, 2007, 12:20:51 PM
Hy

Ok I understand your statement in one way, in the other way it deletes my template. So I cannot understand why you put this in a class and not in an container. Ok for the moist templates it's no problem, but if someone wants to make a special one, which is not like each other with variant positions of picture titles etc. it's really not an ideal solution.

michael

You're not suppossed to continue the discussion by PM - I have not allowed you to contact me individually. There's little point in asking why things are the way they are - the only thing that makes sense is requesting changes for the future. The "Powered by Coppermine" tag is one of the things that already has been taken care of in the devel code, so your issue will be solved in the future. Meanwhile, you'll have to live with it.