Newsletter Manager Problem

[oconnell12]

I've had the site up and running for a while now and have finally come round to trying out the Newsletter manager and have hit a couple of problems.

1. Any newsletter that is created either within FCKEditor or externally, shows the following error when I come to send it;
Warning: preg_match() [function.preg-match]: Unknown modifier '>' in /home/karluadmin/public_html/holly/includes/modules/newsletters/newsletter.php on line 46
Has anyone else come acroos this?? .

2. If I create an HTML newsletter in expressionweb, for instance, and then paste the source code into the FCKeditor, when I come to send, there are lots of extra blank lines appearing between boxes and tables and the alignment is all messed up, even though the layout looks fie whilst in the editor. The same HTML code goes out fine via normal email from Outlook.

Anybody out there come across the same issues?

[ridexbuilder]

"FCKEditor" - this tells us that you are not using the current 2.0.25 release of 'Max.
You could try to remove the teletype tags in line 46 and see if that makes a difference.

<tt>monospaced</tt>

(See if you can edit your post to read .../public_html/myadmin/includes...)

[oconnell12]

Hi

Nope not on the latest version - had too many issues putting this one in to look at upgrading just yet!

There is no /tt on or near line 46.

The only line in the file that has pre_match or the /tt is at line 229
<td><tt><?php echo (preg_match('<.*>',$nInfo->content)?$nInfo->content:nl2br($nInfo->content)); ?></td>

There seems to be a lot of unanswered issues on line spacing within standard OSC as well - so I'm startign to think that this may be an OSC family "feauture"??

[oconnell12]

sorry forgot to say that I tried removing the </tt> at line 229 and unfortunatley no difference.

[ridexbuilder]

Well, I only have versions going back to 2.0.4 available to me. You should NOT really be using any version older than this and it's unsurprising that they're are bugs!
So many areas of the software has been fixed, changed and enhanced that you can't really compare 2.0.25 to obsolete software.

Considering that the fault lies at line 46, it's hardly surprising. As, above I have no means of looking at the file and frankly, not worth my time - maybe someone else will.

I strongly suggest that you make a concerted effort to install a fresh version of 'Max then migrate the data over.