[Pro] Update for easiForm users

Freeway
1

The easiForm action (v1.49) has been updated to be friendly to the PHP changes as of PHP 5.3 , this version as the previous version of the action is Freeway 6 Pro friendly and can be used with Freeway Pro versions from 4 and above. The action can be downloaded from Actionsforge: PHP easiForm - ActionsForge or from the http://easibase.com/ web site.

This v1.49 action update is a bit overdue due to a shortage of my time for making the changes needed to the easiForm script and encryption process, this update now brings the easiForm script up to v1.87.
Many servers are now using or starting to use PHP 5.3 so this update will prevent the need for using the PHP error_reporting action to suppress any deprecated warnings, if you where using the PHP error_reporting action to suppress these warnings I suggest when you update the PHP easiForm action you now either remove the PHP error_reporting action or deactivate it unless you are using it for other reasons.

freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

2

Mike, from bitter recent experience, you owe it to yourself to get a machine somewhere (a $5 digitalocean.com VPS, maybe) with PHP 5.4, install your app there, and turn on E_ALL error reporting.

MyActiveRecord, which ran nicely on PHP 4.2 on up, can make a multi-gigabyte-sized error log in no time under 5.4. I had a host change me to 5.4 recently, and then wondered why I ran out of disk space.

While you may think this is not the current version, it is coming fast to a hosting provider near you. 5.6 is the current alpha, 5.5 the current beta, 5.4 is the new stable, and anything that ran on 5.3 and used the OO style of coding is probably not going to run clean in 5.4.

Walter

On Apr 13, 2013, at 3:06 AM, Mike B wrote:

The easiForm action (v1.49) has been updated to be friendly to the PHP changes as of PHP 5.3 ,

freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

3

Hi Walter,
Thanks for the heads up but I switched my server around from PHP 5.3 to PHP 5.4 a couple of times this last week or so specifically for this reason.

I was looking into an error someone was getting on their server and discovered that a some changes for PHP 6 seem to have been brought forward to 5.4. It would seem there might be a lot of problems coming up for quite a few people who might end up getting caught with their socks down, if it hadn’t been for the error someone reported I would not have realised that some changed had been brought forward to 5.4

Did you mention this because I had mentioned PHP changes as of 5.3 or was there something specific to easiForm?

Mike

On Apr 13, 2013, at 4:0 PM, Walter Lee Davis wrote:

Mike, from bitter recent experience, you owe it to yourself to get a machine somewhere (a $5 digitalocean.com VPS, maybe) with PHP 5.4, install your app there, and turn on E_ALL error reporting.

MyActiveRecord, which ran nicely on PHP 4.2 on up, can make a multi-gigabyte-sized error log in no time under 5.4. I had a host change me to 5.4 recently, and then wondered why I ran out of disk space.

While you may think this is not the current version, it is coming fast to a hosting provider near you. 5.6 is the current alpha, 5.5 the current beta, 5.4 is the new stable, and anything that ran on 5.3 and used the OO style of coding is probably not going to run clean in 5.4.

Walter

On Apr 13, 2013, at 3:06 AM, Mike B wrote:

The easiForm action (v1.49) has been updated to be friendly to the PHP changes as of PHP 5.3 ,

freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

4

I was hoping you would not get caught flat-footed as I was. No specific issue I am aware of in your software. You mentioned 5.3, but not 5.4, and I said “Uh-oh! Giant pothole ahead!”

Walter

On Apr 13, 2013, at 6:55 PM, Mike B wrote:

Did you mention this because I had mentioned PHP changes as of 5.3 or was there something specific to easiForm?

freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

5

Thanks for the thought.

Just on a side note to the thread, I should really start another thread in Dynamo for this but:

I came across a couple of Warnings in some scripts I had on one of my web sites, nothing to do with easiForm, this was a configuration file:

$someVar = end(explode("/",__FILE__));

returns: ‘Strict Standards: Only variables should be passed by reference in…’, not a major but it still takes time to go through every script to fix! :wink:

Then one I just couldn’t get to the bottom of:

Warning: Illegal string offset ‘subject’

$SA['mail']['error']['subject'] = $SA['site']['name'] . ' Some text';

To get around the problem I ended up replacing this with:

$SA['mail']['errorsubject'] = $SA['site']['name'] . ' Some text';

I tried changing ‘error’ to ‘anerror’ and ‘subject’ to ‘asubject’ but the Warning just updated from ‘subject’ to ‘asubject’!

Some of the things seem really trivial but can be difficult to get to the bottom of… but then it seems that these changes are bringing PHP more into line with your pet ‘Ruby’ from what I have read. :wink:

Mike

On Apr 14, 2013, at 1:11 AM, Walter Lee Davis wrote:

I was hoping you would not get caught flat-footed as I was. No specific issue I am aware of in your software. You mentioned 5.3, but not 5.4, and I said “Uh-oh! Giant pothole ahead!”

Walter

On Apr 13, 2013, at 6:55 PM, Mike B wrote:

Did you mention this because I had mentioned PHP changes as of 5.3 or was there something specific to easiForm?

freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

6

On 13 Apr 2013, 7:06 am, Mike B wrote:

The easiForm action (v1.49) has been updated to be friendly to the PHP changes as of PHP 5.3 , this version as the previous version of the action is Freeway 6 Pro friendly and can be used with Freeway Pro versions from 4 and above. The action can be downloaded from Actionsforge: PHP easiForm - ActionsForge or from the http://easibase.com/ web site.

