mrmut

I don’t know, but I would try to test run new WAMP in a virtual machine.

I use WAMP, and this works fine with normal paths. Maybe you should check/test for PHP version issues?

Wow Michael, you are OK! ??

I thought something happened to you.

Glad you are back. Hope all is good with life.

It seems to me you have an issue with cf7 and not cfdb.
Make a test install on WAMP and test.

You should either style the resulting front-end table by yourself, or pull data from the database via PHP.

Па што онда? Има и 350 мили?уна славена. Ово ?е интернационални форум.

I think this is due to plugin that writes that date. CFDB just stores stuff. I think in my DB (haven’t checked, but we use ISO dates, so I would notice) all is fine. Try with another plugin to see what happens when you store stuff.

I use contact form 7.

This is amazing. Did you really expect something to help you? You could have write in Korean or Russian as well.

No support. I think the guy might have died.

As for deleting, you can do that from administration in the backend.

Yes.

I think it takes WP/server timezone. Set that instead.

Add a field with user selection?

There is something wrong there.
Get another cf plugin and test with it to see if it is due to CF7.

You will have to use javascript for that, but it would be simpler to delete a row.

Of course you can. Go to shortcode generator and remove columns you don’t like.

EDIT: The test entries can be deleted in the back end.

• This reply was modified 4 years, 9 months ago by mrmut.

No, it was actually your plugin; there is some kind of built in limitation.

Maybe CF7 pulls WP file upload limit as default? The upload failed exactly when it was over 2 MB.

I checked both MariaDB/MySQL logs and PHP logs, and while the error pointed to CFDB, there was no limitation on the server side – both blob size and max upload size on PHP side were set more than sufficiently high (I think 64 MB).

What solved the problem is setting the file limit in CF7 to very high value. I tested a form with file upload only without any file size restriction, and the error was the same. When I set the file size deliberate lot very high byte value (100000000) the form worked.

Apparently, it is a known issue. I found the solution somewhere on the internet based on the same problem description.