Once I FINALLY got started on a members directory useing MX Directory again after losing countless data entry hours due to a module failure... I have alpha listings enabled & after approx. 90 entries... when logged in & clicking on H or O... I get a blank page. When visiting the site as a tipical user... & clicking on the same Letters... I get this error...

Warning: Unknown(): A session is active. You cannot change the session module's ini settings at this time. in Unknown on line 0

I have backed up the database...

Xoops version 2.0.9.2
mXdirectory version 2

Help Please?

Todd

The module is not throwing this, it is either PHP or your web server. A restart may help, also you may want to re-FTP the module pages up again over the top of the existing files and then update the module.

The reason I suggest re-upping the pages, is that it sounds like someone is trying to hijack your sessions... line 0 of 'unknown' sounds pretty shady to me.

Ok... I re-uploaded the mxdirectory folder...updated the module in admin...restarted the server...still throwing the same error. It seems kinda odd that this error only appears when clicking on the H or the O in the alpha listing. Everything else seems to be running fine. Kinda scarey actually seeing that I lost a ton of info & hours in a previous attempt.

I turned on PHP Debug mode & now Im getting these errors...

Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 25213 bytes) in /home/webadmin/highlandcountychamber.com/html/html/class/xoopstree.php on line 133

Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 2 bytes) in /home/webadmin/highlandcountychamber.com/html/html/class/database/mysqldatabase.php on line 215

Warning: Unknown(): A session is active. You cannot change the session module's ini settings at this time. in Unknown on line 0
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
In MSQL/Blocks Debug mode...

SELECT * FROM xoops_config WHERE (conf_modid = 0 AND conf_catid = 1) ORDER BY conf_order ASC
SELECT sess_data FROM xoops_session WHERE sess_id = 'b0ed373c2e88eaf4641cb8fe64b0e35f'
SELECT * FROM xoops_users WHERE uid=1
SELECT * FROM xoops_modules WHERE dirname = 'system'
SELECT * FROM xoops_configcategory WHERE confcat_id=1
SELECT * FROM xoops_config WHERE (conf_modid = 0 AND conf_catid = 1) ORDER BY conf_order ASC
SELECT * FROM xoops_modules WHERE (hasmain = 1 AND isactive = 1) ORDER BY weight ASC, mid ASC
SELECT * FROM xoops_tplset
SELECT * FROM xoops_configoption WHERE conf_id = 13 ORDER BY confop_id ASC
SELECT * FROM xoops_groups WHERE groupid != 3
SELECT * FROM xoops_configoption WHERE conf_id = 32 ORDER BY confop_id ASC
SELECT * FROM xoops_configoption WHERE conf_id = 33 ORDER BY confop_id ASC
SELECT * FROM xoops_smiles
SELECT * FROM xoops_modules WHERE hasmain = 1 ORDER BY weight ASC, mid ASC
SELECT * FROM xoops_group_permission WHERE (gperm_name = 'module_admin' AND gperm_modid = 1 AND (gperm_groupid = 1 OR gperm_groupid = 2))
Total: 15 queries

Blocks
Total: 0 blocks

Execution Time
XOOPS took 0.13330912590027 seconds to load.

Extra


Todd

Anyone else gotta clue whats happening here?

Quote:

Well something seems to be using the 32 MB of memory that you are alocated from the php.ini file.

The warning, I do not know what is causing that. And the MySQL querry, I assume did not show red. As far as I can tell it looks pretty normal.

So you need to try to find what is using your resources or allocate more memory.

Now I think, if on a shared server, it may not even be your application using up the memory.

But 32 MBs has already been increased some. I believe the default is 8 MB.

Ok...after talking with my server techs...uping the memory to 50M...now its not throwing any errors...now it just brings a PAGE CANNOT BE DISPLAYED page. back to the server & re-uping the memory to 80M...still the same error page so it seems to NOT be a memory problem BUT...what I think is odd is...this only happens upon clicking the H or the O...I can go top a category with a business that I know starts with an H...everything works fine there. That error presented itself & Im afraid if I keep adding entries, I will lose it all as I did in a previous attempt. There has to be something somewhere causing this error. Im begging for an upgrade or a hack. Im really stumped.

Todd @ GNP Designz

You have some MAJOR overhead going on there...

What is the count of H or O entities that are in the dB? Are there significantly more or less entries than for other letters?

The function is exactly the same for any letter that you click on, so the fact that it's hurling on H & O leads me to believe that there is something aside from the alpha query (my code) causing your issues.

Try checking your data... one of the records may have something causing a MySQL or sanitization issue.

Try banging it around with myadmin and looking through your H & O records for something out of the ordinary...

Of course you could verify this by dumping all the H records and creating a simple H entry to test... if it works in alphaview, then you will know it is the data in one of the existing entries causing the problem. If this is the case, when you remove the offending record, all others should work fine.

If your using custom templates, try regenerating them...

Make sure the URL (in your browser status bar) is correct by comparing the URL for H & O to the other letters.

I have O & H entries in my test dB and it works just great, so it's not a problem with the alpha list code.

GL!

well...now I feel a bit silly...after removing just one entry from the H section...the module began working again...after removing one entry from the O section...it started working again as well. After removing those entries & seen that it was working again, I re-entered the same businesses & it still worked. I added more & it's still working. Just a crazy glitch? I dunno but Im very happy & I thank you all for your time & help with this matter.

Todd @ GNP Designz