thomasbadstuebner

OK, last shot at gaining some insight into this issue.

I still had a doubt that my import data might be the cause so, to rule out this possibility, I have done the following:

– deleted all fields and field groups from PD that the plugin will allow me to delete.
– created a new field called room_number
– added 20 records manually via the back-end
– exported the list as CSV via the plugin
– re-imported the CSV file to check if import works. The import is successful with no errors reported.
– repeat the export/import process

The outcome is always the same. Each successive import is successful until 1770 imported records are exceeded. Thereafter the system reports the same fatal error:

Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 28672 bytes) in C:\xampp\htdocs\signup\wp-content\plugins\participants-database\participants-database.php on line 2087

I am running the latest version of wordpress and the latest version of the PD plugin.
Imports are set to create a new record with each import as this would be a requirement of the system I’m trying to implement.

Referring to line 2087 of participants-database.php it seems to me that the problem lies with generating an unique private ID for each new record.
It’s interesting that this problem only exists when the number of saved records exceeds 1770 and more specifically that it only affects imports via CSV.
If I add a new record via the back-end then it works just fine. In this case a new record with unique ID is generated almost instantly. However if I try to import even a single new record via CSV then the process terminates in a fatal error.

Do you think that this issue can be resolved somehow?

Best regards
Tom

I only get the error message at the time of the upload and thereafter if I try to create a new record via my Signup page.

I’ve tried these two things today:

– I got rid of any field data that might contain syntax errors keeping only the straightforward Yes/No data

– I divided the data set into 3 separate csv files and uploaded them one after the other in a variety of different orders to see whether a single record could be corrupted.

However the outcome is always the same, as soon as the number of records exceeds 1770 the system reports the same fatal error.

That’s all I can tell you really.

I’m using Version 1.7.0.13
This appears to be the latest version.

Thanks
I appreciate the support.
Best regards, Tom

Michael you’re a genius!
You’ve made my life a lot easier ??
Much thanks from myself and all my staff at the dive centre.
Best regards
Tom

Hi Michael

Thanks ever so much for your help. The search logic works perfectly.
There are still a couple of issues though.

1. When the search page loads, the following fields are pre-filled:

“First Name” is pre-filled with value: “[echo_var var=’First-Name’]”
“Last Name” is pre-filled with value: “[echo_var var=’Last-Name’]”
“Bag” is pre-filled with value: “[echo_var var=’Bag’]”

If I run a search with any of these values inputted then an error message appears for each record in the DB. I need to first delete these values from each field before I can successfully perform a search.

For now I have managed to work around this problem by using javascript to clear the form fields on page load.

<script>
var input = document.getElementById('search-first-name');
input.value = '';
</script>
<script>
var input = document.getElementById('search-last-name');
input.value = '';
</script>
<script>
var input = document.getElementById('search-bag');
input.value = '';
</script>

I’m sure that there is a more elegant solution ??
As I’ve said before my coding ability is very limited.

2. Each time the search page loads a search is automatically run on the DB and all of the DB entries are automatically displayed by the CFDB datatable shortcode.

If possible I would prefer if no data is displayed until after a search is performed by a user.

Thanks for the time and effort you’ve taken to help me.
I greatly appreciate it.

Tom