Deutsch:
Dies ist die Download-Seite für den auf Bryan Palmers großartigem BDPRSS Aggregator basierenden Parteibuch Aggregator. Auf dieser Seite wird es immer die aktuellste Version zum Download geben, sowie Links zu weitere Ressourcen von Mein Parteibuch, sobald sie verfügbar sind.Parteibuch Aggregator v. 0.2 zum Download
Installationsvoraussetzungen:
- Wordpress - getestet auf Version 2.1 - vermutlich tut es eine ältere Version aber auch, der BDPRSS Aggregator läuft bei mir auch auf Wordpress 1.5
- php mit Multibyte String Unterstützung
English:
This is the Download Page for the Parteibuch Aggregator, which is based on Bryan Palmers great BDPRSS Aggregator. At this page you will find always the latest download packages, links and updates provided by Mein Parteibuch.Parteibuch Aggregator v. 0.2 for Download
Installation prerequisites:
- Wordpress - version 2.x prefered - but probably lower version works as well, tried basics also on Wordpress 1.5
- php with support of multibyte strings
 |
| Persönlichkeitsrecht |
 2006 Lurusa Gross |
Par·tei·buch n. Heft mit persönlichen Daten und Mitgliedsnummer zum Beweis der Mitgliedschaft in einer Partei
[20 queries. 3.712 seconds. 8 level2 caches. Top ]
I installed it and followed your directions but all I get is “Cheatin’ uh?”
I’m running wordpress version 2.1 on my Hostgator shared hosting account
If a solution is available, can you please send me email?
The plugin is preconfigured in a way, that you need at least user level 6. The easiest way to get around this security feature is to log in to your wordpres installation as user admin.
It is possible to see the “Cheatin’ uh?” message even if you are logged in as administrative user. If you install your WordPress fresh, you get a preconfigured “admin” account, but that account isn’t assoiciated with any user level. That’s the reason why some skripts, which checks the user level (and not the newer concept of the user’s role) may fail in a mysterious way. This scripts gets a user level of “0″, which is not allowed to execute them. (A few months ago, I searched two hours in the WP 2.2 sources to find this bug.)
But there is a simple workaround for this issue. Log in as “admin” and create a user with administrative privileges, and use this user account to configure your feed aggregator. The user level is created as it should be and everything works fine.