Title: sinapars's Replies | WordPress.org --- # sinapars [ ](https://wordpress.org/support/users/sinapars/) * [Profile](https://wordpress.org/support/users/sinapars/) * [Topics Started](https://wordpress.org/support/users/sinapars/topics/) * [Replies Created](https://wordpress.org/support/users/sinapars/replies/) * [Reviews Written](https://wordpress.org/support/users/sinapars/reviews/) * [Topics Replied To](https://wordpress.org/support/users/sinapars/replied-to/) * [Engagements](https://wordpress.org/support/users/sinapars/engagements/) * [Favorites](https://wordpress.org/support/users/sinapars/favorites/) Search replies: ## Forum Replies Created Viewing 15 replies - 1 through 15 (of 83 total) 1 [2](https://wordpress.org/support/users/sinapars/replies/page/2/?output_format=md) [3](https://wordpress.org/support/users/sinapars/replies/page/3/?output_format=md) [4](https://wordpress.org/support/users/sinapars/replies/page/4/?output_format=md) [5](https://wordpress.org/support/users/sinapars/replies/page/5/?output_format=md) [6](https://wordpress.org/support/users/sinapars/replies/page/6/?output_format=md) [→](https://wordpress.org/support/users/sinapars/replies/page/2/?output_format=md) * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Web Stories] Feature Suggestions](https://wordpress.org/support/topic/feature-suggestions-38/) * Thread Starter [sinapars](https://wordpress.org/support/users/sinapars/) * (@sinapars) * [1 year ago](https://wordpress.org/support/topic/feature-suggestions-38/#post-18572872) * Hi [@swissspidy](https://wordpress.org/support/users/swissspidy/) , Thanks for your response and for considering my suggestions.If extending the Web Stories block with these features isn’t currently on your roadmap, could you please share how you plan to address the usability issues related to tracking seen and unseen stories?When there are many stories, it’s really hard for users to know which ones they have already watched and which they haven’t, which affects the overall experience.Looking forward to your insights. Thanks again for your great work! * Best Regard * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[افزونه پرداخت امن زرین‌پال برای ووکامرس (ZarinPal for WooCommerce)] مشکلات بزرگ و دردسر ساز](https://wordpress.org/support/topic/%d9%85%d8%b4%da%a9%d9%84%d8%a7%d8%aa-%d8%a8%d8%b2%d8%b1%da%af-%d9%88-%d8%af%d8%b1%d8%af%d8%b3%d8%b1-%d8%b3%d8%a7%d8%b2/) * Thread Starter [sinapars](https://wordpress.org/support/users/sinapars/) * (@sinapars) * [1 year ago](https://wordpress.org/support/topic/%d9%85%d8%b4%da%a9%d9%84%d8%a7%d8%aa-%d8%a8%d8%b2%d8%b1%da%af-%d9%88-%d8%af%d8%b1%d8%af%d8%b3%d8%b1-%d8%b3%d8%a7%d8%b2/#post-18572866) * آرمین جان خیلی ممنونم از پاسخت، تا حدی امیدوارم شدم که شاید این مشکلات توسط شما حل بشه چون این موارد سمت افزونه باید هندل بشه من با پشتیبانی مفصل صحبت کردم و تیکت زدم و به هیچ نتیجه ای نرسیدم ! و نهایت به من اعلام میکنن باید خودتون توسعه بدین چرا من باید خودم توسعه بدم ؟ یا هزینه بکنم از افزونه های غیر رسمی استفاده کنم؟ اونم زرین پالی که جز بزرگترین و اولین ها بوده… بگذریم …به هر حال خواستم بگم من با پشتیبانی پیش رفتم و به نتیجه ای نرسیدم و مدتی هست دارم از افزونه غیر رسمی استفاده میکنم و تقریبا تمام مشکلاتم برطرف شده و میزان تراکنش های مشکل دار به شکل قابل توجهی کاهش پیدا کرده و وقتی تراکنشی هم به مشکل میخوره چون تو نوت دخیره میشه ما دقیقا متوجه میشیم چرا کاربر نتونسته پرداخت کنه .. * به نظرم تمام خطاها باید توی نوت لاگ بشه نمیدونم چرا میفرمایید فیدبکی خوبی نگرفتید؟ اینجوری هم ما میتونیم عیب یابی دقیق کنیم هم اگه بخوایم با پشتیبانی زرین ارتباط بگیریم میتونیم دقیقا ببینیم مشکل چیه و بهشون اعلام کنیم در آخرین مورد، پشتیبانی به من اعلام کرده توسط یه برنامه نویس خطاهارو لاگ کنید و به ما بگید چه خطایی میگیرید!! برای همین میگم مهم تر از لاگ شدن در دیباگ، ذخیره تمام رویدادها تو نوت سفارش هست که واسه همیشه هم تو سوابق اون سفارش باقی بمونه * در مورد مشکل وریفای پشتیبانی این راه کار رو به ما دادن و ما گزینه اول رو فعال کردیم اما مشکل حل نشد و وقتی با افزونه غیر رسمی نوت هایی که برای این موارد ثبت شده رو بررسی کردیم این خطا رو دقیقا سه بار و به فاصله دو دقیقه گرفتیم در صورتی که تراکنش با موفقیت انجام شده بود و فقط تایید نشده بود * `Verify Response: Array( [data] => Array ()[errors] => Array ([message] => Session is not this merchant_id session.[code] => -53[validations] => Array ())) * برای حل مشکل وریفای سفارشات وریفای نشده اون پیشنهادی که در پست اول دادم میتونه کمک کنه مثلا یه جابی تعریف بشه که هر دو دقیقه یه بار اجرا بشه و دو تا شرط برای بررسی داشته باشه سفارشات **وریفای نشده ای** که وضعیت اونها روی پ**ندینگ پیمنت** یا **کنسل شده** هست رو بگیره و در صورتی که از سمت زرین **وریفای** شده بود رو خودکار تایید کنه و وضعیت اونها رو به در حال پردازش تغییر بدهفقط این جاب باید در بازه کوتاه اجرا بشه مثلا هر دو دقیقه یه بار یا کمتر چون ما ممکنه برای هر وضعیت سفارش پیامک ارسال کنیم و اگر طولانی باشه تجربه خوبی نداره و کاربر مطمئن نمیشه که سفارشش دریافت شده و دلیل بعدش اینه که تو تنظیمات ووکامرس قابلیتی وجود داره که شما میتونید زمانی رو تعیین کنید (مثلا سی دقیقه) تا اگر در این بازه سفارش تایید نشد خودکار لغو بشه * این پیشنهاد من برای حل این مشکل بزرگ بود قطعا شما از نظر فنی آگاه تر هستید و ممکنه راه بهتری داشته باشید نیاز به هر دیتایی داشتید خوشحال میشم بتونم کمک کنم - This reply was modified 1 year ago by [sinapars](https://wordpress.org/support/users/sinapars/). * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Wordfence Security - Firewall, Malware Scan, and Login Security] Suggestion for WP_HTTP_Proxy Support in Wordfence Plugin](https://wordpress.org/support/topic/suggestion-for-wp_http_proxy-support-in-wordfence-plugin/) * Thread Starter [sinapars](https://wordpress.org/support/users/sinapars/) * (@sinapars) * [1 year, 1 month ago](https://wordpress.org/support/topic/suggestion-for-wp_http_proxy-support-in-wordfence-plugin/#post-18544196) * Hi there, [@judehall](https://wordpress.org/support/users/judehall/) Just wanted to say **a huge thank you** for your post – it completely solved my issue!I had been struggling with the same problem, and your suggestion to directly modify the `wfWAFHTTPTransportCurl` class with: * `curl_setopt($ch, CURLOPT_PROXY, WP_PROXY_HOST); curl_setopt($ch, CURLOPT_PROXYPORT, WP_PROXY_PORT); * worked perfectly for my setup as well. I really appreciate you sharing your workaround 🙌 * As an additional tip: if you’ve already defined your proxy settings in `wp-config. php`, you can make the code a bit more dynamic by using the constants like this: * `curl_setopt($ch, CURLOPT_PROXY, WP_PROXY_HOST); curl_setopt($ch, CURLOPT_PROXYPORT, WP_PROXY_PORT); * And just for reference, these are the lines you’d add to your `wp-config.php`: * `define('WP_PROXY_HOST', '192.168.84.101'); define('WP_PROXY_PORT', '8080'); * [@wfpeter](https://wordpress.org/support/users/wfpeter/) There’s already a `@ todo Proxy settings` comment in the class, so I assume you’re aware of this, but I hope this can be properly implemented in a future release so we don’t have to modify core plugin files after every update 🙏Thanks again! - This reply was modified 1 year, 1 month ago by [sinapars](https://wordpress.org/support/users/sinapars/). * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Formidable Forms - WordPress Form Builder for Contact Forms, Calculators, Quizzes & More] Issue with “Created By” in CSV Export (Version 6.19)](https://wordpress.org/support/topic/issue-with-created-by-in-csv-export-version-6-19/) * Thread Starter [sinapars](https://wordpress.org/support/users/sinapars/) * (@sinapars) * [1 year, 4 months ago](https://wordpress.org/support/topic/issue-with-created-by-in-csv-export-version-6-19/#post-18393787) * Thanks for your response! * You’re right—I thought this might be a general issue that needed a fix for everyone. I’ll go ahead and create a ticket as suggested. * Just for my understanding, could you please clarify my second question? What exactly does the “Created By” column store and display in the export file—the user’s email or username? I’d love to understand the logic behind this change. * Thanks again! * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Formidable Forms - WordPress Form Builder for Contact Forms, Calculators, Quizzes & More] frm_csv_columns Filter Not Removing Comment Columns in CSV Export](https://wordpress.org/support/topic/frm_csv_columns-filter-not-removing-comment-columns-in-csv-export/) * Thread Starter [sinapars](https://wordpress.org/support/users/sinapars/) * (@sinapars) * [1 year, 4 months ago](https://wordpress.org/support/topic/frm_csv_columns-filter-not-removing-comment-columns-in-csv-export/#post-18393777) * Hi again [@altoin](https://wordpress.org/support/users/altoin/), Thank you for your response! * I understand that some hooks are specific to the Pro version, but I’m using the free version, and the frm_csv_columns filter is working fine on it. The only issue is that the comment columns are not being removed. * Would you be able to provide any insights on why this might be happening? * Best Regards * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Wordfence Security - Firewall, Malware Scan, and Login Security] Suggestion for WP_HTTP_Proxy Support in Wordfence Plugin](https://wordpress.org/support/topic/suggestion-for-wp_http_proxy-support-in-wordfence-plugin/) * Thread Starter [sinapars](https://wordpress.org/support/users/sinapars/) * (@sinapars) * [1 year, 5 months ago](https://wordpress.org/support/topic/suggestion-for-wp_http_proxy-support-in-wordfence-plugin/#post-18317930) * Hi Peter, * I hope you’re doing well. I wanted to follow up on the proxy support request I sent last month. I haven’t seen any updates on this yet, so I was wondering if there are any plans to include this feature in future versions of Wordfence. * I’d really appreciate any updates you can share. Thanks again for your time and support! * Best regards * [@wfpeter](https://wordpress.org/support/users/wfpeter/) * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Wordfence Security - Firewall, Malware Scan, and Login Security] Suggestion for WP_HTTP_Proxy Support in Wordfence Plugin](https://wordpress.org/support/topic/suggestion-for-wp_http_proxy-support-in-wordfence-plugin/) * Thread Starter [sinapars](https://wordpress.org/support/users/sinapars/) * (@sinapars) * [1 year, 7 months ago](https://wordpress.org/support/topic/suggestion-for-wp_http_proxy-support-in-wordfence-plugin/#post-18248557) * Hi [@wfpeter](https://wordpress.org/support/users/wfpeter/) * I’ve just sent the **diagnostic **information to the email address you provided. The email subject is “**Suggestion for WP_HTTP_Proxy Support in Wordfence Plugin**“. I’ve **attached **the requested file and also included an additional download link for your convenience, in case the attachment doesn’t work. * This feature is quite important for users like me who rely on **WP HTTP Proxy** configurations due to restricted direct internet access. I’ve been unable to ** manually update the WAF rules** for over a year, which has been a significant challenge. * If there’s any additional information or steps you need from me to assist in adding this feature, please let me know. I’m happy to provide further details to help make this possible. * Thank you once again for your time and for considering this request. I hope with your help, this feature can be added to benefit others in similar environments as well. * Regards * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Formidable Forms - WordPress Form Builder for Contact Forms, Calculators, Quizzes & More] Request Hard Fix for UTF-8 Encoding Issue in CSV Exports-Formidable Forms](https://wordpress.org/support/topic/fixed-request-hard-fix-for-utf-8-encoding-issue-in-csv-exports-formidable-forms/) * Thread Starter [sinapars](https://wordpress.org/support/users/sinapars/) * (@sinapars) * [1 year, 7 months ago](https://wordpress.org/support/topic/fixed-request-hard-fix-for-utf-8-encoding-issue-in-csv-exports-formidable-forms/#post-18235336) * Hi Nathanael, * Thank you so much for the update! It’s great to hear that the lead developer is planning to add this as an option in the plugin in the near future. I really appreciate the effort your team is putting into improving this feature, and I’ll definitely keep an eye on the changelog for the future release. * That said, I wanted to share a small concern regarding the implementation of this update. I hope this new feature will be introduced **as an optional setting** rather than a **default**, **mandatory **one. The reason for this is that while it’s incredibly useful for smaller datasets, it can lead to significant issues( like freezing or crashing) when working larger datasets after exporting, as we’ve discussed before. * Allowing users to enable or disable or check or uncheck this option when exporting based on their specific needs would provide maximum flexibility and avoid unintended complications for those working with large data files. * Thank you again for your support [@njones35](https://wordpress.org/support/users/njones35/) * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Formidable Forms - WordPress Form Builder for Contact Forms, Calculators, Quizzes & More] Request Hard Fix for UTF-8 Encoding Issue in CSV Exports-Formidable Forms](https://wordpress.org/support/topic/fixed-request-hard-fix-for-utf-8-encoding-issue-in-csv-exports-formidable-forms/) * Thread Starter [sinapars](https://wordpress.org/support/users/sinapars/) * (@sinapars) * [1 year, 7 months ago](https://wordpress.org/support/topic/fixed-request-hard-fix-for-utf-8-encoding-issue-in-csv-exports-formidable-forms/#post-18234813) * Thank you so much for your response and for sharing the developer’s feedback along with the documentation link. I’m genuinely happy to learn that this action was already anticipated and documented. I appreciate you bringing it to my attention— it’s incredibly helpful! * With this action available, **there’s no need for a hard fix by users or your dev team, especially** considering the potential freezing issue with larger files. That said before, the snippet can still be extremely effective for **smaller files**, and it’s great to have this option for those cases. * Unfortunately, I tested the provided snippet as well, and the issue with the file becoming unresponsive (or crashing) persists when working with **larger datasets**. This makes it difficult to work with the exported file in tools like Excel or Numbers or Google sheets. * Thank you again for all your support and for helping improve the experience with Formidable Forms. If your team happens to explore a more robust solution in the future, I’d be happy to assist with testing. * [@njones35](https://wordpress.org/support/users/njones35/) * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Formidable Forms - WordPress Form Builder for Contact Forms, Calculators, Quizzes & More] Request Hard Fix for UTF-8 Encoding Issue in CSV Exports-Formidable Forms](https://wordpress.org/support/topic/fixed-request-hard-fix-for-utf-8-encoding-issue-in-csv-exports-formidable-forms/) * Thread Starter [sinapars](https://wordpress.org/support/users/sinapars/) * (@sinapars) * [1 year, 7 months ago](https://wordpress.org/support/topic/fixed-request-hard-fix-for-utf-8-encoding-issue-in-csv-exports-formidable-forms/#post-18234012) * Hi [@njones35](https://wordpress.org/support/users/njones35/) , * Thank you so much for your response and for forwarding my suggestion to the development team. I really appreciate the time and effort your team puts into improving Formidable Forms. * After further testing, I discovered that the issue with freezing isn’t limited to Excel. It also occurs in other software like Numbers and Google Sheets, especially when working with large datasets. Essentially, adding the BOM code makes it almost impossible to work with heavy data files. * Given that many users rely on Windows and Excel, I believe it would be better not to implement this change until a more robust solution is found, as it could negatively impact a significant portion of your user base. * **For further clarification:Your plugin generates CSV files with proper and correct UTF-8 encoding. For example, when opening the file in Notepad, all characters display correctly. However, if the file is opened directly in Excel, the characters appear distorted. To resolve this, users need to: * Go to the **Data tab** in Excel. 1. Select **From Text/CSV**.2. **Choose **the downloaded CSV file.3. Select **file origin** on **Unicode (UTF-8)** and load Button4. This ensures everything displays correctly in Excel. * The code I shared earlier bypasses these steps and resolves the issue directly,** but unfortunately, it introduces a more serious problem (software freezing), which can be incredibly frustrating.** * For now, I believe it’s best not to make this change until a better solution is identified. If your team comes up with an alternative and needs it tested before implementing it as a hard fix, please feel free to reach out—I’d be happy to assist with testing. * Thank you again for your support! * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Formidable Forms - WordPress Form Builder for Contact Forms, Calculators, Quizzes & More] issue with huge Form entries Export in formidable form Plugin](https://wordpress.org/support/topic/issue-with-huge-form-entries-export-in-formidable-form-plugin-2/) * Thread Starter [sinapars](https://wordpress.org/support/users/sinapars/) * (@sinapars) * [1 year, 7 months ago](https://wordpress.org/support/topic/issue-with-huge-form-entries-export-in-formidable-form-plugin-2/#post-18232034) * Hi [@jonathanenlared](https://wordpress.org/support/users/jonathanenlared/) * Thank you for your response and for the efforts your team is putting into improving the import/export feature. I really appreciate it. * However, I believe there might have been some **misunderstanding **regarding the solution. The issue I encountered **wasn’t resolved** with the **batch size adjustment**. The solution that worked for me was **increasing the timeout duration in the main web server configuration**, which solved the issue. * In the meantime, I also **found another solution** by adding this line to the** FrmCSVExportHelper.php** file in the function **public static function generate_csv( $atts )** at **line 104**: * `set_time_limit(0);` * With this code alone, there was **no need** for the **batch size adjustment** or changing the **timeout **in the main **web server configuration**, and it ** solved **the issue. Additionally, it reduced the time required to prepare the file by around one minute. * Thanks again for your support! Please let me know if you need any further details. * BR Sina * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Formidable Forms - WordPress Form Builder for Contact Forms, Calculators, Quizzes & More] Request Hard Fix for UTF-8 Encoding Issue in CSV Exports-Formidable Forms](https://wordpress.org/support/topic/fixed-request-hard-fix-for-utf-8-encoding-issue-in-csv-exports-formidable-forms/) * Thread Starter [sinapars](https://wordpress.org/support/users/sinapars/) * (@sinapars) * [1 year, 7 months ago](https://wordpress.org/support/topic/fixed-request-hard-fix-for-utf-8-encoding-issue-in-csv-exports-formidable-forms/#post-18231871) * **Update:** * I recently discovered an issue with the provided fix when working with **large CSV** files in **Excel **specifically. When the file is downloaded and opened for editing in **Excel**, even small changes cause the software to freeze and stop responding until it’s restarted. * Interestingly, the file size itself **doesn’t change**, and this issue only occurs when working with Excel. Other software (like Numbers or Google Sheets) doesn’t seem to have this problem. * It seems this happens because the BOM is applied to all characters in the file. * I’m currently searching for an alternative solution to address this problem, but I’d be happy to hear any ideas or suggestions your developers might have to resolve it more efficiently. * Thank you! * Forum: [Requests and Feedback](https://wordpress.org/support/forum/requests-and-feedback/) In reply to: [Request to Remove Post Moderation Restriction](https://wordpress.org/support/topic/request-to-remove-post-moderation-restriction/) * Thread Starter [sinapars](https://wordpress.org/support/users/sinapars/) * (@sinapars) * [1 year, 7 months ago](https://wordpress.org/support/topic/request-to-remove-post-moderation-restriction/#post-18229609) * Hi [@moderator](https://wordpress.org/support/users/moderator/) * I sent an email on **Friday, January 3rd**, as per your recommendation, but unfortunately, I haven’t received a response yet, and the post moderation restriction is still in place. * I would appreciate it if you could kindly follow up on this matter or let me know if there’s anything else I should do. Thank you for your time and assistance! * Best regards, Sina * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Formidable Forms - WordPress Form Builder for Contact Forms, Calculators, Quizzes & More] issue with huge Form entries Export in formidable form Plugin](https://wordpress.org/support/topic/issue-with-huge-form-entries-export-in-formidable-form-plugin-2/) * Thread Starter [sinapars](https://wordpress.org/support/users/sinapars/) * (@sinapars) * [1 year, 7 months ago](https://wordpress.org/support/topic/issue-with-huge-form-entries-export-in-formidable-form-plugin-2/#post-18229603) * Hi [@jonathanenlared](https://wordpress.org/support/users/jonathanenlared/) * Thank you so much for looking into this issue and providing the pre-release version. I tested it with different batch size values, such as 50, 100, 150, 200, and 300, but unfortunately, the problem still persists. To be honest, even if it had worked, I’m not sure how practical and reliable this solution would be in the long run, for a few reasons: 1. **Server Variability:** The resources available on each server differ significantly. As a result, the batch size values that should be selected will vary based on each user’s infrastructure and server conditions. 2. **Dynamic Data Growth:** The amount of data in each form changes over time. As users, we would need to constantly experiment with different batch sizes to achieve optimal performance. This trial-and-error approach isn’t feasible. * For now, I found a temporary solution to resolve the issue: I increased the server timeout in the main web server configuration file located at:**/etc/apache2/httpd. confby adding these two parameters: * `Timeout 600 ProxyTimeout 600 * However, this is **not a recommended solution** for several reasons: - Only a small percentage of users have access to dedicated servers and can modify their web server configuration. - From a security perspective, this is risky as it increases the likelihood of running heavy or malicious scripts. * **Suggestions:** To address this issue more effectively, here are a few suggestions: 1. **Database and Export Optimization:** Optimizing the database structure and the way data is generated and exported. I replicated my form (with 30,000 records) in a competitor’s plugin, and to my surprise, the export process was completed on a **shared server with limited resources** (128MB RAM) in **under 20 seconds.** 2. **Custom Date Range for Export Filters:** Adding the ability to filter export data based on a custom date range (start and end date). While I understand the pro version includes some date-based options, they are very limited as they only allow filtering by day, month, or year. A more flexible calendar-based system where users can select a specific date range would be much more helpful. 3. **Excel Export Option:** Adding an option to export form data in Excel format. This would provide better accessibility, consume fewer server resources, and significantly reduce file size. For example: * - A CSV file with 30,000 entries takes up about **40MB**. - The same data exported in Excel format would only be about 4MB—almost **10 times smaller.** * **Additional Notes (FYI):** - While reviewing the code, it seems the batch size adjustment only applies to the export process. However, this issue also affects **imports **with large records. - One of my clients, who has a large dataset, reported similar problems in the** Entries **tab and while **downloading CSV** files in the pro version. - The issue also occurs when attaching a CSV file to emails during form submission. - In the **Reports tab**, pages with large datasets fail to load and time out after a few minutes. * Thank you for your continued support, and I hope these suggestions help improve the plugin’s functionality for all users. Please let me know if there’s anything else I can assist with. * BR Sina * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Formidable Forms - WordPress Form Builder for Contact Forms, Calculators, Quizzes & More] issue with huge Form entries Export in formidable form Plugin](https://wordpress.org/support/topic/issue-with-huge-form-entries-export-in-formidable-form-plugin-2/) * Thread Starter [sinapars](https://wordpress.org/support/users/sinapars/) * (@sinapars) * [1 year, 7 months ago](https://wordpress.org/support/topic/issue-with-huge-form-entries-export-in-formidable-form-plugin-2/#post-18223602) * thanks for response [@jonathanenlared](https://wordpress.org/support/users/jonathanenlared/), Sorry for the delayMy posts need to be approved but I don’t know why it’s not happening or it’s happening twice! * I enabled error logs but no errors are saved in the debug.log file and I don’t get any errors in the output either But in the console as I mentioned before I get error 500 of which I sent you screenshots * [https://drive.google.com/file/d/1a87-bj9HJ1JIaim23jF8yixVJ0bNCP9Q/view](https://drive.google.com/file/d/1a87-bj9HJ1JIaim23jF8yixVJ0bNCP9Q/view) [https://drive.google.com/file/d/1HRahdllSl4ht2r77zNev-h79VC-mRZ5P/view](https://drive.google.com/file/d/1HRahdllSl4ht2r77zNev-h79VC-mRZ5P/view) * **But what might help you is the error I am getting in the web server error logs:** * `[Thu Jan 02 20:00:17.636002 2025] [core:error] [pid 50254:tid 140668735305472][ client X.XX.X.XXX:48554] Script timed out before returning headers: admin-ajax. php, referer: http://XXXXX/XX/wp-admin/admin.php?page=formidable-import` * BR Viewing 15 replies - 1 through 15 (of 83 total) 1 [2](https://wordpress.org/support/users/sinapars/replies/page/2/?output_format=md) [3](https://wordpress.org/support/users/sinapars/replies/page/3/?output_format=md) [4](https://wordpress.org/support/users/sinapars/replies/page/4/?output_format=md) [5](https://wordpress.org/support/users/sinapars/replies/page/5/?output_format=md) [6](https://wordpress.org/support/users/sinapars/replies/page/6/?output_format=md) [→](https://wordpress.org/support/users/sinapars/replies/page/2/?output_format=md)