David’s Thoughts

When using the typo3 extension “rtehtmlarea” there is a compatability issue with Firefox 2.0.0.3. The issue is explored on the typo3 bugtracker here and here. Toward the bottom of the list of comments you’ll find the solution. I’ve tried it, and it works. Here’s the boiled down solution.

in this file:
sysext/rtehtmlarea/htmlarea/htmlarea.js in line 85
change this:

HTMLArea.is_wamcom = (HTMLArea.agt.indexOf("wamcom") != -1) || (HTMLArea.is_gecko && (HTMLArea.agt.indexOf("1.3") != -1));

to this:

HTMLArea.is_wamcom = (HTMLArea.agt.indexOf("wamcom") != -1) || (HTMLArea.is_gecko && HTMLArea.agt.indexOf("1.3") != -1 && HTMLArea.agt.indexOf(".1.3") == -1);

Then disable the compressed scripts option for rtehtmlarea in the extension manager.

And, remove from typo3temp all files that start with rtehtmlarea. Clear the cache and Firefox, and you’re good to go!

So, you’ve started using typo3, and you’ve even built a couple of web using typo3. Then, of course, you’ve heard of typoscript, and seen things like this:

lib.something = TEXT
lib.something.value = hello there.

Well, have you ever wanted to just append a value, or slightly change an existing value?

Welcome, :=

Here’s an example:

lib.something.value = hello there.
lib.something.value := prependString(Umm, )
# results in “Umm, hello there”

Here are all the functions that are available, copied right out of doc_core_ts.

prependString: Adds a string to the beginning of the existing value.
appendString: Adds a string to the end of the existing value.
removeString: Removes a string from the existing value.
replaceString: Replaces old with new value. Separate these using “|”.
addToList: Adds a comma-separated list of values to the end of a string value. There is no check for duplicate values, and the list is not sorted in any way.
removeFromList: Removes a comma-separated list of values from a comma-separated list.

For all of you intermediate TYPO3 configurators out there, I know your gears are turning already, thinking about all the times you wished you could use something like this!

I will cut right to the chase on this. After researching and trying several different methods of enabling imagemagick in typo3 on my mac, there was only one package that worked completely. The package imagemagick-6.1.7.pkg.tar.gz provided by Marc Liyanage. Just download the pacakage, extract it, run it, and it will install everything in /usr/local/bin/ just like it should! At the time that I was hunting, the pages of his site were not responding, but I found the important page in a google cache.
Here are some other things that I tried. These did not work for me, in case you are considering some of these same methods.

• Using DarwinPorts to install GraphicsMagick
• Using DarwinPorts to install ImageMagick
• Using the Image Magick downloadable binary from the ImageMagick web site
• Compiling ImageMagick from source. (I was missing some of pretty important libraries, like JPG, TIFF, etc.)

So, don’t mess around. Just be smart and use the Mac installer from Marc Liyanage.

Enter this in SETUP:

plugin.tx_cssstyledcontent._CSS_DEFAULT_STYLE >

Doing this will clear all that extra CSS you get, but will also have some negative effects.

quote from http://bugs.typo3.org/view.php?id=1636:
The css styles from the integrated cron_cssstyledcontent are vital for positioning of the elements, so this cannot be a “reference” implementation: without it, no image positioning would work, many users would be frustrated. A second reason to have this in TypoScript is that it makes use of some constants that can be set through the constant editor (border color, margins, etc), so that the generated css includes this information dynamically. These constants also are well known and provide a “smoother” transition from table-based styles to the css-styled-approach, without having to adapt any css-styles on your site.

1) create a template file for your form, messages, and emails, based on example_form/mailformplus_demo.html
2) add a mailformplus record to a page
3) fill in send-to, subject, send-from, required-fields
3b) most importantly, attach the template file
3c) redirect-to-this-page seems not to work.
4) add a mailform plugin to the page (as content). No config needed on it.
5) add typoscript to template record:
plugin.tx_thmailformplus_pi1.emailHeader = Content-Type: text/html\r\n
plugin.tx_thmailformplus_pi1.emailParameter = -f server@host.example.com

I have just done some initial research into how to use typo3’s versioning api, especially in regards to previously existing extensions. Here is what I’ve found, in summary.

To add versioning capabilities to an existing table of an extension.

ext_tables.php:

$TCA[”user_localdev_stores”] = Array (
“ctrl” => Array (
…
‘versioningWS’ => TRUE,
‘origUid’ => ‘t3_origuid’,
…

ext_tables.sql: (right after the cruser_id line)

CREATE TABLE user_localdev_stores (
…
t3ver_oid int(11) DEFAULT ‘0′ NOT NULL,
t3ver_id int(11) DEFAULT ‘0′ NOT NULL,
t3ver_wsid int(11) DEFAULT ‘0′ NOT NULL,
t3ver_label varchar(30) DEFAULT ‘’ NOT NULL,
t3ver_state tinyint(4) DEFAULT ‘0′ NOT NULL,
t3ver_stage tinyint(4) DEFAULT ‘0′ NOT NULL,
t3ver_count int(11) DEFAULT ‘0′ NOT NULL,
t3ver_tstamp int(11) DEFAULT ‘0′ NOT NULL,
t3_origuid int(11) DEFAULT ‘0′ NOT NULL,
…

that’s it. make those two adjustments, and your records will now have that nifty “v” versioning icon.

2)

Now, if you want your extension to DO things with versioning, such as create a new version of a record automatically, e.g. when a FE user submits a form, here are some classes to reference:

t3lib_BEfunc->selectVersionsOfRecord() and others in t3lib_BEfunc
t3lib_page->versionOL() and others in t3lib_page
t3lib_TCEmain->insertNewCopyVersion()
!! t3lib_TCEmain->versionizeRecord() and others in t3lib_TCEmain
t3lib_TCEmain->insertDB($table,$id,$fieldArray,$newVersion=FALSE,$suggestedUid=0,$dontSetNewIdIndex=FALSE)
t3lib_TStemplate->versionOL() ??
t3lib_userAuthGroup

It looks like TCEmain is a class that I need to spend some time in!