Sign Up form not working

So, are you saying it works in the development site, but not in the production site? Is everything else working in your production site?

I suggest you revisit your plugin settings, make sure they are all correct.

When you submit the signup, it just shows you a blank signup form?

This could be because PHP sessions are not working, you can change the “use PHP sessions” setting (under the advanced tab) and see if that helps, although I doubt that will fix it if it was working in your development site.

Another thing to try is to clear any browser cookies from your site and try again–or use another browser that won’t have those cookies.

Well, it worked in the development site – before moving the site up a folder, I did upgrade to 3.9 – I’ll admit I don’t know if I tested this completely – i didn’t submit the sign up form for sure – then I also upgraded the participants database after i realized things weren’t working. It didn’t help.

As far as I can see the plugin settings are fine. I don’t think anything in there is path specific, right? Is it possible there’s a path somewhere that needs updating? Or permissions perhaps? I looked in the database – where are the settings for the plugin stored?? I don’t see them anywhere there…

I just tried unchecking the sessions box – no luck. I also tried all this in a browser i never use and it still doesn’t work. Now I’m seeing that I can’t edit participants from the control panel (admin) when yesterday I could. That seems odd.

Finally, I tried deactivating the plugin and reactivating it (I did this yesterday) – should I try that again??

Thanks for any help you can give me. I’m happy to send you a link to the signup if that helps.

Sharon

Ok, now everything is broken – links to the single record, the list, everything. This is really bad for me, my client was happy with it working last week and we were about to expose it for a board meeting to review it. What do you suggest?????

I used to link to the single record using ?pdb=1, but now in the instructions you say to use ?pid=1. Did that change???

Thanks so much,
Sharon

One last thing – I made a custom search for them, and I also use that for the list page – you can see it here. Can you take a look and see if something’s not right? At least the data comes up here:

https://canopy.org/caring-for-trees/arborist-list/search/

Thanks,
Sharon

Well, that is a lot to answer about. You’ll need to have a look at your PHP error log to get an idea what’s going on.

When you say link to a single record, how are you constricting this link? If it is for the pdb_single shortcode the link must include the record ID in the form ?pdb= If it is for the pdb_record shortcode, it is looking for the private ID and the link would be ?pid=

So they’re both right, but the context determines which one to use.

Thank you again for helping – sorry for so many questions.

I changed the pid back to pdb, still not working but I’m guessing that wasn’t the problem at all. I added some new data fields and I’m guessing those are causing the trouble. Here’s a few items from the log:

[07-May-2014 19:57:29] WordPress database error Unknown column ‘p.assist_with_palo_alto_tree_rem’ in ‘field list’ for query SELECT p.approved,p.arborist_name_1,p.arborist_name_2,p.arborist_name_3,p.arborist_summary,p.asca_member_1,p.asca_member_2,p.asca_member_3,p.assist_with_palo_alto_tree_rem,p.board_certified_master_1,p.board_certified_master_2,p.board_certified_master_3,p.cell_phone_number_1,p.cell_phone_number_2,p.cell_phone_number_3,p.certified_tree_risk_assessor_1,p.certified_tree_risk_assessor_2,p.certified_tree_risk_assessor_3,p.commercial_tree_care,p.construction_monitoring_servic,p.consulting_assessment_and_advi,p.consulting_for_palo_alto_devel,p.date_recorded,p.date_updated,p.email_address,p.emergency_tree_services,p.firm_address,p.firm_city,p.firm_name,p.firm_state,p.firm_zipcode,p.free_wood_chip_delivery,p.fruit_tree_pruning,p.id,p.informational_pdf,p.isa_1,p.isa_2,p.isa_3,p.large_tree_pruning,p.last_accessed,p.lumber_salvage,p.more_company_information_speci,p.office_phone,p.other_certifications_1,p.other_certifications_2,p.other_certifications_3,p.pesticide_application,p.private_id,p.services_summary,p.sick_tree_diagnosis,p.small_or_specialty_tree_prunin,p.stump_removal,p.total__of_isa_certified_arbori,p.tree_installation,p.tree_moving,p.tree_preservation_reports,p.tree_removals,p.tree_risk_assessment,p.tree_selection,p.website_url FROM dmv_participants_database p WHERE p.id = ‘6’ made by do_action(‘participants-database_page_participants-database-edit_participant’), call_user_func_array, Participants_Db::include_admin_file, include(‘/plugins/participants-database/edit_participant.php’), Participants_Db::get_participant

