Main Menu
collapse

Simple Portal Archived Forum

This is an Archive Forum.

The content in this forum may be out-of-date or have been superseded by newer information, and links in forum pages to other sites may not work.
This forum contains archives for future reference.

Visit our thread at Simple Machines Forum for current support.

SMF 2.1 users: EhPortal is a ported version of Simple Portal specifically designed for the SMF 2.1 branch.
Please visit web-develop.ca to download EhPortal and for its support.

User Info

Welcome Guest.
Please log in.

Who's Online

  • Dot Guests: 789
  • Dot Hidden: 0
  • Dot Users: 0

There aren't any users online.

Recent Posts

Adding Forums Button to Nav bar by jirapon
[August 01, 2019, 09:07:12 AM]


Re: Board Icons by ♦ Ninja ZX-10RR ♦
[July 30, 2019, 04:03:41 PM]


MOVED: Czech translation???? by ♦ Ninja ZX-10RR ♦
[July 30, 2019, 03:04:51 PM]


Board Icons by jirapon
[July 30, 2019, 07:28:44 AM]


Re: Thankyou Simpleportal, by ♦ Ninja ZX-10RR ♦
[July 29, 2019, 09:41:29 AM]


If you're interested in helping other members with support requests, consider joining the Community Support Helpers group.

[SOLVED] Cache directory not writeable in standalone mode

Started by kai920, July 30, 2009, 09:24:22 AM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

kai920

I'm using SP 2.2.2 with SMF 2.0 RC1.2.

SMF is installed in /forums, and I copied the standalone php file to /index.php and changed the $forum_dir variable. The portal homepage loads fine on /index.php but I'm getting this warning:

QuoteThe cache directory is not writable - this will adversely affect the performance of your forum.

I've tried changing the /forums/cache directory to 777 or 775, 755 but the message persists. Note that it only appears on the portal's standalone index.php file and not anywhere else.

If SP is in the default setting of Frontpage mode I do not see the performance warning on the portal page (/forums).

Any ideas?

ディン1031

Question is it solved or did this error appear?
Again... I'm having time problems...Normal Monday to Friday I'm at office from 6:00-16:00 (On my local time ;P).

kai920

Not solved.

I need some ideas on how to eliminate SP as a potential cause for this...

[SiNaN]

Well, I haven't seen this before really. Try adding this after SSI.php is included in standalone file:

var_dump($cachedir);

It will echo the relative path to cache directory. See if the path is correct.
And slowly, you come to realize... It's all as it should be...

kai920

I included var_dump($cachedir); and it says NULL when I load the frontpage (standalone file).

kai920

Any reason why $cachedir would be null? (I only see the warning on the standalone php page)

ディン1031

Did you disable the complete cache?
Possible this will not fill this value.
Again... I'm having time problems...Normal Monday to Friday I'm at office from 6:00-16:00 (On my local time ;P).

kai920

My cache was disabled, but I changed it to Level 1 and it still shows the warning - on the standalone php page.

(is the cache warning supposed to show on other pages?)

ディン1031

No i only ask if you disabled it =). Possible that the reason why the $cachedir is empty. I want only find a hint for the empty cachdir value and this would be a good reason.
Again... I'm having time problems...Normal Monday to Friday I'm at office from 6:00-16:00 (On my local time ;P).

kai920

Well as I said, I enabled caching (level 1) and the warning is still showing...

kai920

Still seeing this on SP 2.3. Not a showstopper by any means, but I'm just curious why the message is there...


Nathaniel

Sorry for the long wait on this issue.

I have another suggestion, have a look in your 'Settings.php' file.

Is the $cachedir variable defined there? index.php will give $cachedir an automatic value in case your Settings.php file is corrupt, something that SSI.php doesn't. That would explain the issue with the Standalone mod for the portal.
SMF Friend (Former Support Specialist) | SimplePortal DeveloperMy SMF Mods | SimplePortal"Quis custodiet ipsos custodes?" - Who will Guard the Guards?Please don't send me ANY support related PMs. I will just delete them.

kai920

Ah, you may be on to something :)

There's no $cachedir in settings.php. Should I just add it in?

Nathaniel

Yes, add it after the declaration of the $sourcedir setting. Make sure that it is the exact path to your cache directory.
SMF Friend (Former Support Specialist) | SimplePortal DeveloperMy SMF Mods | SimplePortal"Quis custodiet ipsos custodes?" - Who will Guard the Guards?Please don't send me ANY support related PMs. I will just delete them.

kai920

Very nice, the message is gone now. Thank you  :applause:

shouldn't this have taken care of the message in the standalone php file?


// Make absolutely sure the cache directory is defined.
if ((empty($cachedir) || !file_exists($cachedir)) && file_exists($boarddir . '/cache'))
$cachedir = $boarddir . '/cache';

Nathaniel

Yes, it should have worked anyway. I can only replicate this issue with the Settings.php file, if I remove all references to $cachedir.

My Settings.php file on a SMF 2 RC1.2 test install that was installed with the full install package works has the code below:
if (!file_exists($cachedir) && file_exists($boarddir . '/cache'))
$cachedir = $boarddir . '/cache';


Your 'checking code' for the $cachedir may be from an older version of SMF, but it should still work...

I can't say I am sure why it wasn't working, I'm glad its working now though. :)
SMF Friend (Former Support Specialist) | SimplePortal DeveloperMy SMF Mods | SimplePortal"Quis custodiet ipsos custodes?" - Who will Guard the Guards?Please don't send me ANY support related PMs. I will just delete them.

kai920

Tried your code, doesn't work either unless I have the specific $cachedir definition in settings.php. Strange..

Chas

Just experienced the same problem. I had just enabled Level 1 Cache in SMF 2.0 RC3 with SP 2.3.2.

Previously the cache was set to No Cache.

FTP and SMF reported that the directory was set to 777 but my standalone page reported this error.

Adding $cachedir to my Settings.php file and setting the full path removed the error message.

Thanks.