Help us test release candidate 2 (!) for the upcoming 4.0.8 release

garnold · 2009-01-18 07:08:40

Request for 4.0.8: instead of requiring the user to specify the path to the TXP directory in config.php, why not use the __FILE__ constant to automatically determine the path:

$txpcfg['txpath'] = dirname(__FILE__);

saccade · 2009-01-18 10:39:46

I only just stumbled upon this thread (really didn’t notice before, mind kept on other places, sorry).

My most important need (i didn’t have time to test it now):
Did you also solve the DST-problem ? This would be a huge relief! It’s a base for all calendar like installations where someone cannot adjust server time by him/herself (that is in fact all shared server hostings).

If not: Is there any chance to get it in yet?

ruud · 2009-01-18 11:34:37

garnold, try removing txpath from config.php… you should find that TXP works fine without it, because we’re using dirname(FILE) internally already.

micheal, the DST problem isn’t fixed, unfortunately. It’s not a trivial problem so there was no time to do that properly in 4.0.8. Since we’re in RC2 (or for that matter RC1) it is way too late to change something that invasive at this point.

fdsafdsa · 2009-01-18 13:18:13

i upload stuff on,my txp still 4.0.7.

——————————————————————-

after upload, refresh pages on opera,there will be a blank lasting 1 second,then display the correct page, but it seems usual in IE.
i’m upload back to 4.0.7 then test it.

———————————————————————————-

OK,that’s not concerned 4.0.7 or 4.0.8; it’s because read CSS from database i think. after i change <link rel=“stylesheet” href=”<txp:css />” type=“text/css” media=“screen” /> to <link rel=“stylesheet” type=“text/css” href=“http://iblog.org.ru/style.css” />, the short blank disppear.
i’m now uploading 4.0.8 rc2 again.

Last edited by fdsafdsa (2009-01-18 13:41:19)

els · 2009-01-18 13:28:11

fdsafdsa wrote:

i upload stuff on,my txp still 4.0.7.

wet wrote:

The download advertises itself as 4.0.7 (r…) in diagnostics, because we haven’t yet bumped the version number.

beztak · 2009-01-18 14:01:59

I would like to ask how to help with TXP translation? Because since 4.0.7 there are several messages in CZECH they are not translated (mainly in select boxes so noboby knows what it does) and in 4.0.8 the count is growing. It seems nobody is updating czech translation. If I can, I would like to help.

wet · 2009-01-18 14:34:47

beztak wrote:

If I can, I would like to help.

If you’d like to act as one of the Czech translators, send me a forum e-mail containing the e-mail address you’d like to use for that prupose, and I’ll establish an account on the translation server.

garnold · 2009-01-18 15:10:56

ruud wrote:

garnold, try removing txpath from config.php… you should find that TXP works fine without it, because we’re using dirname(FILE) internally already.

Thanks ruud, I took a look through the source and see that it is no longer used. Maybe it should be completely removed from the config-dist.php to avoid confusion?

Krifitze · 2009-01-18 18:06:22

Sorry for bolting in, I don’t know whether it was already mentioned.
While working with Textpattern 4.0.7 I used a very dark Desktop theme and my standard font for forms was white.
In the 4.0.7’s textpattern.css the background-color for every form was set to white but the font color was not set. So I had to change it by myself, otherwise I could not see anything I wrote.

The textpattern.css of 4.0.8 RC2 seems to be the same, so I suggest adding “color: black;” to any form element.
I do not use the same theme any more and I do not have the time to check the whole css file; If this is already fixed, nevermind.

Markus

TheEric · 2009-01-18 19:23:08

Any chance of this making it into 4.0.8 ?

ruud · 2009-01-18 20:54:29

Nope. that will have to wait for 4.0.9.
Ideally we don’t change a single thing between this RC and the final 4.0.8.

TheEric · 2009-01-19 19:02:20

Very well, I’ll continue with this ugly piece of code then :

$(“#list td:first img”).attr(‘id’,‘mainImg’);

Textpattern CMS

Textpattern CMS support forum

#49 2009-01-18 07:08:40

Re: Help us test release candidate 2 (!) for the upcoming 4.0.8 release

#50 2009-01-18 10:39:46

Re: Help us test release candidate 2 (!) for the upcoming 4.0.8 release

#51 2009-01-18 11:34:37

Re: Help us test release candidate 2 (!) for the upcoming 4.0.8 release

#52 2009-01-18 13:18:13

Re: Help us test release candidate 2 (!) for the upcoming 4.0.8 release

#53 2009-01-18 13:28:11

Re: Help us test release candidate 2 (!) for the upcoming 4.0.8 release

#54 2009-01-18 14:01:59

Re: Help us test release candidate 2 (!) for the upcoming 4.0.8 release

#55 2009-01-18 14:34:47

Re: Help us test release candidate 2 (!) for the upcoming 4.0.8 release

#56 2009-01-18 15:10:56

Re: Help us test release candidate 2 (!) for the upcoming 4.0.8 release

#57 2009-01-18 18:06:22

Re: Help us test release candidate 2 (!) for the upcoming 4.0.8 release

#58 2009-01-18 19:23:08

Re: Help us test release candidate 2 (!) for the upcoming 4.0.8 release

#59 2009-01-18 20:54:29

Re: Help us test release candidate 2 (!) for the upcoming 4.0.8 release

#60 2009-01-19 19:02:20

Re: Help us test release candidate 2 (!) for the upcoming 4.0.8 release

Board footer