Billmel

That did it! Thanks!

The contents of the drop down list look like this:

0::Alaweo Pl, 1::Alaweo St, 2::Aulena Pl, 3::Ehupua Pl, 4::Ehupua St, 5::Hanahanai Pl, 6::Hapai St, 7::Hawane, etc.

I can arrange for you to access the site, but it’s painful, and would require two different passwords to access. Please let me know if that’s what you need.

I just sent the HTML to your support mailbox. Let me know if you need anything else. The page itself has not changed in years.

P.S. the other information, including Mailing address, would also be helpful.

One other, odd thing. When I configure the plugin as you describe in your email, it appears to work each time I change the approval field from the admin back end, but it doesn’t work when I use the front end. Likewise, when I use the front end, if I have “Send Record Form Update Notification Email” checked, I get an email when the record is updated, but if I update the same record from the admin back end, no notification is sent.

Mahalo!

The way I’ve setup my database, the “approval” field is a checkbox in a multi-checkbox array of values, in this case a string of years. There used to be documentation on how to print out an entire record for debugging purposes, so either I need that again, or some clue as to how to reference an array element value in the example code to key off of.

Mahalo!

This new example is very helpful. In the example email, it looks like you can include values from the database, as you can with the other mail options in the plugin. Can HTML be included in the outgoing mail as well? Specifically, I’d like to include a URL.

• This reply was modified 8 years, 3 months ago by Billmel.

This works for me as well, but if I choose another page, it puts me at the very bottom of the page, not at the top. Is this a CSS thing?

Problem solved; user error. Thanks Roland!!

Information sent to [email protected]

No page cache. I did try re-saving the permalinks, and I just tried updating to the latest version of PDB, after disabling ALL other plugins. No difference; still get taken to the 404 error page after saving an edited record from the front end. Exactly same code worked in pre-1.7 PDB.

With the update, I can now go to the edit_record page in the front end, and make changes to the record. However, when I save those changes, I’m taken to a “404” error page, which unfortunately doesn’t tell me what page it was trying to find. I was using a custom template from 1.6, but I changed the page to just a [pdf_record], and it still doesn’t save correctly.

Mahalo

Is there any chance that a simple mechanism to show all the records could be created, so that the theme can handle the output records as it sees fit? The theme developer doesn’t seem inclined to provide support in disabling their customer scrolling feature…

Worked like a charm, Mahalo!

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.