problem post update to 1.6

Also, my signup form no longer sends email to the notification alias, and doesn’t return to the designated page after pressing the save changes button in the front end; the changes are saved.

I’m not sure what is in that template, so I can’t comment specifically on the message you’re getting ot how it relates the latest plugin version. It may be that the sort function needs to be wrapped in a test to make sure that only an array is used.

You may want to turn off the PHP setting that dumps messages to the screen, that is for debugging, not something you want on a live site.

Your second comment sounds like two different issues. You’ll need to check on your settings to make sure the notifications are configured correctly. Nothing in the update would have changed that, although it is necessary to be using PHP version 5.2 or later.

For the save changes buttons….are you talking about editing the record or signing up?

Have you updated the example templates? That’s what I used as a baseline.

How does one turn off the PHP error messages? I’m running version 5.3 of PHP.

The saving changes issue comes up when updating an existing record. The update occurs, as the same URL is displayed, ending with ?pid=xxxx, but instead of re displaying the information, it shows “[pdb_record template=edit]”

I haven’t changed anything in notifications.

I decided to restore the previous version, in order to confirm the problems.

I found that the signup form notification is broken on the older version as well, so that is a different problrem.

In running the older version, I find that if I update the plugin settings page with ANY change, all of the drop drop selections for single entry, record update, etc, all disappear, and the site stops working, requiring that I restore it again.

Does reverting to the 1.5 code not work properly, and is there some reason that the information saved from the settings page would be broken?

Oh, and after the restore, the “manage database fields” tab no longer works.

Well, all these things work in both versions, so there is something particular to your setup that is breaking it. Taking a look at the PHP error log will help you figure out what’s wrong.

Downgrading the plugin is OK, if you do it right. You can run into problems if you try to overwrite the plugin, it’s better to completely delete it (using FTP, not the built in plugin delete, which would delete all your settings). Another way to downgrade is to install both versions of the plugin, just give the plugin folder a different name, then be sure to activate only one at a time. You’ll see both in the plugin page, so you can choose which version to run.

The PHP error messages are probably showing because you have WP_DEBUG set to true. If you want debugging to be on, you can set WP_DEBUG_DISPLAY to false to prevent the messages appearing. Generally, you shouldn’t have WP_DEBUG on for a live website.

I switched back to 1.6; I want to work through the problems, not be stuck on the old version.

WP_DEBUG is and has always been set to false.

I’m going to try to test the input value to sort() in your template example, and see if that removes the warnings; all of the places the warnings show up, the field is blank.

I still don’t understand why after the submit button I’m sent to a page with
“[pdb_record template=edit]”, rather than the page having just been updated. Is there something I can do to provide more information on this?

I don’t understand that either. You go to the page where you can update a record, it shows the record edit form, then when you submit the change, it shows the shortcode instead?

Have you tried temporarily using a default theme to see if it works there? This sounds like it might be the theme doing something fancy withe the content so the shortcode isn’t getting called, it’s showing the shorcode text instead.

In my template I added a check for empty record prior to the sort() call, and the warning errors are gone. Please consider doing this in your template example code.

On the second issue, if I remove the reference to my template for the pdb_record short code, the page works correctly. If I use the default record template without any changes, I get the same behavior. I need to make some changes to what’s displayed and what’s read only, so perhaps I need a new default record template?

Thanks.

BTW: I noticed there are new templates for 1.6; I’m trying them now. I should have known that the templates change from release to release.

The templates don’t usually change, but there were some minor changes to the list template in the 1.6 release. There isn’t a “sort” call in the default template, so this is something you’re doing in the custom template you are using.

Yes, I must have added the sort function from an example somewhere, sorry for the confusion.

So, I updated the record template to the version in 1.6, and then added my changes to it. When I include the short code [pdb_record template=edit], and name my template pdb-record-edit.php, my changes work but I get the same problem with displaying the short code text after submitting a change. If I rename the file to be pdb-record-default.php and change the short code to be [pdb_record], not only do my changes work, but I see the expected behavior after submit. Note, these files live in the templates directory under the child theme; I’m not touching the files in the plugin directory at all. I also tried the short code [pdb_record template=default], and it worked correctly as well.

The good news is you know where the problem is: in your custom template. Now, why it’s doing that, I can’t say, I’m not sure how that is possible.