Entries tagged as dotclear2
|
September '10 | |||||
| Mon | Tue | Wed | Thu | Fri | Sat | Sun |
| 1 | 2 | 3 | 4 | 5 | ||
| 6 | 7 | 8 | 9 | 10 | 11 | 12 |
| 13 | 14 | 15 | 16 | 17 | 18 | 19 |
| 20 | 21 | 22 | 23 | 24 | 25 | 26 |
| 27 | 28 | 29 | 30 | |||
5.2.0
5.2.7
antispam
apache2
bavaria
binary
cartoon
cgi
conference
Dotclear
dotclear2
fastcgi
feed
filter
filters
GD
google
graphics
htaccess
htscanner
iis
innotek
internals
ipc
ISP
libGD
lighttpd
munich
Mysql
PEAR
PECL
PHP
PHP-core
php 5.2.7
png
qa
release
security
Sun
symfony
testfest
tutorial
virtualbox
virtualization
visual-C
win32
windows
wtf
zip
ziparchive
Posted by Pierre in
Uncategorized
Saturday, March 24. 2007
The comments are finally working again. After a little bug in the dotclear2, I forgot to remove the old antispam system. All comments were marked as spam. Everything should work well now. Back to a free talk mode ![]()
Posted by Pierre in
PHP
Friday, December 29. 2006
It is a small addition but really useful. If you already use dotclear2, you may have missed the new feeds options (see the URL handlers code). It is now possible to create a feed for a given tag. For example, my PECL related entries can be fetched from:
http://blog.thepimp.net/index.php/feed/tag/PECL/rss2
By the way,the beta4 is out, go fetch it!
Posted by Pierre in
Uncategorized
Monday, December 4. 2006
Loosing his old URLs is not always a good thing and not only for the ranking in google. I got a couple of requests to restore them, here you go, old post URLs are back.
Here is the lighttpd rewrite rules for the old rss.php file and the post access, if anyone needs it (not really rocket sciences, but copy/paste can be faster
:
url.rewrite-once = ( "^/rss\.php" => "/index.php/feed/rss2", "^/index\.php/([0-9]{4}.*)" => "/index.php/post/$1" ) Update You can find further rules for apache’s mod_rewrite in the dotclear’s forum. If you need some of them for lighttpd, let me know, I can try to "port" them (I’m happy with the two rules above).
Posted by Pierre in
Uncategorized
Tuesday, November 28. 2006
During my upgrade to dotclear2, I noticed some notices about ""Indirect modification of overloaded property" and thought they are minor (notices…) and can be somehow ignored, bad idea ![]()
It seems that the known issues with setter/getters with array are more serious than I thought, being not really a fan of these magic methods, especially not for arrays or other non scalar data, I did not really "care", selber schuld ![]()
In the case of dotclear, the workaround is relatively easy:
<br /> class context<br /> { public $stack = array();</p> public function __set($name,$var) { $this->stack[$name] = $var; } public function __get($name) { if (!isset($this->stack[$name])) { return null; } return $this->stack[$name]; } } <p>$ctx = new context;<br /> $ctx->comment_preview = array();<br /> $ctx->comment_preview[‘content’] = ‘’;<br /> $ctx->comment_preview[‘rawcontent’] = ‘’;<br /> $ctx->comment_preview[‘name’] = ‘’;<br /> $ctx->comment_preview[‘mail’] = ‘’;<br /> $ctx->comment_preview[‘site’] = ‘’;<br /> $ctx->comment_preview[‘preview’] = false;<br /> $ctx->comment_preview[‘remember’] = false;<br /> var_dump($ctx);</p> <p>$comment_preview = array();<br /> $comment_preview[‘content’] = ‘’;<br /> $comment_preview[‘rawcontent’] = ‘’;<br /> $comment_preview[‘name’] = ‘’;<br /> $comment_preview[‘mail’] = ‘’;<br /> $comment_preview[‘site’] = ‘’;<br /> $comment_preview[‘preview’] = false;<br /> $comment_preview[‘remember’] = false;<br /> $ctx->comment_preview = $comment_preview;<br /> var_dump($ctx);<br />
The first initialiation will raise notices and fails (do not assign anything, as the error message says), the second works like a charm. This bug just confirms what I think about all these magic methods, don’t use them for non scalar unless someone put a gun on you.
The issue is known (thanks tony for the info). It is certainly due to the read/write access required by the array element change, but I do not know exactly how userland getter/setter work. I reopen an old bug (#36214), let see what will come out of it.