Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
Re: Help us test release candidate 2 (!) for the upcoming 4.0.8 release
Here i upped my topic with case-sensetive search. Any chance to solve this?
Providing help in hacking ATM! Come to courses and don’t forget to bring us notebook and hammer! What for notebook? What a kind of hacker you are without notebok?
Offline
#62 2009-01-21 01:23:26
- rsilletti
- Moderator
- From: Spokane WA
- Registered: 2004-04-28
- Posts: 707
Re: Help us test release candidate 2 (!) for the upcoming 4.0.8 release
I’m getting a consistent notice when I try to save CSS in the editor, rather than raw CSS, side as follows:
Notice: Undefined variable: selector in /users/home/—/web/public/textpattern/include/txp_css.php on line 275
I rarely use this – sorry so late with it.
Textpattern version: 4.0.7 (r3074)
Last Update: 2009-01-18 21:47:21/2009-01-18 21:30:56
Document root: /users/home/**/web/public
$path_to_site: /users/home/**/web/public
Textpattern path: /users/home/**/web/public/textpattern
Permanent link mode: section_id_title
upload_tmp_dir: /usr/local/www/php/tmp
Temporary directory path: /users/home/**/web/public/textpattern/tmp
Site URL: **
PHP version: 5.1.4
GD Image Library: bundled (2.0.28 compatible); supported formats: GIF, JPG, PNG.
Server Local Time: 2009-01-21 01:14:53
MySQL: 4.1.22-log
Locale: en_GB.UTF-8
Server: Apache
PHP Server API: cgi-fcgi
RFC 2616 headers:
Server OS: FreeBSD 6.2-STABLE
Active plugins: ras_author_list-4.0.8.dev, ras_page_of-4.0.7, smd_calendar-0.33, ras_plugin_credits-4.0.7
Pre-flight check:
————————————
You are running in-development files on a live server:
/users/home/**/web/public/textpattern/include/txp_category.php,
/users/home/**/web/public/textpattern/include/txp_section.php
————————————
.htaccess file contents:
————————————
#DirectoryIndex index.php index.html
#Options +FollowSymLinks
#Options -Indexes
<IfModule mod_rewrite.c> RewriteEngine On #RewriteBase /relative/web/path/
RewriteCond %{REQUEST_FILENAME} -f [OR] RewriteCond %{REQUEST_FILENAME} -d RewriteRule ^(.+) – [PT,L]
RewriteCond %{REQUEST_URI} !=/favicon.ico RewriteRule ^(.*) index.php
RewriteCond %{HTTP:Authorization} !^$
RewriteRule .* – [E=REMOTE_USER:%{HTTP:Authorization}]
</IfModule>
#php_value register_globals 0
————————————
Offline
Offline
#64 2009-01-21 03:58:56
- rsilletti
- Moderator
- From: Spokane WA
- Registered: 2004-04-28
- Posts: 707
Re: Help us test release candidate 2 (!) for the upcoming 4.0.8 release
no – actually I saved them on the raw side then tried to resave them in the editor. I use it occasionally to clean up the appearance of the file.
Offline
Re: Help us test release candidate 2 (!) for the upcoming 4.0.8 release
rsilletti wrote:
I’m getting a consistent notice when I try to save CSS in the editor, rather than raw CSS, side
Confirmed. Interesting factoid of the day: I have never ever used the “cooked” CSS editor. Will look into it.
Offline
Re: Help us test release candidate 2 (!) for the upcoming 4.0.8 release
Rick, is there any reason for using that CSS editor?
(I’ve used it once to see what it was and then found that it totally wrecked my stylesheet which at that point contained a lot of hacks).
Offline
Re: Help us test release candidate 2 (!) for the upcoming 4.0.8 release
rsilletti wrote:
I’m getting a consistent notice when I try to save CSS in the editor, rather than raw CSS, side as follows:
Notice: Undefined variable: selector in /users/home/—/web/public/textpattern/include/txp_css.php on line 275
Fixed in r3079.
Offline
#68 2009-01-21 17:58:23
- els
- Moderator
- From: The Netherlands
- Registered: 2004-06-06
- Posts: 7,458
Re: Help us test release candidate 2 (!) for the upcoming 4.0.8 release
ruud wrote:
Rick, is there any reason for using that CSS editor?
I’m not Rick, but I don’t see any reason at all. I doubt if anyone ever uses it. My guess is that most people who want to keep their css tidy use their own preferred editor.
Offline
Re: Help us test release candidate 2 (!) for the upcoming 4.0.8 release
Not saying that the CSS editor (aka “Automatic mode”) should be removed from Textpattern guts, but at least, it could be removed as a “cool” feature from Textpattern homepage, as suggested by this maniqui.
Offline
Re: Help us test release candidate 2 (!) for the upcoming 4.0.8 release
I certainly wouldn’t object to removing the CSS editor.
Offline
Re: Help us test release candidate 2 (!) for the upcoming 4.0.8 release
Go for it. Damn thing is a PITA on a new client’s site if they decide they want to mess about. If you have commented-out lines as I usually do for title blocks to split the CSS up, damn thing wipes them out. Any commented-out line will do which is why some CSS “hacks” get wiped out too.
Burn the damn thing!
Stuart
In a Time of Universal Deceit
Telling the Truth is Revolutionary.
Offline
#72 2009-01-21 23:40:23
- cocogum
- New Member
- From: Sydney, Australia
- Registered: 2009-01-17
- Posts: 3
Re: Help us test release candidate 2 (!) for the upcoming 4.0.8 release
Indeed, lets nuke the CSS editor!
Offline