* This is a permalink, and the page only ever contains links to the latest version of this module. This thread is updated with details of each update, but there is only one page to get the latest file.
I’ve attached some examples of the sorts of page title images this module can produce, typefaces used are Cooper and Myriad Pro, both with gradient fills.
* Added first level of error checking in control panel when creating or editing existing page title types.
* Added new field to page title types: save location, for determining where page titles are stored.
afaik, fonts are like software and should be treated as such. You should not distribute them.
However, uploading to a web server for a script or SIFR is somewhat a grey area. With SIFR, users can easily download your .swf files and use your fonts on their own server through their own SIFR. Some people have even set up sites like www.fontsmack.com for this exact purpose, which in my eyes appears to be wrong.
Whilst the module above doesn’t allow for the ease of access to the fonts like SIFR does, at the moment the fonts are in a directory accessible via www.
I think I will add the ability in my module to store fonts outside of the domains site files directory, so that if users wish, they can store their fonts in a secure place.
“I think I will add the ability in my module to store fonts outside of the domains site files directory, so that if users wish, they can store their fonts in a secure place.”
Yes, that would be helpful, say, to access the files via server path like /www/fonts/, where the site itself is in /www/public_html/
* Changed the font file storage location to an absolute path from server root. Users are advised to store fonts outside of their public html directory to prevent unauthorised access or distribution of licensed fonts.
* Fixed a bug occurring when the gradient parameter was set.
* Added a tag preview to the TK Page Title module index page.
* Added a link to the documentation page.
* Rewrote the code which calculates the number lines in in the text, in order to more accurately generate the gradient fill. This fixes a bug with gradient fills on some images.
* Added align parameter to define the alignment of text within an image.
* Added style parameter to define additional style attributes on the containing tag.
* Changed the way the filename is generated. The hashed value is now generated from a wider range of given parameters, to prevent unwanted caching.
At the moment, that is not possible. I really cant think why anyone would want that - but the next time I update this plugin I will try to implement this feature for you!
* Added antialias parameter which will turn off AA if set to false.
* Fixed bug for the target parameter.
* Changed the way images are stored. Gradient and Mask files used in the generation of the image are now automatically removed.
I do get an error the first time I load a page with a new title though, and it royally messes with the URL in the browsers URL field. Only the first time though.
Is this a known bug or have I done something wrong?
* Rewrote the code which calculates the number lines in in the text, again. This fixes a bug with gradient fills on some images.
Phil J Leitch - 22 December 2008 08:23 PM
I love this module. Very nice.
I do get an error the first time I load a page with a new title though, and it royally messes with the URL in the browsers URL field. Only the first time though.
Is this a known bug or have I done something wrong?
Thanks.
Hi Phil,
Sorry for the delay in replying.
Known bug. The rewriting URL oddity I have come accross before. I can only make it happen on rare occasions (and only when the image is being generated for the first time).
I’ve tried already but its a real hard one to track down, so I cant promise any fixes for this anytime soon, unless a brainwave hits me as to its cause.
* Added colour property: Page titles will use the colour when a gradient fill is not provided.
* Added support for global variables within page titles.
* Restructured some code to make it a bit tidier.
* Fixed a part of the code which was causing the image to be output to the browsers URL bar. This error may continue to occur in the event of a PHP error (different server setups could potentially cause some errors).
Phil J Leitch - That might have fixed your problem!
I downloaded it and gave it a try. Unfortunately my production server PHP is not up to standard at this moment and I kinda need to finish this project in the next 3 or 4 days.
Its on my list to try when I get more time. It certainly looks like it could be the solution to some issues I have.
