Posted by kaakuu on June 22, 2009 at 4:23pm
While using gallery module like Acidfree I am at my wit's end when I try to put the body text above the image. Something like Contemplate does not help also.
The theme files seem to present $content which contains both image and text, but
no way to alter their positions.
Comments
=-=
you can alter the position of the image using CSS by targeting the image tag or by targeting a div
Seems not possible
That is possible for right or left positioning.
But that is not possible to float DOWN an image, moreso when quantity of node text varies from node to node. Any other guideline will be appreciated.
=-=
Therefore you can put your own div in play no? and place that div in a tpl.php file below where you want it to show. IF $content is removed and you add your own calls, using contemplate or some other method, I tend to use contemplate or devel to show me what is available and where and place that information in my on tpl.php file and design the entire page the way I see fit.
I am sorry
I had a detailed going with contemplate. And devel etc.It does not help.
Probably you need to install to check for yourself.
This gallery has image within $content. The trick will to break it into $image and $content either at module level ( the module owner did not answer issue or contact form) or at theme level. This is NOT possible by css or contemplate but may be by some tweaking code of one or two lines that can be added to the module. Any programmer out here can easily help, imho.
=-=
Gotcha, I don't use acidfree. I prefer building my own content type with imagefield and creating a gallery with views.
imagefield is indeed exposed to contemplate and I can move it around any way I choose.
Acidfree isn't the way forward, fields are.
I see
Image fields do not offer the pagination that acidfree offers - that post is somewhere in my tracker.
Per user gallery is also nicely handled plus mass import etc.
=-=
it's still a deadend method. I highly doubt acidfree makes it to Drupal 7, it doesn't even have a stable release for Drupal 5.x let alone Drupal 6.x.
you can add paganation to content types that ultize imagefields and the other features that you require can be found as well. like for example user galleries, you can use filefield paths and tokens to set up per user galleries uploaded into their own folder. Of course you will not get this type of functionality by flipping a few switches right out of the box with a single module (acid free style) but the choice is yours of course.
good luck.
Is Acidfree not stable ?
Pagination can be added to content types - I am aware of this and Views can do this too. But what Acidfree does it adds an extra pagination when you are viewing a node. By other modes, pagination is available to list pages only.
"you can use filefield paths and tokens to set up per user galleries uploaded into their own folder." - this sounds very complex to me and not an easy CMS way
By the way Acidfree for Drupal 6x works in a trouble free way for me - I wrote 2 or 3 emails to the author to mark it green and ready for use. I have no idea why he has put up this incomplete/broken reputation for Acidfree. It works well out of the box and has no demand like Image Cache etc like Node Gallery. The author said he wants to give away the project to someone interested. As for myself i find it OK and will really be interested to know if there is any real "instability" issues in using it for production sites.
Drupal 7 will take another two years minimum to be ready with all the modules that one may need and some people may just stick with Drupal 6.
=-=
I didn't say acidfree didn't work. Obviously by looking at the issue queue there are issues that stopped the developer from putting out a stable release version. Either way -dev isn't recommended for production sites. It's great that you find it useful.
Of course one can stay with Drupal 6.x, until Drupal 8.x is released or the philosophy changes in some way that makes 6.x still valuable to somoene and they carry the torch after Drupal 8.x is released. Though I think the surge to 7.x will be far faster than it was to D6 where it concerns contrib modules and with the push to get some features in core especially image handling.
My point is still that acidfree is a dead end, with the maintainer him/herself not actively maintaining it, it certainly can't bode well for the project in total. Acidfree is good at what it does but the self contained nature of it, i believe is ultimately it's downfall now that other modules have expanded and make using a self contained package obsolete. In many ways the same as the video.module and audio.module. For Drupal 4.7.x all three were tops for what they did. Futureproof use? not so much.