Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
Pages: 1
#1 2006-01-11 03:13:34
- Andrew
- Plugin Author
- Registered: 2004-02-23
- Posts: 730
evaluator_trace.php ?
Each time someone leaves a comment on a v4.0.3 site, the site breaks, at least this is how it behaves for my sites that use /textpattern/tmp as plugin_cache_dir. The reason is that a file named evaluator_trace.php is written to /textpattern/tmp when a new comment is recorded. Because files in this directory are automatically included and this is not a valid php file, fatal errors kill page execution.
What is the expected behavior of comment_evaluation() (where the file is created & written)? Am I only supposed to be using /textpattern/tmp as plugin_cache_dir if I’m working locally?
Last edited by Andrew (2006-01-11 03:16:29)
Offline
Re: evaluator_trace.php ?
Why would you use …/tmp as a plugin cache dir? (imho, the purpose of the plugin cache dir is to hold plugins during development thus enabling plugin authors to install new versions of their plugins without going through the txp backend)
I’d suggest to use a distinct dir as the plugin cache dir.
Offline
#3 2006-01-11 07:10:57
- Andrew
- Plugin Author
- Registered: 2004-02-23
- Posts: 730
Re: evaluator_trace.php ?
Offline
Re: evaluator_trace.php ?
“Oh, what a difference a day makes…” (or, as in that case, seven months). Sencer obviously wasn’t aware of the side effects when he chose to write the diagnostic output of the spam evaluator to the same directory which one might use as a plugin cache, obeying his “ancient” advice.
I’ve posted a feature request referencing your case.
Last edited by wet (2006-01-11 07:24:46)
Offline
Re: evaluator_trace.php ?
I am currently caught up in this loop. Upgraded to 4.0.3 four days ago. Added new content with no problems. A nice easy upgrade.
The first new comment blew up the whole shebang. Not knowing any better, I had pointed all my /tmp directories to the same place. Including a separate PHP file that wrote cached rss feeds to that same directory. I think that file is what blew it all up.
It’s gone now, and the rss/php file now points to its own dedicated tmp directory, but Textpattern is still dead. Even after clearing the tmp directories, I can’t even login. Database checks out as fine, and exports with no problem. Yet I get a blank white page instead of the standard login.
So how do I get out of this loop?
TextPattern user since 04/04/04
Offline
#6 2006-01-18 18:09:08
- Andrew
- Plugin Author
- Registered: 2004-02-23
- Posts: 730
Re: evaluator_trace.php ?
Is your plugin_cache_dir is set to something different than /textpattern/tmp?
Offline
Re: evaluator_trace.php ?
So how do I get out of this loop?
Hmm? loop? If plugin_cache_dir is set, textpattern will include and parse the available .php files in that directory. That’s all, there’s no loop. If you suspect your poblem is related, unset the plugin_cache_dir or set it to a directory other than the normally used tmp-directory.
Offline
Re: evaluator_trace.php ?
> Andrew wrote:
> Is your plugin_cache_dir is set to something different than /textpattern/tmp?
Why, yes, as I said, I stupidly pointed everything to one /tmp directory. To be efficient.
It’s fixed now, thanks to filip at Txd:
“it’s fixed now. I followed the topic you linked, logged into MySQL directly and changed the plugin cache dir to ../textpattern/plugin_tmp (which I created). It must not be set to the same place as temp (which most likely was not your fault).”
But it was my fault. Why did I change soemthing that had been working before the upgrade? Because, if I recall, the cache was set by default for /var/tmp
Of course, there was no such directory. I couldn’t see the harm in pointing it to a real one. My bad.
And Sencer, my use of the word “loop” was not meant in a semantic programming sense, since I’m not a programmer. I meant, I’ve got a problem, I know what is, and how to fix it, yet the problem keeps me from logging in to fix it.
TextPattern user since 04/04/04
Offline
Pages: 1