Page 1 of 1

Related Entries Smarty Error

Posted: Thu Dec 02, 2010 9:49 pm
by danst0
Hi,

I just realized that I am having issues with the related entries plugin, I receive the following error.
Warning: Smarty error: unable to read resource: "file:/usr/www/users/username/plugins/serendipity_event_relatedlinks/plugin_relatedlinks.tpl" in /usr/www/users/username/bundled-libs/Smarty/libs/Smarty.class.php on line 1093

I am including the related links plugin using smarty, but I receive the same error with the other options. Of course the tpl file exists and is readable. I just replaced all files in the plugin folder with new ones from s9y.org.

According to my Hetzner Server Frontend my real path is /usr/home/username/public_html/ and this is also configured in the blog preferences. So I have two questions:

Why does S9Y show the wrong path?

How can I tell s9y to use the correct path?

Daniel

Re: Related Entries Smarty Error

Posted: Fri Dec 03, 2010 2:01 pm
by garvinhicking
Hi!

If smarty reports that it cannot read the file, it actually realls means that there is a problem.

Your real path is the one where Smarty.class.php is reported to live in. If hetzner tells you otherwise, they use symlinks to obfuscate that...but PHP always reports the resolved, real path.

Regards,
Garvin

Re: Related Entries Smarty Error

Posted: Fri Dec 03, 2010 5:53 pm
by danst0
Ok, the problem went away, as soon as I deleted the current related links in my entry and re-inputed them...

This also showed me the cause of another problem I recently struggled with (http://board.s9y.org/viewtopic.php?f=3&t=17184). I did not know that the related links are statically created once upon saving the article, so it is obvious that the change of the tpl file had no effect, since I did not re-save all my entries with related links.

Honestly, I thought this is the reason for having a template that I can directly see the changes there immediately within my entries...

Re: Related Entries Smarty Error

Posted: Mon Dec 06, 2010 11:24 am
by garvinhicking
Hi!

You might be using the Caching option of extended entries? :-)

If so, of course that caches plugins like these :)

Regards,
Garvin