[phorm] [Phorm:] Re: Error 123 - Unable to save file - Resolved

  • From: webbbs@xxxxxxxxx
  • To: support@xxxxxxxxx
  • Date: 6 Jan 2004 22:36:24 -0000

The following new message has been posted on Phorm Support Forum at 
<http://www.phorm.com/support/>. 

*************************************************************************** 

  MESSAGE:  (#3553) Re: Error 123 - Unable to save file - Resolved 
            <http://www.phorm.com/support/?rev=3553> 
  AUTHOR:   Michael Payne 
  DATE:     January 6, 2004 at 5:36 p.m. EST 

  Reply To: (#3551) Re: Error 123 - Unable to save file 
  Author:   Michael Payne 
  Date:     January 5, 2004 at 11:25 a.m. EST 

Problem resolved - Downloaded phorm 3.5.1 and followed what appears to be a 
new rules text format. Then received the parse error - this was resolved from 
an earlier forum response from a guy called Richard who posted the following 
comments- 

"Have you tried changing line 169 of functions.php? I'm pretty sure that's the 
source of the problem. Change: 

else eval("\$ph_SubVal = \$$ph_SubVar;"); 

to 

else eval("\$ph_SubVal = \$\$ph_SubVar;"); 

If it doesn't fix your problem, you can always change it back" 

This worked a treat. Now I'm a back up and running, and wish to congratulate 
Holotech on an excellent product! 

*************************************************************************** 

This is an automatically-generated notice.  If you'd like to be removed from 
the mailing list, please visit Phorm Support Forum at 
<http://www.phorm.com/support/>, or send your request to webbbs@xxxxxxxxxx  If 
you wish to respond to this message, please post your response directly to the 
board.  Thank you! 
-------------------------------------------------
You are receiving this message because you are subscribed to the Phorm mailing 
list. To send messages to the mailing list, simply send email to 
phorm@xxxxxxxxxxxxx from the address you have subscribed. You may unsubscribe 
from the list by sending email to phorm-request@xxxxxxxxxxxxx with 
'unsubscribe' in the SUBJECT field.

Other related posts: