inndesign

Seeing the support thread has no support activity and I couldn’t wait for months, therefore fixed it myself. The file that required edit: “wp-customer-reviews-3.php”. Added “//” or commented out lines 967 and 968 which fixed the issue.

If you could kindly fix this so that it will not be overwritten by the next update.

• This reply was modified 8 months, 3 weeks ago by inndesign.

Thanks @benmeredithgmailcom for your responsive and articulate comments. I wish more support people took their task as serious. Appreciate it!

Greetings @benmeredithgmailcom,

I am a dedicated server host and serve hundreds of clients.

My client already has Form Field Manager 3.0.4 installed. Otherwise we could not have as mentioned above “Even though I added a phone number field to the form the import module never reflects this field value in the database.” Therefore the FFM doesn’t work as it should if developed properly. Since the field “Phone Number” is added via Form Field Manager, the import process should map to the field created during the imports, except NO custom field added using FFM is recognized during the mapping process. I have many years of database experience going back to Paradox and dBase. As such, mapping is extremely simple, therefore if the addon plugin worked as it should if properly developed, the field would be resident to import into.

I could correct the PHP in the modules to allow this, but your developers would need to implement the fixes on your end. Otherwise, this is a bug, and any additional workaround as you mentioned is unnecessary if the combined plugins were developed properly.

You did not address another issue: “I can’t change the order of the fields in the donation form address fields. Who puts the country on top?” If the FFM addon is supposed to allow this, it doesn’t work.

Thanks.

Of course, it would be senseless to open a ticket if ANYTHING was not up-to-date and current. Avada 7.11.5 and The Events Calendar 6.3.3. PHP 8.1.27. Everything is 100% current and the website runs lean, only required plugins.

There are no “steps” to create the problem. Simply activate Events Calendar and the error log starts filling up. Disable it, the error log remains empty. The below posts over 3 or 4 seconds until the error log file bloats to 1.5Gig in about two weeks.

[20-Feb-2024 23:02:36 UTC] WordPress database error Unknown column ‘wp_tec_occurrences.start_date_utc’ in ‘field list’ for query
SELECT wp_posts.ID, CAST( wp_tec_occurrences.start_date_utc AS DATETIME ) AS event_date_utc, CAST( wp_tec_occurrences.duration AS DECIMAL ) AS event_duration
FROM wp_posts LEFT JOIN wp_term_relationships ON (wp_posts.ID = wp_term_relationships.object_id)
WHERE 1=1 AND (
wp_term_relationships.term_taxonomy_id IN (314)
) AND wp_posts.post_type IN (‘post’, ‘page’, ‘attachment’, ‘donor’, ‘funds’, ‘donation’, ‘tribe_events’, ‘avada_portfolio’, ‘avada_faq’) AND ((wp_posts.post_status = ‘publish’)) AND ((
TIMESTAMPDIFF ( SECOND, wp_tec_occurrences.start_date_utc, ‘2021-10-30 03:59:59’ ) >= 1
AND
TIMESTAMPDIFF ( SECOND, ‘2021-10-29 04:00:00’, wp_tec_occurrences.end_date_utc ) >= 1
))
GROUP BY wp_tec_occurrences.occurrence_id
ORDER BY event_date_utc ASC, event_duration ASC, wp_posts.post_date ASC
made by require(‘wp-blog-header.php’), require_once(‘wp-includes/template-loader.php’), include(‘/themes/Avada/tribe/events/v2/default-template.php’), Tribe\Events\Views\V2\Template_Bootstrap->get_view_html, Tribe\Events\Views\V2\View->get_html, Tribe\Events\Views\V2\Views\Day_View->setup_template_vars, Tribe\Events\Views\V2\View->setup_template_vars, Tribe__Repository->all, WP_Query->get_posts

No, that is not it…

System Information
Views V2 Status: Enabled
Custom Tables Migration Status: Completed
Custom Tables Health Check: Good!

No database restorations have been done.

I also wanted to point out that the logs are not recording what is being blocked as it once did. The below is all I see in the logs since November 11th.

plugin’s rules:

2023-11-14 17:45:03 :: Visitors IP Address: 107.172.229.188
The following [TEXT] is blocked by the plugin’s rules:

2023-11-14 22:07:44 :: Visitors IP Address: 202.47.55.114
The following [TEXT] is blocked by the plugin’s rules:

2023-11-15 10:36:36 :: Visitors IP Address: 194.36.98.211
The following [TEXT] is blocked by the plugin’s rules:

2023-11-15 12:35:49 :: Visitors IP Address: 89.187.180.19
The following [TEXT] is blocked by the plugin’s rules:

2023-11-15 17:26:18 :: Visitors IP Address: 23.106.20.19
The following [TEXT] is blocked by the plugin’s rules:

2023-11-16 03:43:19 :: Visitors IP Address: 204.44.117.21
The following [TEXT] is blocked by the plugin’s rules:

2023-11-16 16:01:44 :: Visitors IP Address: 151.237.177.44
The following [TEXT] is blocked by the plugin’s rules:

2023-11-17 04:04:52 :: Visitors IP Address: 172.241.243.177
The following [TEXT] is blocked by the plugin’s rules:

2023-11-17 07:43:01 :: Visitors IP Address: 173.44.213.121
The following [TEXT] is blocked by the plugin’s rules:

2023-11-17 11:13:53 :: Visitors IP Address: 45.38.60.110
The following [TEXT] is blocked by the plugin’s rules:

2023-11-17 16:44:15 :: Visitors IP Address: 104.168.75.138
The following [TEXT] is blocked by the plugin’s rules:

2023-11-18 07:07:05 :: Visitors IP Address: 23.106.16.99
The following [TEXT] is blocked by the plugin’s rules:

2023-11-18 07:20:19 :: Visitors IP Address: 23.230.11.227
The following [TEXT] is blocked by the plugin’s rules:

2023-11-18 08:00:21 :: Visitors IP Address: 52.128.14.202
The following [TEXT] is blocked by the plugin’s rules:

2023-11-18 17:55:16 :: Visitors IP Address: 194.36.96.217
The following [TEXT] is blocked by the plugin’s rules:

2023-11-18 20:21:07 :: Visitors IP Address: 196.245.220.36
The following [TEXT] is blocked by the plugin’s rules:

2023-11-19 01:08:19 :: Visitors IP Address: 172.241.243.39
The following [TEXT] is blocked by the plugin’s rules:

2023-11-19 01:27:29 :: Visitors IP Address: 23.80.143.64
The following [TEXT] is blocked by the plugin’s rules:

2023-11-19 01:27:29 :: Visitors IP Address: 23.80.143.64
The following [TEXT] is blocked by the plugin’s rules:

2023-11-19 03:18:41 :: Visitors IP Address: 207.170.176.12
The following [TEXT] is blocked by the plugin’s rules:

2023-11-19 08:14:42 :: Visitors IP Address: 86.111.229.56
The following [TEXT] is blocked by the plugin’s rules:

2023-11-19 18:53:01 :: Visitors IP Address: 104.129.58.211
The following [TEXT] is blocked by the plugin’s rules:

2023-11-19 19:02:13 :: Visitors IP Address: 173.213.84.58
The following [TEXT] is blocked by the plugin’s rules:

2023-11-20 03:48:55 :: Visitors IP Address: 23.106.19.110
The following [TEXT] is blocked by the plugin’s rules:

2023-11-20 09:03:12 :: Visitors IP Address: 191.101.217.68
The following [TEXT] is blocked by the plugin’s rules:

2023-11-20 13:53:25 :: Visitors IP Address: 155.94.240.219
The following [TEXT] is blocked by the plugin’s rules:

2023-11-20 15:19:29 :: Visitors IP Address: 172.241.152.194
The following [TEXT] is blocked by the plugin’s rules:

2023-11-20 15:27:38 :: Visitors IP Address: 130.185.156.74
The following [TEXT] is blocked by the plugin’s rules:

2023-11-20 15:37:25 :: Visitors IP Address: 5.157.56.128
The following [TEXT] is blocked by the plugin’s rules:

2023-11-20 20:27:15 :: Visitors IP Address: 196.240.51.123
The following [TEXT] is blocked by the plugin’s rules:

2023-11-20 21:47:44 :: Visitors IP Address: 146.70.181.246
The following [TEXT] is blocked by the plugin’s rules:

2023-11-20 22:27:09 :: Visitors IP Address: 23.83.88.138
The following [TEXT] is blocked by the plugin’s rules:

2023-11-21 05:53:25 :: Visitors IP Address: 45.39.116.52
The following [TEXT] is blocked by the plugin’s rules:

2023-11-21 06:07:31 :: Visitors IP Address: 23.82.106.46
The following [TEXT] is blocked by the plugin’s rules:

2023-11-21 07:36:44 :: Visitors IP Address: 46.35.252.130
The following [TEXT] is blocked by the plugin’s rules:

2023-11-21 09:39:03 :: Visitors IP Address: 139.171.25.208
The following [TEXT] is blocked by the plugin’s rules:

2023-11-21 12:34:18 :: Visitors IP Address: 38.154.99.168
The following [TEXT] is blocked by the plugin’s rules:

2023-11-21 15:36:04 :: Visitors IP Address: 23.82.40.113
The following [TEXT] is blocked by the plugin’s rules:

2023-11-22 02:20:54 :: Visitors IP Address: 38.153.74.240
The following [TEXT] is blocked by the plugin’s rules:

2023-11-22 10:11:35 :: Visitors IP Address: 172.241.168.227
The following [TEXT] is blocked by the plugin’s rules:

2023-11-22 15:53:09 :: Visitors IP Address: 52.128.15.14
The following [TEXT] is blocked by the plugin’s rules:

2023-11-22 16:17:43 :: Visitors IP Address: 149.34.252.58
The following [TEXT] is blocked by the plugin’s rules:

2023-11-22 22:28:15 :: Visitors IP Address: 64.120.34.220
The following [TEXT] is blocked by the plugin’s rules:

2023-11-22 23:09:44 :: Visitors IP Address: 103.179.44.140
The following [TEXT] is blocked by the plugin’s rules:

2023-11-23 04:58:37 :: Visitors IP Address: 107.174.59.54
The following [TEXT] is blocked by the plugin’s rules:

2023-11-23 10:00:08 :: Visitors IP Address: 154.12.230.31
The following [TEXT] is blocked by the plugin’s rules:

2023-11-23 10:20:27 :: Visitors IP Address: 23.83.88.247
The following [TEXT] is blocked by the plugin’s rules:

And on it goes through the current date.

Hello, @nysl, yes, I already know all those points and how Contact Form 7 works. The question still stands that wasn’t answered specifically. I understand the plugin detects spam content through text matches, but if spam is detected, are you saying that this plugin does not fully block the spammed form from completing its delivery? Thanks.

Same here, I am still getting the same error and developers don’t seem to care to fix it. Plugin version: 3.5.2, PHP 8.0.30, MySQLi 8.0.34, WordPress 6.3.1

Warning: Undefined array key “login_enable_language_switcher” in /home/domain/public_html/wp-content/plugins/admin-custom-login/login-form-screen.php on line 53

Warning: Uninitialized string offset 0 in /home/domain/public_html/wp-content/plugins/admin-custom-login/login-form-screen.php on line 67

Greetings @abzlevelup and @d0153,

I submitted a ticket as “other” from the Help link provided.

My updates are as follows in case the help page submission fails.

The recently updated version of 6.2.1 still crashes our site completely when activated with Avada version 7.11.2.

When I deactivate Avada Builder 3.11.2 (version with Avada 7.11.2), the site restores. Therein lies part of the problem, Avada builder’s dedication to Event Calendar is not compatible since 6.2.0. I reverted back to The Events Calendar 6.1.4 to restore the plugin and website. I also had to revert the Avada theme back to version 7.8.2 to regain a reliable website.

My developer who is a veteran at coding says all his clients experience constant issues with The Events Calendar. He looked over my conflict and confirmed it was an issue with Events Calendar 6.2.0, 6.2.0.1, and 6.2.1 against Avada version 7.11.2. He could not ascertain the cause.

Thanks.

