Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
Re: Feedback to: Textpattern CMS 4.2.0 Release Candidate: Help us test!
Neko wrote:
I see logs are recording hits on feed URLs, such as /rss. It this by design?
Hmmm, this is likely a side-effect of r3258. I’ll try and confirm when I get a chance. Whether this is a good or a bad thing I don’t know yet. Would you prefer it not to?
The smd plugin menagerie — for when you need one more gribble of power from Textpattern. Bleeding-edge code available on GitHub.
Txp Builders – finely-crafted code, design and Txp
Offline
#38 2009-08-01 15:44:37
- Neko
- Member
- Registered: 2004-03-18
- Posts: 458
Re: Feedback to: Textpattern CMS 4.2.0 Release Candidate: Help us test!
Bloke wrote:
Whether this is a good or a bad thing I don’t know yet. Would you prefer it not to?
I don’t know, I’m neutral. :) For one thing it is more data, for another it is more load on the database, I guess.
The thing is, it appears that RC is not recording all hits on feeds, just a few on certain conditions. Which conditions I don’t know.
Offline
Re: Feedback to: Textpattern CMS 4.2.0 Release Candidate: Help us test!
Neko wrote:
Another report: when deleting a user, TXP returns “Please re-assign user’s content”. Problem is that that user doesn’t have any article associated to him. Could you reproduce such error?
We do not check if the user actually has any content – we just want to know the new owner in case she had.
Offline
Re: Feedback to: Textpattern CMS 4.2.0 Release Candidate: Help us test!
Bloke wrote:
Would you prefer it not to?
Not.
Offline
Re: Feedback to: Textpattern CMS 4.2.0 Release Candidate: Help us test!
What’s the correct way to deal with Textpattern’s textpattern/setup directory if you’re using multiple sites? If you delete it, you can’t install additional sites, but if you keep it around, couldn’t someone exploit that?
Offline
#42 2009-08-01 22:15:21
- Neko
- Member
- Registered: 2004-03-18
- Posts: 458
Re: Feedback to: Textpattern CMS 4.2.0 Release Candidate: Help us test!
wet wrote:
We do not check if the user actually has any content – we just want to know the new owner in case she had.
I see now, thanks. Problem is, at least with my RC, that the system doesn’t actually delete the user. It just displays the message.
Offline
Re: Feedback to: Textpattern CMS 4.2.0 Release Candidate: Help us test!
Neko wrote:
Problem is, at least with my RC, that the system doesn’t actually delete the user. It just displays the message.
This is not a problem but the desired effect. If you try to delete a user but omit to select the new owner of said user in the dropdown labelled “Assign user’s content to:” we flash an error message instructing you to “please re-assign user’s content”.
Offline
#44 2009-08-01 22:30:44
- Neko
- Member
- Registered: 2004-03-18
- Posts: 458
Re: Feedback to: Textpattern CMS 4.2.0 Release Candidate: Help us test!
I’m really sorry, Robert, I’m thinking I’m making a mistake here but I don’t know what it could be.
This is what I did:
- select the user
- select delete user
- click go
- message appears
- user is not deleted
- no other form appears
I don’t know. It’s probably caused by my upgraded version. I don’t know what to say, except for I should try a fresh install.
If you’d like to try my RC install, I’ll gladly register you as a user.
Last edited by Neko (2009-08-01 22:31:33)
Offline
Re: Feedback to: Textpattern CMS 4.2.0 Release Candidate: Help us test!
johnstephens wrote:
What’s the correct way to deal with Textpattern’s
textpattern/setupdirectory if you’re using multiple sites? If you delete it, you can’t install additional sites, but if you keep it around, couldn’t someone exploit that?
The recommended approach (per the instructions in the README.txt), is to set up a separate virtual host for each site, making the textpattern folder inaccessible (because it will lie outside of the web root).
Offline
Re: Feedback to: Textpattern CMS 4.2.0 Release Candidate: Help us test!
artagesw wrote:
The recommended approach (per the instructions in the README.txt), is to set up a separate virtual host for each site, making the textpattern folder inaccessible (because it will lie outside of the web root).
Thanks, Sam. I don’t have httpd.conf access at my hosting provider, and I can’t place my textpattern directory outside the web root because php only executes in my html directory. I do have shell access, in addition to unlimited subdomains and symlinks, so I got the rest working (let me know if you need instructions for this, in case you want to provide such alternatives in the README).
It’s unlikely that anyone will ever find my textpattern directory on that server, but the setup directory is accessible for anyone who can figure out the path. I imagine the best solution is to delete it and use svn co to grab it whenever I set up a new directory under sites.
Offline
Re: Feedback to: Textpattern CMS 4.2.0 Release Candidate: Help us test!
johnstephens wrote:
I imagine the best solution is to delete it and use
svn coto grab it whenever I set up a new directory under sites.
Yes, that would be the safest approach. Another alternative would be to restrict access to the textpattern directory via .htaccess. Something like the following (untested):
Order allow,deny
Deny from allOffline
Re: Feedback to: Textpattern CMS 4.2.0 Release Candidate: Help us test!
artagesw wrote:
Order allow,deny
Deny from all
Perfect, thanks!
Offline