seeker286
Forum Replies Created
-
I seem to have the same problem. Can you share what caused your issue, and how you fixed it?
Update: I had tried to manually update Jetpack from 5.6.1 to v. 5.7 and WP Maintenance Mode from 2.0.9 to 2.1.2. I got a “Site down for maintenance” message that took much longer than usual to resolve (several minutes vs. typically seconds). However, it eventually timed out, and I’m up and running again.
- This reply was modified 6 years, 9 months ago by seeker286.
Forum: Plugins
In reply to: [Contact Form DB] Compatible with PHP 7?Thanks for the prompt response!
It’s working for me. Thanks for taking on this project!
Same as last release – users can proceed to checkout even without checking the “required” checkbox.
Thanks Visser, I just subscribed on your site (B. Hall).
Hi Visser, I just installed 4.0.3, and I’m still having the same issue. I understand you have lots on your plate, and this isn’t urgent for me.
Hi Visser, thanks for your quick response. We’re only using one Additional field, however I just tried adding a similar field to Billing and got the same result.
It would be great if the developer resumes work on the plug-in. In the meantime, it’s too easy for clients to unknowingly install the update and break their site.
Can the available version be rolled back to the 3.6.8 stable release?
Works like a charm. Thanks!
Aha! I finally found the problem.
In Settings > Formatting tab > Search Form > Country > Default Country. If this has any country selected, events with no location will not be displayed in search results.
I changed it to “No default country,” and the search form is working as desired.
Default location has always been blank (“no default location”).
Default country was originally US, but I’ve changed it to “no default country,” and I’m still seeing the same issue.
Here’s an update. I checked the SQL query that’s not showing results:
SELECT wp_em_events.post_id FROM wp_em_events LEFT JOIN wp_em_locations ON wp_em_locations.location_id=wp_em_events.location_id WHERE (<code>recurrence</code>!=1 OR <code>recurrence</code> IS NULL) AND ( event_start_date >= CAST('2014-12-05' AS DATE) OR (event_end_date >= CAST('2014-12-05' AS DATE) AND event_end_date != '0000-00-00' AND event_end_date IS NOT NULL)) /************************************/ /************************************/ AND location_country='US' /************************************/ /************************************/ AND (wp_em_events.post_id IN ( SELECT object_id FROM wp_term_relationships WHERE term_taxonomy_id IN (28) )) AND (<code>event_status</code>=1) GROUP BY wp_em_events.post_id ORDER BY event_start_date ASC, event_start_time ASC, event_name ASC LIMIT 10 OFFSET 0
Note that even though it is left joining to the Locations table, it is requiring that the Country is US. If I remove that part and run the query directly in my database, it returns the correct records.
Now, the question is how to prevent Events Manager from including that criteria. I tried removing the default country (US), but it didn’t help: https://stlwildones.org/calendar/. Here are my location settings:
– Default location: none
– Default country: US
– Enable locations: yes
– Require locations: no
– Use dropdown for locations: no
– Enable location attributes: no
– Enable location custom fields: noAny suggestions? If nothing else, can you tell me where to edit the SQL code?
Forum: Plugins
In reply to: [WordPress MU Domain Mapping] What's new in 0.5.5?Thanks Ron. I installed the update, and everything seems to be working fine.
Forum: Plugins
In reply to: [BruteProtect] WP admin slow when BruteProtect server unavailableThis morning I’m getting the math captcha on all my sites, but the login pages load fairly quickly – just a little slower than normal. Progress!
Forum: Plugins
In reply to: [BruteProtect] Error BP100: This site is not properly configuredI’m experiencing this problem on one of my sites that uses the a custom login plug-in. I can’t login, so I can’t see which one.
Once I get access again, I can add the suggested code, but it’s disconcerting to lose administrative access to the site.
Earlier responses said the new high-availability hosting should solve the problem, but something’s still not working right.