This v1.49 action update is a bit overdue due to a shortage of my time for making the changes needed to the easiForm script and encryption process, this update now brings the easiForm script up to v1.87.
Many servers are now using or starting to use PHP 5.3 so this update will prevent the need for using the PHP error_reporting action to suppress any deprecated warnings, if you where using the PHP error_reporting action to suppress these warnings I suggest when you update the PHP easiForm action you now either remove the PHP error_reporting action or deactivate it unless you are using it for other reasons.

Mike, thanks for the update. Aside from deactivitating the PHP error_reporting action, do I simply install this over the previous action or are there other files I need to update?

freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

7

Just install it over the old action and up load the form again.

It should be as simple as that.

Mike

On Apr 14, 2013, at 8:49 AM, RavenManiac wrote:

On 13 Apr 2013, 7:06 am, Mike B wrote:

The easiForm action (v1.49) has been updated to be friendly to the PHP changes as of PHP 5.3 , this version as the previous version of the action is Freeway 6 Pro friendly and can be used with Freeway Pro versions from 4 and above. The action can be downloaded from Actionsforge: PHP easiForm - ActionsForge or from the http://easibase.com/ web site.

This v1.49 action update is a bit overdue due to a shortage of my time for making the changes needed to the easiForm script and encryption process, this update now brings the easiForm script up to v1.87.
Many servers are now using or starting to use PHP 5.3 so this update will prevent the need for using the PHP error_reporting action to suppress any deprecated warnings, if you where using the PHP error_reporting action to suppress these warnings I suggest when you update the PHP easiForm action you now either remove the PHP error_reporting action or deactivate it unless you are using it for other reasons.

Mike, thanks for the update. Aside from deactivitating the PHP error_reporting action, do I simply install this over the previous action or are there other files I need to update?

freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

8

Non need to update ionbase?

freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

9

As long as the ioncube loader is in the ioncube folder for your version of PHP then no.

If this is a GoDaddy account:
As long as you have already set the GoDaddy account up for using ioncube for your version of PHP and the loader version is in the ioncube folder then there is nothing else to do.

HTH

On Apr 14, 2013, at 3:4 PM, RavenManiac wrote:

Non need to update ionbase?

freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

10

On Apr 13, 2013, at 7:54 PM, Mike B wrote:

Thanks for the thought.

Just on a side note to the thread, I should really start another thread in Dynamo for this but:

I came across a couple of Warnings in some scripts I had on one of my web sites, nothing to do with easiForm, this was a configuration file:

$someVar = end(explode("/",__FILE__));

returns: ‘Strict Standards: Only variables should be passed by reference in…’, not a major but it still takes time to go through every script to fix! :wink:

Then one I just couldn’t get to the bottom of:

Warning: Illegal string offset ‘subject’

$SA['mail']['error']['subject'] = $SA['site']['name'] . ' Some text';

To get around the problem I ended up replacing this with:

$SA['mail']['errorsubject'] = $SA['site']['name'] . ' Some text';

I tried changing ‘error’ to ‘anerror’ and ‘subject’ to ‘asubject’ but the Warning just updated from ‘subject’ to ‘subject’!

The error is pretty clear. You are expecting $SA[‘mail’][‘error’] to be an array or an object, containing a key called ‘subject’. But at that point in your program, $SA[‘mail’][‘error’] is a string, and there is no offset in it called subject. Try putting a print_r($SA['mail']['error'] ); on the previous line, followed by an exit; and see what happens when you visit that page.

Some of the things seem really trivial but can be difficult to get to the bottom of… but then it seems that these changes are bringing PHP more into line with your pet ‘Ruby’ from what I have read. :wink:

From what I have seen, PHP is chasing Java (a curious thing, given PHP’s roots in Perl, and the diametric opposition of those two ancestors’ object models). Ruby is often referred to as the bastard love-child of Perl and SmallTalk, two more different parents you are unlikely ever to find. (What does he see in her?)

Walter

freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

11

Right, I found out what was making this php ‘Warning:’ seem so confusing.

What I couldn’t understand was why it was happening in the script this was used while in another file where a similar array was used there was no warning… the second file was including another file… that had error_reporting suppressed! I normally have this tied into the configuration file but for some reason I had error_reporting set in the other included file so wasn’t expecting supression there.

I have an expression I normaly use for descibing this… but I couldn’t use it here!

Mike

On Apr 14, 2013, at 4:43 PM, Walter Lee Davis wrote:

Then one I just couldn’t get to the bottom of:

Warning: Illegal string offset ‘subject’

$SA['mail']['error']['subject'] = $SA['site']['name'] . ' Some text';

To get around the problem I ended up replacing this with:

$SA['mail']['errorsubject'] = $SA['site']['name'] . ' Some text';

I tried changing ‘error’ to ‘anerror’ and ‘subject’ to ‘asubject’ but the Warning just updated from ‘subject’ to ‘subject’!

The error is pretty clear. You are expecting $SA[‘mail’][‘error’] to be an array or an object, containing a key called ‘subject’. But at that point in your program, $SA[‘mail’][‘error’] is a string, and there is no offset in it called subject. Try putting a print_r($SA['mail']['error'] ); on the previous line, followed by an exit; and see what happens when you visit that page.
Walter

freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options