‘[30-Aug-2023 20:39:22 UTC] WordPress database error Unknown column ‘wp_tec_occurrences.start_date_utc’ in ‘field list’ for query
SELECT SQL_CALC_FOUND_ROWS wp_posts.ID, CAST( wp_tec_occurrences.start_date_utc AS DATETIME ) AS event_date_utc, CAST( wp_tec_occurrences.duration AS DECIMAL ) AS event_duration
FROM wp_posts LEFT JOIN wp_term_relationships ON (wp_posts.ID = wp_term_relationships.object_id) INNER JOIN wp_postmeta ON ( wp_posts.ID = wp_postmeta.post_id )
WHERE 1=1 AND (
wp_term_relationships.term_taxonomy_id IN (310)
) AND (
( wp_postmeta.meta_key = ‘_EventEndDateUTC’ AND CAST(wp_postmeta.meta_value AS DATETIME) < ‘2023-07-01 04:00:00’ ) ) AND wp_posts.post_type IN (‘post’, ‘page’, ‘attachment’, ‘donor’, ‘funds’, ‘donation’, ‘tribe_events’, ‘avada_portfolio’, ‘avada_faq’) AND ((wp_posts.post_status = ‘publish’)) GROUP BY wp_tec_occurrences.occurrence_id ORDER BY event_date_utc DESC, event_duration DESC, wp_posts.post_date DESC LIMIT 0, 30 made by require(‘wp-blog-header.php’), require_once(‘wp-includes/template-loader.php’), do_action(‘template_redirect’), WP_Hook->do_action, WP_Hook->apply_filters, Tribe__Events__iCal->do_ical_template, apply_filters(‘tribe_ical_template_event_ids’), WP_Hook->apply_filters, Tribe\Events\Views\V2\Hooks->inject_ical_event_ids, Tribe\Events\Views\V2\iCalendar\Request->get_event_ids, Tribe\Events\Views\V2\View->get_ical_ids, Tribe__Repository->get_ids, WP_Query->get_posts
[30-Aug-2023 20:40:38 UTC] WordPress database error Unknown column ‘wp_tec_occurrences.start_date_utc’ in ‘field list’ for query
SELECT SQL_CALC_FOUND_ROWS wp_posts.ID, CAST( wp_tec_occurrences.start_date_utc AS DATETIME ) AS event_date_utc, CAST( wp_tec_occurrences.duration AS DECIMAL ) AS event_duration
FROM wp_posts LEFT JOIN wp_term_relationships ON (wp_posts.ID = wp_term_relationships.object_id) INNER JOIN wp_postmeta ON ( wp_posts.ID = wp_postmeta.post_id )
WHERE 1=1 AND (
wp_term_relationships.term_taxonomy_id IN (297)
) AND (
( wp_postmeta.meta_key = ‘_EventEndDateUTC’ AND CAST(wp_postmeta.meta_value AS DATETIME) > ‘2023-08-31 04:00:00’ )
) AND wp_posts.post_type IN (‘post’, ‘page’, ‘attachment’, ‘donor’, ‘funds’, ‘donation’, ‘tribe_events’, ‘avada_portfolio’, ‘avada_faq’) AND ((wp_posts.post_status = ‘publish’))
GROUP BY wp_tec_occurrences.occurrence_id
ORDER BY event_date_utc ASC, event_duration ASC, wp_posts.post_date ASC
LIMIT 0, 30
made by require(‘wp-blog-header.php’), require_once(‘wp-includes/template-loader.php’), do_action(‘template_redirect’), WP_Hook->do_action, WP_Hook->apply_filters, Tribe__Events__iCal->do_ical_template, apply_filters(‘tribe_ical_template_event_ids’), WP_Hook->apply_filters, Tribe\Events\Views\V2\Hooks->inject_ical_event_ids, Tribe\Events\Views\V2\iCalendar\Request->get_event_ids, Tribe\Events\Views\V2\View->get_ical_ids, Tribe__Repository->get_ids, WP_Query->get_posts
[30-Aug-2023 20:47:00 UTC] Cron reschedule event error for hook: action_scheduler_run_queue, Error code: invalid_schedule, Error message: Event schedule does not exist., Data: {“schedule”:”every_minute”,”args”:[“WP Cron”],”interval”:60}’

Thanks!

The first thing I looked at was mime.type on our WHM dedicated server and “.log” is included by default:

text/plain txt text conf def list log in

I would think there should be a truncate function that allows a user to set a range of grandfathered logged form entries instead of storing all forms intercepted forever. Like retaining only the last 30 days, 60, or 90 days.

Then a text file would be ideal.

No, that isn’t the answer at all. Of course the write permissions work. The file wrote fine, but a person cannot open it up in a browser. It will always result in a 404 error.

.log files cannot be opened in a default browser. It will 404 error by default. The log file must be saved as .txt to open. Please rename your logs generated as a .txt format so people can actually open them in a browser without downloading them. The saved format is user unfriendly as it is currently saved.

Thanks.

Added to the above, when clicking “To download and view the log file click here”, even though the Log failed message is set to “YES” the link to https://domain.com/wp-content/spcf_spam_block.log results in a 404-page error. Despite many efforts to populate the log with test spam, the log does not exist.

@weblizar There has been no follow-up despite proof of error?

Thanks @takayukister,

The culprit turned out to be Simple Redirection for Contact Form 7:
https://www.ads-software.com/plugins/simple-redirection-for-contact-form-7/

I found a substitute that appears maintained, Redirection for Contact Form 7 https://www.ads-software.com/plugins/wpcf7-redirect/

Thanks very much!