[07-May-2014 19:57:30] PHP Warning: array_merge() [function.array-merge]: Argument #1 is not an array in /home3/canopyor/public_html/wp-content/plugins/participants-database/participants-database.php on line 1664

[07-May-2014 14:09:43] PHP Warning: next() [function.next]: Passed variable is not an array or object in /home3/canopyor/public_html/wp-content/plugins/participants-database/classes/PDb_Shortcode.class.php on line 497

[07-May-2014 14:09:43] PHP Warning: key() [function.key]: Passed variable is not an array or object in /home3/canopyor/public_html/wp-content/plugins/participants-database/classes/PDb_Shortcode.class.php on line 500

[07-May-2014 20:10:36] WordPress database error Unknown column ‘p.assist_with_palo_alto_tree_rem’ in ‘field list’ for query SELECT p.approved,p.arborist_name_1,p.arborist_name_2,p.arborist_name_3,p.arborist_summary,p.asca_member_1,p.asca_member_2,p.asca_member_3,p.assist_with_palo_alto_tree_rem,p.board_certified_master_1,p.board_certified_master_2,p.board_certified_master_3,p.cell_phone_number_1,p.cell_phone_number_2,p.cell_phone_number_3,p.certified_tree_risk_assessor_1,p.certified_tree_risk_assessor_2,p.certified_tree_risk_assessor_3,p.commercial_tree_care,p.construction_monitoring_servic,p.consulting_assessment_and_advi,p.consulting_for_palo_alto_devel,p.date_recorded,p.date_updated,p.email_address,p.emergency_tree_services,p.firm_address,p.firm_city,p.firm_name,p.firm_state,p.firm_zipcode,p.free_wood_chip_delivery,p.fruit_tree_pruning,p.id,p.informational_pdf,p.isa_1,p.isa_2,p.isa_3,p.large_tree_pruning,p.last_accessed,p.lumber_salvage,p.more_company_information_speci,p.office_phone,p.other_certifications_1,p.other_certifications_2,p.other_certifications_3,p.pesticide_application,p.private_id,p.services_summary,p.sick_tree_diagnosis,p.small_or_specialty_tree_prunin,p.stump_removal,p.total__of_isa_certified_arbori,p.tree_installation,p.tree_moving,p.tree_preservation_reports,p.tree_removals,p.tree_risk_assessment,p.tree_selection,p.website_url FROM dmv_participants_database p WHERE p.id = ‘7’ made by require(‘wp-blog-header.php’), require_once(‘wp-includes/template-loader.php’), include(‘/themes/canopy/whiterightcol.php’), the_content, apply_filters(‘the_content’), call_user_func_array, do_shortcode, preg_replace_callback, do_shortcode_tag, call_user_func, Participants_Db::print_single_record, PDb_Single::print_record, PDb_Single->__construct, Participants_Db::get_participant

[07-May-2014 20:10:36] PHP Warning: array_merge() [function.array-merge]: Argument #1 is not an array in /home3/canopyor/public_html/wp-content/plugins/participants-database/participants-database.php on line 1664

It looks like it doesn’t like one of my new columns – ideas? Have I added too many?

Sharon

Also, at some point, I think put a copy of the files for PDB in my template directory – sort of like a child theme – do those need to be updated since I updated the plugin??? Sorry, I set this up a few months ago…memory is a bit fuzzy.

Sharon

Just realized that I added some new columns that have long names – in the database, the column is longer than the one in the error message above. I’ll try recreating those with shorter names. I removed them and I can now see the entries – I will test the form to add an entry later (I have to run out).

Thanks for the tip on checking the error logs. Ignore my super long error log unless you see other errors that might be insightful!

More soon and thanks,
Sharon

Yes, Sharon, there was a bug with older version of the plugin when really long names were used. You figured it out…you need to rename those fields so the name in the “fields” table matches the column name in the main database.

Thanks so much for the guidance, that fixed it completely!!