mukasama

I did a bit more troubleshooting but still no luck. I have found the teccc_stylesheet in the uploads folder and it is being correctly called as https:// in the page header.

The page is at: https://discoveryvoyages.com/rates-schedules/

When I use Web Developer Tools to look at the code and styles, I can select the h2 a block level element that is usually colored: h2.tribe-events-list-event-title but it doesn’t have a background-color. The color doesn’t appear to be being overwritten or superceded by another css element. It seems like their is no category-specific selector that would trigger the background-color.

Here is a sample of the css from the teccc_stylesheet:

.tribe-events-category-3-day-classic-voyage h3.tribe-events-list-event-title,
.tribe-events-shortcode .tribe-events-month table .type-tribe_events.tribe-events-category-3-day-classic-voyage,
.tribe-events-list-widget li.tribe-events-category-3-day-classic-voyage h4,
li.tribe-events-list-widget-events.tribe-events-category-3-day-classic-voyage h4,
.events-archive.events-gridview #tribe-events-content table .type-tribe_events.tribe-events-category-3-day-classic-voyage,
.teccc-legend .tribe-events-category-3-day-classic-voyage,
.tribe-events-calendar .tribe-events-category-3-day-classic-voyage,
#tribe-events-content .tribe-events-category-3-day-classic-voyage > .tribe-events-tooltip h3,
.type-tribe_events.tribe-events-category-.tribe-events-category-3-day-classic-voyage h2,
.tribe-events-category-3-day-classic-voyage > div.hentry.vevent > h3.entry-title,
.tribe-events-mobile.tribe-events-category-3-day-classic-voyage h4
{
background-color: #7a209b;
border-left: 5px solid #CFCFCF;
border-right: 5px solid transparent;
color: #fff;
line-height: 1.4em;
padding-left: 5px;
padding-bottom: 2px;
}

I am having the same issue. I just changed everything on the site to work with our SSL certificated. Everything is now working except for the category colors not showing up. They were showing up before the change.

I don’t see any .css document in the Uploads folder. What should I be looking for? I also don’t see a link to a category color css in the page source.

I had tried with both one underscore and two beforehand. I just tried adding back the extra underscore and it still doesn’t work. I have confirmed that I have universal tracking implemented. I am using:

“__gaTracker(‘send’, ‘event’, ‘Contact Form’, ‘Submit’);”
and I get an “Uncaught SyntaxError: Invalid or unexpected token”

(If I use: on_sent_ok: “ga(‘send’, ‘event’, ‘Contact Form’, ‘Submit’);” I get: Uncaught ReferenceError: ga is not defined)

I am using the MonsterInsights plugin to insert the Analytics tracking code into my site. The tracking code inserted is:

<!– This site uses the Google Analytics by MonsterInsights plugin v5.5.2 – Universal enabled – https://www.monsterinsights.com/ –>
<script type=”text/javascript”>
(function(i,s,o,g,r,a,m){i[‘GoogleAnalyticsObject’]=r;i[r]=i[r]||function(){
(i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o),
m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m)
})(window,document,’script’,’//www.google-analytics.com/analytics.js’,’__gaTracker’);

__gaTracker(‘create’, ‘UA-766614-2’, ‘auto’);
__gaTracker(‘set’, ‘forceSSL’, true);
__gaTracker(‘require’, ‘displayfeatures’);
__gaTracker(‘send’,’pageview’);

</script>
<!– / Google Analytics by MonsterInsights –>

I hope that helps. Not sure what else to try.

FYI: When submitting the form the page produces the following error messages:

Uncaught ReferenceError: _gaTracker is not defined
or
Uncaught ReferenceError: ga is not defined

Yes, you are right on. I recently changed to universal tracking. Can you be more specific though about the code I need to enter in the Additional Settings box? I have tried all of the following, but the green success message still does not appear:

old code that worked before switch to universal tracking:
on_sent_ok: “_gaq.push([‘_trackPageview’, ‘/Contact-Success-Thanks/’]);”

new attempts that don’t work:
on_sent_ok: “_gaTracker(‘send’, ‘event’, ‘Contact Form’, ‘Submitted’);”
on_sent_ok: “ga(‘send’, ‘pageview’, ‘/Contact-Success-Thanks/’);”
on_sent_ok: “ga(‘send’, ‘event’, ‘Contact Form’, ‘Submitted’);”

Checking the “Redirect to File” box worked for me as well. I also got a file not found error due to permission issues. Instead of moving the files to a new folder, I deleted the .htaccess “denyfromall” file in the dlm_uploads folder. That worked, and saved some work.

Will do. Thanks for the suggestion.

I am using WP Super Cache with the default settings

OK, I will talk to the client and get back to you by email to discuss scope and budget if they want to make it work better for next year (this is an annual signup), which I will recommend. Unfortunately, the timeline is too soon to make that work for this year since they have calendar dates that can’t be changed. Right now the form is set up completely kosherly (i.e. following multi-page form instructions for all shortcodes and not providing the Lost Link on the signup page, but putting it on its own page), yet it is still giving me a Record Not Found error on page 3 or 4 of the form (it varies) in IE, Firefox and Safari (Chrome seems more resilient), and then throwing the same Catchable Fatal Error in those browsers:

Catchable fatal error: Argument 2 passed to Participants_Db::replace_tags() must be of the type array, boolean given, called in /–full-path-redacted–/wp-content/plugins/participants-database/participants-database.php on line 2942 and defined in /–full-path-redacted–/doyoncandidate/wp-content/plugins/participants-database/participants-database.php on line 2953

I will investigate other Form plugins this weekend to see if I need to completely change gears. Let me know if you know of any I should look at. I will also re-install everything I have created so far on a new WordPress site, and see if I can at least get it to work as intended on most major browsers. I don’t know if it will be acceptable to the client to have them complete the entire form in one sitting, but that’s a starting place at least.

Marking this as resolved while exploring solutions in other open thread on “weirdness.”

(I will mark the other open thread as resolved so we can keep any additional discussion on this one.)

Thanks, this helps I think. Though am still deciding where to go with it. One clarification: I already use the [pdb_request_link] on a separate page, and not the [pdb_signup] method for getting them their link. When they use it they ALWAYS reenter at the first page with the [pdb_record…] shortcode on it, even if they have completed more pages, and they can use the “save and next” (aka submit) button to review what they have entered and get to where they left off. But it sounds like even this is not within the tested use of the plugin. So.

I could go back to my original method and have them just complete and submit the signup fields (and none of the other field groups) (i.e. a [pdb_signup] with no actions that takes them right to the thank you page, and then they can use their private link to return and enter the rest of the paged field-groups, then return to the same thank you page on completion. I believe you said there were also issues with not having an action with the original [pdb_signup] shortcode, though it worked in initial testing. The single thank you page was the main usability issue, but I may be able to overcome that through better wording and design cues. Before I do that let me know if there are fundamental technical issues with this approach that would argue against it.

Are you available/interested in doing any custom development needed to either a) create a separate custom thank-you page template for initial sign up and then for completion of multipage form; or b) a different/better solution for allowing someone to fill out long multi-page forms in more than one sitting (and ideally allowing them to come back to where they left off)? Let me know and I can send an email to your support address to follow up on timing and pricing.

Still getting a Record Not Found when going from one page to another in the multi-page form (often from page 2 to 3 or page 3 to 4). Also still getting the “catachable fatal error” noted above when paging through the multi-page form. At other times it works fine in Chrome, but in IE and Firefox it almost never works.

OK, you say “I would recommend against [placing a link to the “lost private link” form on some of your form pages] because you’re going to get people who have unfinished forms visiting a page with the retrieve link form and that’s asking for trouble.”

Can you explain why this is trouble? Once they start a record, they have an ID, so why can’t we email them a link?

Another solution to the “very long form” issue that I tried initially was to have them just fill out one page of it with their personal info and then send them immediately to the thank you page (no action to take them to page 2), so they could get their link, and then choose to continue entering info (I had a button-styled link that said “I’m ready to Continue” which took them to the first page of the multi-page pdb_record) or use the link to come back later. However, they end up on the same Thank You form when they finish the last screen of the pdb_record, so that was confusing. I broke that into two halves (New Applicants and Returning Applicants) with separate instructions (New users could see their link or choose to continue; People who had filled out the whole form could click on the button-styled link to go to the signature page). But that failed in usability testing because the people who elected to finish the form in one setting didn’t feel like they were “returning” and ignored that message.

This is all to say that having one single flow from signup through thank you (as in your multi-page tutorial) seemed to work best AS LONG AS we can give users an EARLY way to retrieve their link. If this is indeed asking for trouble, then I’m out of ideas for making this work for such a long form. I’m open to any ideas.

Thanks for the insights and tips. That makes sense about the lost link function placed on the signup form not useful for multi-page forms, because your right that that didn’t make sense to me. I had already disabled it.

I do have a page with the “request-link” shortcode on it. (https://doyoncandidate.iialaska.com/request-link/) Because this form is so darn long (20 pages of grouped fields – and no I didn’t design it ?? I think it is really important that 1) people know they can stop at the end of any page and come back to finish later (some pages will take some time/research to fill in so the whole thing could take a couple hours); and 2) it should be possible (and obvious) that they can request a link to come back later BEFORE they get to the final screen (thank you) page, since they may not be able to finish the form in one sitting.

My solution was to put a link to the page with the request link shortcode on it at the bottom of every PDB_Record page (I put it in a copy of the pdb-record-default.php template saved in my child them, just below the table), so it appears on every RECORD page, but not on the initial SIGNUP page.

I have UN-done my prior “temporary solution” of moving the PDF_signup_thanks message text from the Settings page. We can see if the issue of it being inserted in the middle of the request-link form page occurs again.