HTML in product descriptions without using !!<>!!?

[Sadcase]

Hi,

I'm in the process of changing the design of our webstore, and this means adding HTML tags to the product description. All of these tags are already styled using CSS.

My question is: Is it possible to enable the product descriptions to display HTML, without having to enclose the text within the !!< >!! tags? The reason for asking is because I've got 900+ products to change, and any saving on key presses would be appreciated.

Also, I notice in the HTML section of the Text section of Actinic, there are two entries - !!<%s>!! - (ID 1193 and 1194) which don't seem to be referred to in the AUG, but look like they'd do the job if they could be applied to the product description.

Please can anyone advise as to whether this is possible?

[gabrielcrowe]

I'd like to further this question with a feature request.

a tickbox that says: 'This is HTML'.

Then actinic assumes that all of the text in the box is html.

[fergusw]

Another option to cut out keystrokes, if you require !!< and >!! in all your product descriptions, is to prefix and append !!< and >!! respectively to these fields directly into the database once you have added your HTML into the relevant fields.
(note - editing the database is not recommended for the inexperienced. Make BACKUPS before even attempting it!)
Alternatively there are plugins available that would perform this kind of action (amongst others) for you.

a tick box that says: 'This is HTML'.

Excellent idea Gabriel. Whooooosh. Straight onto the wish list.

[pinbrook]

or set up an automatic keystroke thingy - hit a button o nthe keyboard and it types in the code - can't remember what its called

[magicalwonders]

hit a button o nthe keyboard and it types in the code - can't remember what its called
A macro?

This might be of use:
http://www.macroexpress.com/
There are probably some free utilities out there as well.

Myles

[gabrielcrowe]

or enclose the description in some php that unescapes all the escaped characters.

[los_design]

or remove the delimiting factor altogether from actinic and allow it to parse your HTML cleanly as it would recognise the coding instructions on a WYSIWYG format within the frag and products etc?

[gabrielcrowe]

the problem with this is that...


actually, its not a problem, you're right.

get rid of that god damn pointless !!<>!! thing, its useless. 'nic should be able to just 'know' if it needs to insert html

[TraceyHand]

get rid of that god damn pointless !!<>!! thing, its useless. 'nic should be able to just 'know' if it needs to insert html

*mumbles*
I was moaning about this yesterday and got called a nutter :p
*stomps off in a fake strop*

[fergusw]

*looks to V9 hopefully........."

[los_design]

*mumbles*
I was moaning about this yesterday and got called a nutter :p
*stomps off in a fake strop*
put your vote here (http://community.actinic.com/showthread.php?t=33168) then :p

[magicalwonders]

I was moaning about this yesterday and got called a nutter
LOL. There is no justice in the world! ;)

Myles

[gabrielcrowe]

werent you were complaining about the mis-labelling of the 'insert html' part of the interface, that still requires the user to use the silly tags?

but still, the concept stands. something like this (http://tinymce.moxiecode.com/example_full.php) in actinic would be the best thing since sliced bread.

Developers? are you listening? :D

[pinbrook]

or set up an automatic keystroke thingy - hit a button o nthe keyboard and it types in the code - can't remember what its called

remembered it AutoIT

[gabrielcrowe]

AutoIT is perhaps one of the most useful tools ever.

Its a combination of visual basic and event hooker. wonderfully easy to code in.

[NormanRouxel]

this means adding HTML tags to the product descriptionYou may end up with gibberish in the printed reports and customer email. Best check these with some test embedded HTML before you commit to major changes.

[Sadcase]

Thanks for the suggestions - I look forward to the next version of Actinic!

[Sadcase]

You may end up with gibberish in the printed reports and customer email. Best check these with some test embedded HTML before you commit to major changes.
Thanks for pointing this out, Norman.

I've now checked the emails we use and they don't appear to show any problems, as they only show the name of the product (the HTML for which I've set up on the relevant templates). We don't use any of the inbuilt order processing as we export all our orders to Sage for processing.

But it was definitely worth checking as it didn't occur to me that this may have been a problem.