Working with dynamic data and layers can be a pain, using a box model can help you get around these issues but I personally do not use layers for dynamic data ‘or rather rarely use’, I really find it a lot of work and I also find it can be restricting. I see no real disadvantage not using layers and the advantage is the page always comes out as I want it to be without having to worry about overlaps, wide areas of white space etc. Others view on this may differ but this approach works for me, for what I do and for what I need.
I am not sure how you are outputting the data in the markup item but you can limit the number of chars for data, I do this myself at times although I have a function I pass the data through which cuts the string to a certain length and then adds 3 full stops after the text. This might not suit your needs but there are many ways of doing this like adding a [ Read more ] after the text like: ‘and some te… [ Read more ]’ while linking the ‘Read more’ to the full text.
A small example of restricting the string length in a variable could be done as follows:
<?php
// Text content set to variable
$theStr = 'Bla, bla, bla, bla, bla, bla, bla, bla, bla, bla, bla, bla, bla, bla, bla, bla, bla, bla,';
// Shorten the string to 35 chars and add '...' to the end of it.
$theStrShortened = substr($theStr,0,35) . '...';
?>
Obviously you would need to deal with the string being cut off and give your visitor a way of reading the full information as mentioned above but then I am not sure what you are doing and if this is even the problem you are having without seeing an example.
HTH
On Apr 18, 2012, at 11:55 AM, Kim Kohen wrote:
I have a couple of pages where there’s PHP code which pulls rows from a database. No matter what I’ve tried, the markup area always grows to the complete depth of the returned results but I’d like to restrict it to a fixed size. I already limit the rows returned but as each row varies in size it’s not reliable. The data even extends way beyond the page depth which seemed odd to me.
I want to add a footer to a master page and the db listing is just trampling over any attempt at a footer. So my questions are:
-
is there a way to forcibly restrict the size of a markup item?
-
what’s the best way to add a standard footer to a (master) page - preferably which will move up or down with different page content? Something like the blue footer on this page - http://www.theleader.com.au/
-
once I have set an item to be dynamic height (setting height to nil), is there a way to set it back to nominated height again?
I’ve come a long way in a couple of weeks but I clearly still have much to learn.
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options