TK Page Title - Creates font titles as images (like SIFR)

The download link for the latest release does not work correctly.

Why thank you, Flatulent Badger!

Fixed the link now, simple typo error 😊

Thanks Tony,

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.

FB.

Version 1.0.9

• Added cssonly parameter, allowing for output of just the css required to display the image.
• Added ability to define URL and server paths for location of images (this gives increased control for sites running their admin panel in a separate location to the site).
• Further improvements to code.

Pretty pleased with this next version 😊

Version 1.1.0

• Much of the module has been rewritten, providing a number of improvements.
• Improvements have been made when adding or editing a TK Page Title type. Fonts and gradient files now appear in drop-down lists and a colour picker tool is available for TK Page Title images which do not use a gradient fill.
• The locations of outputted files, fonts and gradient image files are now defined in the Settings page.
• There is now a preview of each TK Page Title available within the Control Panel.
• The alignment of text can now be defined within each TK Page Title type.
• Leading (line spacing) is now an attribute of each TK Page Title type and can also be defined via the new leading parameter in the module’s ee tag.
• Debug has been improved. It now outputs key attributes for each image being generated (and prevents images from being cached). nocache has been added as a parameter. It prevents images from being cached (but does not output any debug information).
• More default gradient variations have been added.

Hey Mate, having a bit of trouble with the module.

Using PHP Version 5.2.6, and EE 1.6.8. The issue is it’s outputting what looks like image source code when trying to access the module in the cp. I’ve verified the pagetitles folder has the correct permissions (777), I’m thinking this is probably a path setting somewhere that’s not correct on my end. Any ideas what I might be doing wrong?

ÿØÿà�JFIF���d�d��ÿì�Ducky�����Z��ÿî�Adobe�dÀ���ÿÛ�„�ÿÀ��?�–�ÿÄ�Ä����������� � ������������ �� ����! 1A"Qaq3s³‘Ñ2B#S“4T´WbrCƒ$Ô%µv–G 8������!1AQ"’aq‘±ÑÒT¡BSs2R²#5Áábr3&6ðcD%ÿÚ���?�·¡»;¦ÙÓ˜Sq Sų´)ÿ�´YDÕ6ÎC¨ Ì„iÐeIܝBH†€nzTœì:kÓžéÓ´è?¨ßÖ#ž9( éUä|ÇTTxgý6¦²?h““qE�ãšFߏýÁä]ÉVrÄîOF êT¤ã[Bý:56 "ƒ–j®¨)óŸ«æ)t.1ê¦Ó£³Î’Êm]¶’T® €#»ìvÝ©§—G¯øŒq:¨’2ù!BR"dÔ SPA)ƒí�ÐCðp*ñÎ�þ+¹˜Ã²b‘Ju[ ‰:ç*dØm5á Ž9,!1ç"Lr4{B†d™G×AL¡È&“ÆNqãŽd·¼Æ¾ç¯ãÕò,Å] ¹gNbR•wZ(Ru)`M"˜TS¤¦7IG@ãµ·­í­­d‡ÌšòšŽCûÎC‚˜’mD»•ÎU,ÙÂK&/vCÕ‰È)N&~0ò5žò†oÅ”à¯U`ª÷+\tŒCh¥WTY¼vDT�rés0ˆ�9ü>XK×HmtVÙ³uLsØÇK“0À

Hey Mate, having a bit of trouble with the module. Using PHP Version 5.2.6, and EE 1.6.8. The issue is it’s outputting what looks like image source code when trying to access the module in the cp. I’ve verified the pagetitles folder has the correct permissions (777), I’m thinking this is probably a path setting somewhere that’s not correct on my end. Any ideas what I might be doing wrong?

Blimey.

I made a 1-line change the other day (call it a build update, not a version change) - for some reason the encoding on the file got screwed up. I’ve reuploaded, checked and replaced - try version 1.1.0 again

n00b mistake, my apologies 😉

hey, no worries! thanks for all your work on the module!

Hey, I hope you enjoy it!

Feel free to feed back 😊

Hi mr. Nibbles,

your module is working as expected! thanks already.

there’s a small internationalization problem though.. it won’t output german special chars: like äöü. should I change any file format to utf-8, or how should I proceed?

cheers stefan

Oops

Hey there 😊

I’ve not tested with Cyrillic characters, but generally speaking most characters should work fine - so long as the font you’re using supports them There should certainly be no problem with the umlaut.

I’ve used this module on websites for many different languages, including: French, German, Spanish, Dutch, Danish, Polish, Italian, Finnish - no probs.

If in doubt, test it out with the default font, verdana which should let you know if the characters are causing problems with the module, or just not displaying in your font.

😊

Hey there 😊 I’ve not tested with Cyrillic characters, but generally speaking most characters should work fine - so long as the font you’re using supports them There should certainly be no problem with the umlaut. I’ve used this module on websites for many different languages, including: French, German, Spanish, Dutch, Danish, Polish, Italian, Finnish - no probs. If in doubt, test it out with the default font, verdana which should let you know if the characters are causing problems with the module, or just not displaying in your font. 😊

hi, thanks for ashuring me! well.. everything seem to work fine (with umlautes etc) but as soon as I turn on case=”upper” it will leave out the umlautes… I tested without the case=”upper” and the umlautes are not displayed on capital caracters (with both fonts) so any idea?

cheers stefan

Hmm, see what you mean.

I’m not sure if its changing the character, or actually cropping the dots off the top of the U. I think it’s the latter.

There is another problem with the underlying html on the page - it’s not html entity encoding.

Add to the fix-it list!

😊