stickpeople

I do and it still doesn’t. Switching to a different plugin.

Correction. It is working now. The update to 5.3 took longer to implement than anticipated.

That did not fix the issue. The name still does not display correctly.

I am having this same issue of a fatal error on line 79. I am using PHP 5.3. Any other suggestions on how to fix this issue?

There is an incompatibility with wpForo. I get this same fatal error from the new-user-approve plugin which I’ve had installed prior to installing your forum plugin. The error doesn’t occur when using the wp-login screen to register a new account. It only happens when using the wpForo user registration.

It’s not as easy as just deactivating the New User Approve plugin, because I do want to be able to approve new users before allowing them to create an account. There doesn’t seem to be a good clean alternative to it that I can find.

I get this error message too when registering from the wpForo forums registration page.

Sadly, it appears the developer is no longer supporting this plug-in. I was going to purchase the add-on for this, but it seems it would be throwing my money away.

• This reply was modified 7 years, 9 months ago by stickpeople.

Changing to a textarea wouldn’t have any on affect how the update is done. If you want to use a textarea because it’s larger then you have the option of using the custom fields form which already uses a texarea input.

But, this is why I started this thread in the first place. Updating using the custom fields form is confusing and frustrating because it does not save the changes logically with the click of the page update, like it does when making the change in the attribute field.

Is it truly that difficult to change the attribute to a text area so it is easier and more logical to make changes there where changes won’t get lost with the click of the page update?

Obviously we are going in circles….

Can you at least update the plugin so that the attribute field is a textarea format to make it easier to update those values?

So then what? You have not intention of fixing it?

And, it is not true that “updating an attribute field won’t immediately update the corresponding field” as I said in my previous post. A change to the attribute field (which is created from the add custom/update field function you include with the plugin) will update both the attribute and custom field values with the page update function.

When you make a change to the custom field value and click on the custom field update, it does not make the change to the attribute value. So when you then click the page update, it takes the un-updated attribute value and puts it back in the custom field value…so the update to the custom field is lost.

Given the structure of those two sections on the event edit page, the more logical and convenient place to make the update would be in the custom field section. As I said before making the change to the value in the attribute section is not so good since the values are not textarea input fields.

You are correct, it made no difference. One thing I noticed is that whenever a custom field is created, a corresponding attribute is created below with the same name and the field value. If I update the custom field value, it does not also update the Attribute Value, which appears to be the culprit. The custom field update should also trigger a save on the attribute / page. If I change the attribute value and do a page save, then the change is saved in both the attribute and the custom field.

Making the updates to the value in the Attributes section would be fine, but it’s a bit more cumbersome because the Attribute Value field is not an expandable textarea field.

Screen Shot of Custom Fields and Attributes edit

• This reply was modified 7 years, 12 months ago by stickpeople.
• This reply was modified 7 years, 12 months ago by Steven Stern (sterndata).

I am attempting only use one field called ti-payment-info. I have tested with an additional field at your request called ti-new-field. Either with one field or two fields, I get the same issue. I have created these custom fields with your plugin. I’m beginning to think I may need to look elsewhere.

Thanks for getting back. Yes, it appears we are running an older version of PHP and will ask the host to upgrade us. I will let you know if that doesn’t fix the issue.

Thank you for your quick response!

WP: 4.7.3
bbPress: 2.5.12

Now it is throwing this Fatal error when trying to activate:

Parse error: syntax error, unexpected T_FUNCTION in /wp-content/plugins/bbp-toolkit/includes/subscriptions.php on line 96

I tried deactivating my plugins and still got the error.

I tested with a different custom field, and I get the same exact issue. The custom field name is ti-new-field.

I can create the field and click on the page update it it will remain, but when I make a change to the Value of the custom field and click on the custom field “Update” the change of the value will remain. But, if I then click on the page Update, the custom field value loses the recent update. The only way that it will retain the change to the custom field value is if I exit the event edit page and return to it to make updates to the changes to the event content.

I don’t see why testing another field would make any difference. The name of the custom field I created…using your plugin…is ti-payment-info. I have not found anywhere in my installation with that name.

It has been over 2 weeks since I first reported this. Is there any actual plan of looking into this, or just delay with continuous questions?