Neues “nightly” neues .mo. The usual.
die 80% Hürde ist allerdings immer noch nicht durchbrochen, so bleibt auch diesmal u.a. der Link Manager komplett in Englisch. Bei Gelegenheit werde ich da wohl selbst Hand anlegen müssen an den php Dateien…
Aktuelle (30-06-2004) .po und .mo Dateien gibt’s wie immer hier.
Please read carefully.
Once a user has level4 he/she can post native php code in the template files…
Security concerns anyone?
Any user ever tried adding
echo $passsql
to your index.php?
wp-config.php vars are “global”…
until this security flaw is fixed I am afraid users beyond level 4 are right out of the question. I am sure admins with some basic security understanding will agree here.
WP as it is now is a SINGLE user system, with a majorly flawed user and templating system that is far too exploitable and insecure to warrant allowing multiple users at level4+
if you are running WP for yourself this will not concern you. If you want a community to use WP and it’s user level system you really need to be VERY careful about whom to promote to level 4 and beyond.
While I have not searched the boards or WIKI for specific warnings about this I felt I had to post it here, nonetheless.
This is meant as constructive feedback and please do not read anything else into it. WP has some severe security flaws which need to be attended to, esp. in the light of future mulituser ability.
Schon lange überfällig, gibt es nun einen BugTracker (Mantis) für WordPress! Alle die WordPress nutzen, sind herzlich eingeladen einen BugTracker Account zu eröffnen und gefundene Bugs, Bedienschwächen oder Feature Anfragen in den BugTacker einzugeben.
Unter http://mosquito.wordpress.org/ geht’s direkt zur Mosquito Klatsche.
Death to all bugs!
Just came back from Snowboarding in Hintertux. Much fun.
Course the WP homepage is one of the first to visit. I installed the latest nightly and got the following error:
Database error: [Unknown column 'autoload' in 'where clause']
SELECT option_name, option_value FROM wp_options WHERE autoload = 'yes'
on re-running the upgrade.php script the error vanished.
more testing will follow…
—
Die .po und .mo Files sind nun auf Stand 13-06-2004, der Felher ist behoben ;-)