TOPIC: .csv Download Not Accessable On The Backend

I'm getting the following error when accessing the .csv Download link in the Administrator:

Fatal error: Out of memory (allocated 71303168) (tried to allocate 196608 bytes) in /home/stridean/public_html/administrator/modules/mod_cbadmin/tmpl/menu.php on line 111

• I've never had an issue with this before
• I haven't made any changes to my server recently (months)
• I am able to access the .csv download link in the front-end
• I'm running DTRegister 3.1.11c

Any thougths on getting it working again would be much appreciated.

S

The error tells you exactly what the problem is. You've hit your PHP memory limit. You need to increase the setting for memory_limit or have your web host do it. You've basically hit an amount of records then when the admin side attempts to load it all, with everything else, it uses more PHP memory than your server is presently configured to allow.

It seems strange that just bringing up the list of events to decide which one to select for the .csv export would need so much memory? No?

And why would it need a different amount of memory on the front end than the back end? The front end works and the back end doesn't so it would appear that the back end is maxing out the memory limit while the front end isn't? Either way, just populating the event list shouldn't really need anything for resources (you wouldn't think).

Nathan, can you shed a bit of light on how this works within dtRegister so I can understand it a bit better?

Frontend and backend of the sites are completely different with what is being loaded and resources used overall. Nothing we can do about that.

You see just a list of events. What your server sees is all of those events... each with hundreds or thousands of saved variables... with associated fields needed for CSV that all have many variables... along with accessing the many config variables... basically, it's more than just listing some event titles.

There's nothing we can do here. It is what it is and you'll have to address it at the server level.

If Fields and Events are in an "unpublished" state does dtRegister still "read" them as a variable when populating things such as the .CSV Export list?

Events also have an "Archive" state, does dtRegister "read" Archived Events when populating things such as the .CSV Export list?

I'm just thinking about the best way to speed up the reading speed/use less memory resources, when my dtRegister has 400+ Fields and 130+ Events. Does "Unplublished" or "Archived" states allow the system to index less data when operating or is deleting unused Events and Fields the only way to use less memory resources?