Hi,

This was originally posted in another thread ( https://xoops.org/modules/newbb/viewtopic.php?start=10&topic_id=76447&order=ASC&status=&mode=0 ) regarding forum issues with newbb and then smartsection issues but think this issue could require an own thread:

The main page does not load, just blank. Newsitems in smartsection load as they should for example http://vaken.se/modules/smartsection/item.php?itemid=2389

But going directly to http://vaken.se only works sometimes, seems a bit random, sometimes it works directly and sometimes 10+ refresh does not load the page. It shows a blank page with no content (0 kb).

Web hotel support found this in error_log:

[18-Nov-2013 02:36:10] PHP Warning: unlink(/home/vakense/public_html/xoops_data/caches/xoops_cache/xoops_system_modules_active_http%3A%2F%2Fvaken_se.php) [function.unlink]: No such file or directory in /home/vakense/public_html/class/file/file.php on line 328

file.php and line 328 is the following:
return unlink($this->pwd());

Could the error found in error_log be an explanation or our issues?

This is what our XOOPS "expert" had time to find when looking in the other issue with smartsection, uncertain when he will be able to look at the issue again:

"Look like it's related to templates. Smarty is the name of the program that manages templates for xoops. This program manages templates_c och
the cache folder.
_
It looks like this have stopped to work. template_c used to be full of files and is now empty."

After this web hotel support changed rights to 755 for folders and 644 for files. The problems with the main page loading blank actually started after this but according to the web hotel this was the correct settings for suPHP. Be saying it started after this the problem became very common two days after changing rights for folder and files, I can't quite remember is it was an issue the same day the file rights where changed.

I don't know if it's allowed on this forum but if it is we are considering to hire someone to look in the issue and troubleshoot, with an extra reward if the issue is solved, main problem is that the start page just loads blank most of the time.

From what I have heard reported and experienced myself the issues started with seldom occurrences of the main page loading blank and increased.

From debug:

"Fel
Information: Undefined variable: start i fil /modules/smartsection/blocks/items_recent.php rad 44
Information: Function xoops_getLinkedUnameFromId() is deprecated, use XoopsUserUtility::getUnameFromId() instead i fil /include/functions.legacy.php rad 43
Varning: xoops_load('userutility') is deprecated, use xoops_load('xoopsuserutility') i fil /class/xoopsload.php rad 65
Varning: MyTextSanitizer::makeTboxData4Show is deprecated i fil /class/module.textsanitizer.php rad 783
Information: Undefined variable: messages i fil /modules/system/blocks/system_blocks.php rad 175"

templates_c directory is very old and not used anymore , so this cant be the reason

Try:
1.default template instead of your own template
2.check your directory settings (chmod)
3.disable your blocks , if success enable them one at a time
4.turnoff modules likes blocks (do not uninstall them !!)

Better : go and upgrade to newer version of xoops , your version is outdated en you will run for sure in problems when your hoster decides to upgrade his php and sql version

BACKUP FIRST !!

Issue solved, got help from a programmer. An array got bigger than 128 MB, he changed the code to fix the issue.

I'll paste what he wrote when he found the issue, use Google translate to translate from Swedish to English if needed:
"I /www/kernel/groupperm.php (xoops egen kod) har vi en funktion som käkar nästan allt minne. Den skapar ett objekt per rad i group_permission.

Här ser ni hur minnet går åt nästan helt:
(Därav kraschen men den kommer senare.)

groupperm (1) - mem_usage: 13056 kb, peak: 13056 kb
groupperm (1001) - mem_usage: 20992 kb, peak: 20992 kb
groupperm (2001) - mem_usage: 28928 kb, peak: 28928 kb
groupperm (3001) - mem_usage: 36864 kb, peak: 36864 kb
groupperm (4001) - mem_usage: 45056 kb, peak: 45056 kb
groupperm (5001) - mem_usage: 52992 kb, peak: 52992 kb
groupperm (6001) - mem_usage: 60672 kb, peak: 60672 kb
groupperm (7001) - mem_usage: 68608 kb, peak: 68608 kb
groupperm (8001) - mem_usage: 76544 kb, peak: 76544 kb
groupperm (9001) - mem_usage: 84992 kb, peak: 84992 kb
groupperm (10001) - mem_usage: 92672 kb, peak: 92672 kb
groupperm (11001) - mem_usage: 100608 kb, peak: 100608 kb
groupperm (12001) - mem_usage: 108544 kb, peak: 108544 kb
groupperm (13001) - mem_usage: 116224 kb, peak: 116224 kb
groupperm (14001) - mem_usage: 124160 kb, peak: 124160 kb <- nära 128 MB!

Vad används denna gigantiska array till sen?
Jo, den förrut omtalade permission-loopen konverterar den till en ny, mindre array, varpå den förra frigörs."

Thanks for the reporting.

What would be interesting to know is if the problems still exist in XOOPS 2.5.6, and if yes, how did he fixed the issue in XOOPS 2.4.3, so we can see if we can apply his fix in the next version of XOOPS.