Hi, I have a website that is still running CMS Made Simple 1.9.1. I'm using PHP 5.4.4-14, and MySQL 5.5.35, and Formbrowser 0.3.2.
The website contains a from that also writes its results to the formbrowser and by now contains about 2500 records. 1 record contains about 30 fields.
Recently the export to excel has stopped working and you just end up with the export url in the browser. Some other forms which records are available in de formbrowser still work but they contain less records and fields.
The export still works if the non memory option is selected (Writes an .xls to "uploads" directory).
I've already reduced the number of records below 2000 but it is still not working.
Is there a memory limit? Something else I should be looking for?
Excel Formbrowser not working anymore
-
- Power Poster
- Posts: 1049
- Joined: Wed Mar 19, 2008 4:54 pm
Re: Excel Formbrowser not working anymore
cmsms 1.9.1 is way too old to get support, http://forum.cmsmadesimple.org/viewtopi ... 40&t=30336
Also your formbrowser is not up-to-date; current version 0.4.2
So: update your cmsms and all your modules.
Also your formbrowser is not up-to-date; current version 0.4.2
So: update your cmsms and all your modules.
Re: Excel Formbrowser not working anymore
Valid. (Maybe I'll have a go at upgrading)staartmees wrote:cmsms 1.9.1 is way too old to get support, http://forum.cmsmadesimple.org/viewtopi ... 40&t=30336
Also your formbrowser is not up-to-date; current version 0.4.2
So: update your cmsms and all your modules.
But if someone has run into this behaviour and diagnosed it. Let me know.
I'm merely poking at the collective memory that maybe is available here.
-
- Power Poster
- Posts: 1049
- Joined: Wed Mar 19, 2008 4:54 pm
Re: Excel Formbrowser not working anymore
Those old versions weren't made to work with php 5.4.x
Re: Excel Formbrowser not working anymore
Well Captain Obvious, that version of PHP wasn't around.staartmees wrote:Those old versions weren't made to work with php 5.4.x
But ontopic, reducing the number of records below 2000 has resulted in a solution as the export now works again.
This one can be closed...