PHP warnings
-
Hello, i have this error. Can you help me?
Thanks
[15-Jun-2026 09:45:21 UTC] PHP Warning: Undefined array key “form_fields” in /home/avilsaco/public_html/wp-content/plugins/gsheetconnector-for-elementor-forms/includes/gsc-elementor-actions.php on line 260
[15-Jun-2026 09:45:21 UTC] PHP Warning: Undefined array key “field_label” in /home/avilsaco/public_html/wp-content/plugins/gsheetconnector-for-elementor-forms/includes/gsc-elementor-actions.php on line 265
-
Hello @camilo517,
Thank you for sharing the error logs.
To help us investigate this issue further, could you please provide the following information?
- Which version of Elementor are you currently using?
- Which version of GSheetConnector for Elementor Forms is installed on your site?
- Are you using any additional Elementor add-ons or extensions (such as Elementor Pro add-ons, Essential Addons, Premium Addons, etc.)?
Also, please open a support ticket with the above details so our team can review the issue in depth and provide a suitable fix. If possible, include any steps to reproduce the issue and screenshots of your Elementor form configuration.
Once we receive the ticket, our team will investigate and get back to you with a solution.
Thanks
Jina P.Hello
Elementor -> 4.1.3
Elementor pro -> 4.0.4
GSheetConnector for Elementor Forms -> 1.3.1
I’m not sure if it’s due to this bug, but with the plugin active, we’re experiencing MySQL server crashes and significant website slowdowns. When we deactivate your plugin, everything works quickly, including the Elementor editor.
I also note that with PHP version 8.2 or higher, automation no longer works and contacts are no longer inserted. This is due to a deprecated library version. Unfortunately, it has become unusable and absolutely requires a fix.
Please update soon.Looking at the log, errors from the gsheetconnector-for-elementor-forms plugin are preventing it from functioning:
PHP Deprecated: Creation of dynamic property Google\Service\Sheets\CellFormat::$backgroundColor
PHP Deprecated: Creation of dynamic property Google\Service\Sheets\Spreadsheet::$properties
…
Root Cause
The server is running PHP 8.2 or 8.3. In PHP 8.2+, creating “dynamic properties” on classes is deprecated, and in PHP 8.3, it becomes a fatal error that blocks the script from running. Therefore, the lead is never sent to Google Sheets.
The Google API Client library included in the plugin is too old and not compatible with PHP 8.2/8.3.Hello @corsaro ,
Thank you for reporting this issue and for providing the warning details.
We will test this on our development environment using the same plugin version and configuration to reproduce the problem. Once we identify the cause, we will work on a fix and include it in an upcoming plugin update if required.
We appreciate your patience while we investigate this further. We will get back to you with our findings as soon as possible.
Thank you for your support.
Thanks
Jina P.Hello @corsaro, @camilo517,
We have now released a new version of the plugin that includes fixes for the errors and PHP warnings mentioned in this thread, along with improvements related to the library errors.
Please update to the latest version of the plugin and check whether the issue has been resolved on your site.
If you continue to experience any problems after updating, please let us know and share any updated error logs or screenshots. We will be happy to investigate further.
Thanks
Jina P.MySQL usage remains very high when the plugin is active. The main problem is that the Elementor editor either fails to load or loads extremely slowly when the plugin is active. I’m currently testing with PHP 8.5 and the issue persists.
I’ve asked the AI to improve the class-gsc-elementor-integration.php file, and it tells me the following:
To implement the definitive solution in the code you’ve provided, we need to correct the two structural errors that are overwhelming MySQL:
Remove the LIKE “%gscele_form_feeds%” query from the database (Full Table Scan).
Use native WordPress functions (get_post_meta) that make use of the database indexes, reducing MySQL usage to practically zero.
Here is the corrected and optimised code, ready to be substituted. I have modified the two data-submission functions (send_metform_submission_to_google_sheets_feed and send_form_submission_to_google_sheets_feed) so that they perform a direct and clean query by meta_key.
What exactly has changed?
No more $wpdb->get_results with LIKE: Instead of forcing the database engine to search for partial text by scanning through millions of rows, we now use get_post_meta($form_id, “gscele_form_feeds”, true).
Utilising the WordPress index: WordPress natively indexes the meta_key column. By searching directly for the gscele_form_feeds key, the response time drops from hundreds of milliseconds to less than 1 millisecond.
Reduced resource usage in Elementor: As no heavy SQL queries or redundant loops are executed when Elementor saves drafts in the background via AJAX, the editor will once again respond seamlessly.
Could you please check it and update the plugin? Thank you
Hello @camilo517,
Thank you for your detailed feedback and for taking the time to investigate the issue.
We appreciate your suggestions regarding the database query optimization. However, it is difficult for us to properly review, test, and discuss code-level changes within the WordPress.org support forum, especially when they involve modifications to SQL queries, database access patterns, and plugin architecture.
Could you please open a support ticket through our support page so that our development team can review your findings in detail and assist you more efficiently?
Open a ticket here: https://www.gsheetconnector.com/supportWe’re happy to investigate the recommendation and determine whether it can be incorporated into a future update after proper testing and compatibility review.
Thank you again for your valuable feedback and support.
Hello @camilo517,
Thank you for your detailed feedback and for sharing the optimization suggestion.We reviewed the proposed changes carefully. While replacing the current query with
get_post_meta()may work in some cases, our plugin needs to maintain compatibility with both legacy and newer feed structures. A direct switch toget_post_meta()could affect existing configurations and lead to functionality issues for existing users.To address the performance concern safely, we have optimized the feed retrieval process while preserving backward compatibility. These improvements have been included in version 1.3.3-beta1.
Could you please download v1.3.3-beta1 from the Advanced View section, test it on your site, and let us know the results?
If you still experience any issues or have additional suggestions after testing, please feel free to raise a support ticket through our support portal:
We appreciate your feedback and look forward to hearing whether the optimization resolves the issue in your environment.
With version v1.3.3-beta1, the same problem persists: the editor takes an extremely long time to load. Something is still causing it to run slowly. Is it perhaps possible to disable certain calls or code within the editor?
Hello @camilo517,
Thank you for your patience.
We’ve released v1.3.3-beta2, which includes several improvements and fixes, including optimization of feed retrieval queries and database performance enhancements.Could you please download v1.3.3-beta2 from the Advanced View section, test it on your site, and let us know the results? This will help us confirm whether the issue has been resolved in your environment.
We look forward to your feedback.
Thank you!
With version 1.3.3-beta2, the Elementor editor is still running slowly, or in most cases it doesn’t even load. The website is also running slowly in general.
All of this goes away when I deactivate the plugin, and everything works normally.
Perhaps the problem is that the Google API is called when the editor loads, and it should be done asynchronously in the background. It may also be that CSS and JavaScript code is being loaded into the editor when it shouldn’t be.
Hello @camilo517 @corsaro
It looks might be chances to conflict with some another addon plugin, can you share the scree video showing the issue, while filling the form here? so that our team can help you to sort out.
Thanks
Abdullah
You must be logged in to reply to this topic.