deltafactory
Forum Replies Created
-
Hi @wysija,
I just tested the latest version which supposedly addresses the issue. I am still seeing the error. Not sure if this affects your test scenario, but it only occurs under the method to update custom fields, not the core first/last name and email.
Addressed in latest release, thanks!
I see this is resolved in yesterday’s release. Thank you very much!
This user is likely reporting the exact same issue. It’s in the subject and is 2 days old.
https://wordpress.org/support/topic/fatal-error-uncaught-pdoexception-sqlstatehy000/
I resolved the error using the steps I’ve documented for you. I’m trying to help you improve your plugin and save others from running into the same problem.
@florent73, if you feel capable of modifying some PHP code files, look in the plugin source under lib/Config/Migrator.php and look at lines 164-165.
'first_name tinytext NOT NULL DEFAULT "",', 'last_name tinytext NOT NULL DEFAULT "",',Remove
DEFAULT ""from both of the lines above. I hope that you can deactivate and reactivate the plugin to re-trigger this code and run it successfully.@wysija, this is likely related to an issue I reported over 4 months ago.
https://wordpress.org/support/topic/fatal-error-when-activating-current-beta-under-clean-install/
I documented the cause of the issue as it relates to the SQL statements used during the plugin’s activation process and possible conflicts with certain MySQL server configurations.
@wysija, can you please let me know if this is ever going to be addressed?
The ability to add custom mailing method options could have other uses/benefits beyond my specific use case. Would you consider adding support for that?
I am already using a custom mail logging tool that offers more flexibility that I would like to continue to use.
The ability to add custom mailing method options could have other uses/benefits beyond my specific use case. Would you consider adding support for that?
OK thanks. It hasn’t been fixed in the latest release. The other post addressed a few different issues and had been marked as resolved by your staff so I thought it was important to bring up again.
Forum: Plugins
In reply to: [Contact Form 7] Contact Form 7 don’t allow me to upload a file above 2mb@karaptsias, that isn’t recommended since it won’t survive an update of the plugin.
The limit parameter is the correct way to set the max file size. The docs have the full details, https://contactform7.com/file-uploading-and-attachment/
@diegobgl96, if you’re still having the problem did you make sure to modify both of the related settings in php.ini?
Further reading as to the source of the problem with regard to DDL (CREATE/ALTER TABLE, etc.) statements:
https://dev.mysql.com/doc/refman/5.7/en/sql-mode.html#sql-mode-strictThis was still not addressed.
Forum: Plugins
In reply to: [Login with Amazon] Improper use of sessionsThere’s a flaw with my approach, and a possible solution:
It’s true that WP Nonces use information about the current user session to generate the value. However, in this case there is no user and the anonymous context is the same for everyone. At a given moment in time, the nonce for all unauthorized users would be the same.
The solution would be to use a Session cookie, not a PHP session. The value of the cookie would be another component used to generate the WP Nonce.
The next concern would be that this value is accessible from the browser. However, PHPSESSID cookies have the same exact issue.
Forum: Plugins
In reply to: [Login with Amazon] Improper use of sessionsThe WP nonces use a number of components including a timestamp to generate a unique, randomized value that changes over time. We avoid the need to store that component because we can algorithmically regenerate it.
Forgive me for not being clear: the WP Session that is used is not the same thing as a PHP Session. WordPress itself does not use PHP Sessions. Are you still seeing session cookies created when using my fork?
I expect to be testing the changes in my repo (including future enhancements) next week, so feel free to follow along there.