Blog returned invalid data

  1. Hello to all!

    I just updated my Wordpress app on Appstore to 2.7 version. Since updating i can not able to log in to my self hosted wordpress page with this application.

    It says: Sorry, can't log in,blog returned invalid data

    Username, url address and password are correct i just checked each of them.
    XML-RPC setting on my Wordpress admin is enabled!


  2. This plugin generates automatically photo galleries with thumbnails and easy recursive navigation links, the photos can be viewed in several sizes, wi

    This plugin generates automatically photo galleries with thumbnails and easy recursive navigation links, the photos can be viewed in several sizes, with an easy configuration panel.

  3. Having the same problem exactly - response from Wordpress was to "enter the password"!! Must have been an auto response as that's clearly not the problem

    It might be something to do with The following - wordpress claims this can cause the response we're getting. They have a validator for your site on their FAQ. However, they offer no advice on how to resolve - and don't explain why this is an issue in the updated app when it wasn't previously! Anyone?!

    Byte-Order Mark found in UTF-8 File.

    The Unicode Byte-Order Mark (BOM) in UTF-8 encoded files is known to cause problems for some text editors and older browsers. You may want to consider avoiding its use until it is better supported.

  4. Probably you have modified wp-config,php with an editor that insert the BOM at the begin of that file.
    Open that file with an open source editor such as could find the detailed istructions to clean up the files on support forum. (just use the search field with the word "bom" or "bom wordpress").

  5. Right, so we cracked it. Or rather Lartens our super web master cracked it.

    The full answer to this is at:

    Which is a lovely, working, wordpress blog now!

  6. Ps just to be clear - the app now picks up my blog whereas before it was just giving me the invalid data error. All working now! The site itself didn't seem to have any actual problems - for the ref of wordpress, still not sure why update caused this to trip up?!

  7. I did this with my wp-config.php but i still get the error "blog returned invalid data".

    I also deleted wp-config.php and went to my site to regenerate wp-config.php but I'm still getting this error message.

    Any suggestions ?

  8. Okay, works for me too. I did the following:

    - Save a copy of your wp-config php file.

    - open it with notepad ++

    - There's Format menu tab (Or coding) Choose Encode in Ansi. Then go to format again and select UTF8

    Save your file and upload to your server.

    That's all

  9. .................... sorry you have to choose UTF8 WITHOUT BOM

    And save and upload to server

  10. I've tried this with Notepad++ and it doesn't fix the problem.

  11. ok I've had a little success. I have 2 Wordpress accounts. 1 is an Administrator account that I use for installing plugins, approving comments etc and a 2nd account that has the role of editor. I can log into the Wordpress app with the administrator account but not the editor account.

    Anyone know how I can fix this ?

  12. @Towlieban - It may help to create a new user as editor and try again.

  13. Jose Diaz-Gonzalez
    Feb 21, 2008, 1:52 AM

    Changes the visual design of the Wordpress administration area to the "Black" theme.

    Black Style Administration is based upon Barunio Style Administration with a couple of additions and corrections for the latest Wordpress release (currently 2.3.2). As such, many of the images are kinda funky looking (I did not edit them other than changing colors here and there). I’ve changed almost all the colors, but a few still elude me. If you find one, let me know and the release will be updated.

    I am aware of a few rendering issues, most notably concerning images in the “Create New Post/Page” section and “Add Link” section. I’m kinda burnt out from screwing with some other issues with the Barunio Theme, so I can’t work on them at the moment, but again, if anyone has a solution, shoot me an email about it and I will update the release.

    Compatible with Firefox 2.0 and Opera 9 under Linux.

    Black Style Administration is released under the GNU Public License Version 2.

    1. Backup your upload.css file from /wp-admin/css/upload.css to a safe directory
    2. Unpack this archive to your Wordpress install directory
    3. Go to the WordPress Amin Panel and select Plugins.
    4. Activate 'Black Style Administration'

    This does not work in Browser X

    Send me the complete details on the Browser, Wordpress Install, and Operating System and I will do some testing/debugging to correct any errors.

    Admin Plugin Y does not appear correctly

    Email the version of the plugin you are using, your Wordpress install and Browser for testing purposes. It may just be that the CSS for your plugin is not currently supported.


    Confirmed Usable Plugins: 1. SuperEditor 1. RSS Stream version .2

    Notable Errors: I am aware of css issues in Firefox and Opera concerning some images which should be there but are not. Also, many plugins that rely on the default color being dark might be broken. If there are any that need to be fixed, shoot me an email about the Install you are using and plugin information so I can send out a bugfix.


    • Usable in

    • Opera 9@Linux (Some CSS image issues)

    • Firefox 2.0.11@Linux (Rendering Issues with Adding Blogroll links and some posting Options)

    • Untested

    • IE5/6/7

    • Konqueror
    • Safari 3

    • Probably Broken

    • Dillo

    • lynx


    Thanks to: Barun Singh for the base Barunio Style Administration @

  14. ardiansyahputra
    Feb 21, 2008, 5:44 AM


  15. I've done all that's been outlined above but to no avail.

    Does anyone have any other ideas or guidance on how to fix this? Really miss being able to update remotely.


  16. did you download the latest app version (2.7.2)?
    could you please send us the URL of your blog?

  17. WP Status Notifier will send a notification to given email address(es) of posts pending review by contributors.

    WP Status Notifier will send a notification to given email address(es) of posts pending review by contributors. It can also optionally notify the contributors when their post is accepted or rejected. WP Status Notifier is useful for moderation in blogs with multiple contributors.

    The plugin will add an options page in the Wordpress administration area where you can set one or more email addresses to notified of posts pending review.


    1. No need to manually check posts waiting for approval.
    2. Includes a link to edit and/or approve the post in the notification email.
    3. Optionally notifies contributors of the moderation status.
    4. The plugin requires no database access and adds almost zero overhead.
    5. Simple configuration options. Doesn't require editing any .php files.
    1. Upload status-notifier.php to the /wp-content/plugins/ directory
    2. Activate the plugin through the 'Plugins' menu in WordPress
    3. To configure the plugin go to Options>Status Notifications in the Wordpress administration area

    Can you add a feature X?

    Depends, if its useful enough and I have time for it.

    1. wp-status-notifier screenshot 1

      Status notification options


    • Fixed duplicate notifications when posts already submitted for review are saved again (Thanks Keith).
    • Tested upto Wordpress 2.8.4
  18. An easy way to creates the code for multiple collapsible elements in a page or post with it's own administration page.

    This plugin adds a button to code editor and creates the code for having multiple collapsible elements in a page or post.

    So have fun and keep blogging!

    1. Decompress and upload the folder collapsible-elements to the /wp-content/plugins/ directory.
    2. Activate the plugin through the Plugins menu in WordPress.
    3. RIGHT AFTER activation go under Manage and find XCollapse Options page, choose a default container and a style.
    4. To create the collapsible element code use the CODE editor and press XCollapse button.

    Visit the plugin page:

    Visit the plugin page:

    Visit the plugin page:

    Version and Info

    Plugin Name: Collapsible Elements Plugin URI: Version: 2.2 Author: ..::DeUCeD::.. Author URI:


    1. Deactivate the plugin through the Plugins menu in WordPress.
    2. Delete the folder collapsible-elements from your /wp-content/plugins/ directory.
    3. Decompress and upload the new folder collapsible-elements to the /wp-content/plugins/ directory.
    4. Activate the plugin through the Plugins menu in WordPress.
    5. RIGHT AFTER activation go under Manage and find XCollapse Options page, choose a default container and a style.


    1. Deactivate the plugin through the Plugins menu in WordPress.
    2. Delete the folder collapsible-elements from your /wp-content/plugins/ directory.
    3. Remember that all collapsible elements will now remain hidden till you change the display: none attribute of container’s style.


    The Javascript is based on Arvind Satyanarayan example which toggles the visibility of multiple elements on a page, see it at


    This plugin is tested in my installation only. That means you must better test it before you use it even though it doesn't seem to interfere with other plugins. As far as i know it is compatible with all the plugins i use and you could check mines at my plugins page. But i recommend that you deactivate any plugins that do a similar job aiming the same purpose. As we all know, BACKUP AND TRY IT BEFORE YOU USE IT! You are the only responsible person for your DATA.

    Copyright 2008 ..::DeUCeD::..

    This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version.

    This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

    You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA

  19. This is strange since they were working right up to my last update of the app.

  20. This sidebar widget displays photos from the Flickr database.

    This sidebar widget displays photos from the Flickr database. You can define tags you want the images from and you can set how many photos will be displayed.

    This section describes how to install the plugin and get it working.

    1. Upload microFlickrAlbum.php to the /wp-content/plugins/ directory
    2. Activate the plugin through the 'Plugins' menu in WordPress
    3. On the Widget panel drag and drop Micro Flickr Album to your sidebar
    4. Setup title, tags and number of images
    5. Enjoy.
  21. Automatically post commit messages from your public Subversion repository.

    This is a very simple and straightforward plugin to let you automatically blog the commit messages from your public Subversion repository. For now, only one project is supported.

    Currently, it requires that PHP have shell access to the "svn" command. This means that it has to run on a *nix server with subversion installed. If you're not sure whether your server supports this, try typing "svn info" at your shell. If it says that it cannot find the program "svn", you don't have it installed.

    Simply drop the files into a folder in your WordPress plugins folder. Once you've activated the plugin, go to Settings -> WP-Subversion in your WordPress admin panel and set up your project.

  22. @daniloercoli - Thanks so much for your quick response. I used the w3c validater earlier today and my site passed with no errors against doctype XHTML 1.0 Transitional. I did add a new plugin tonight which appears to have a few errors that I can fix swiftly (ampersand issues).

    My question is, which doctype is your app relying on when reading my site? Though it tested as perfect in XHTML 1.0 Transitional, when I then tested my site against different doctypes (html4.01 and html5), it showed errors.

    Knowing which doctype to conform to would likely help me resolve this issue. Thanks for your help on this.

  23. @phinx -- The mobile app communicates with your blog using the XML-RPC endpoint.
    You should check the XML-RPC endpoint of your blog using an xml-rpc debugger. As a first check, you can only ping the URL of the XML-RPC endpoint at in your browser.

  24. WP-SocialCount displays the number of adds/saves from within a social network for any particular URL.

    WP-SocialCount is a Wordpress plugin that displays the number of adds/saves from within a social network for any particular URL. Since this plugin allows you to specify the URL that you want to pull the data for, it means that you can display any social number for any URL of your choosing. We also attach no style to the data the plugin returns - so you are free to style and use the data in any way you see fit. Supported so far: Digg, YouTube and

    1. Upload wpsocialcount.php to the /wp-content/plugins/ directory
    2. Activate the plugin through the 'Plugins' menu in WordPress
    3. Syntax of code to be placed within your template tags <?php wpsocialcount('social-network', 'data-format', 'url'); ?>

    Full and updated list of instructions are available at

  25. Hello All,

    I'm having the same error with my site. XML-rpc is ok. I don't have my site in the root it's actaully one folder deep. Would that make a difference?

    Any help is appreciated.


  26. Keep track of your comments on other sites using the cLog API.

    Comment Log (or clog) is a plugin that allows you to store a copy of a comment you make on another site. This is done through implementing the RESTTA-based cLog API. As long as the remote site supports the API, you can keep track of any comments you make. This plugin also allows those that comment on your blog to keep track of their comments. The full details about the cLog spec can be found HERE

    1. Upload comment-log directory to the /wp-content/plugins/ directory
    2. Activate the plugin through the 'Plugins' menu in WordPress
    3. Edit the restta.xml file in the commentlog directory if your wp installation is in a directory (e.g. Edit the pathPrefix element to surround the path (e.g. /wp)
    4. Move the restta.xml file to the document root. If there already exists a restta.xml file, do not delete it. Open the existing file and merge the appClass tag (along with its contents) in the original file with the other appClass tags in the already-existing file.

    Where do I send my inquiries?

    Please contact me at roamzero[at]

    1. comment-log screenshot 1

      The comment log as it appears on a page.

    2. comment-log screenshot 2

      Confirming a comment you made on another site.

    3. comment-log screenshot 3

      Button added to allow others to log their comments.

    4. comment-log screenshot 4

      Comment log administration screen.

    Version Log

    • 1.2 : Fixed a major bug, it should actually work properly now for the handful of people that use it :D

    • 1.1 : Minor updates, you can select the page to display the comment log on from a dropdown now, and confirmed it working with 2.5

    • 1.0 : Initial version.

  27. Add Google AJAX Translation to your blog. This plugin allows your readers to translate your blog posts, pages, or comments into 52 languages.

    The Google AJAX Translation WordPress plugin provides a quick, simple, and light way to add translation to your blog.

    A "Translate" button can be added to the bottom or top of posts, pages, and/or comments. When the button is clicked a popup window opens showing a list of available languages.

    You can choose which of the 52 languages to display in the Administration Panel. The list of languages can be shown as text (in the native language of each language), as flag icons, or as both. Flag icons can be confusing and sometimes misleading so I recommend the text option. (See this google search for language flags.)

    The plugin detects the browser's preferred language and shows the "Translate" button in that language if available. That language is listed first in the popup. The tooltip for each language is also translated into the browser's preferred language. If the browser's preferred language isn't English a "Translate" button is shown on the Administration Panel that translates the panel. See this page for more information about setting your browser's preferred language.

    Clicking the "powered by Google" link will take you to a full-page Google translation in your browser's preferred language.

    Related Links:

    1. Download the plugin archive and expand it if you haven't already.
    2. Put the google-ajax-translation folder into your wp-content/plugins/ directory.
    3. Go to the Plugins page in your Administration Panel and click "Activate" for Google AJAX Translation.
    4. Change the settings from Setting -> Google Translation.
    5. Have fun with your blog readers.

    Operation and Customizing

    • Google Ajax Translation automatically detects your source language. If your source text changes to more than one language it can get confused.
    • Clicking the "powered by Google" link will take you to a full-page Google translation in your browser's preferred language. (This service will refuse to translate a page into the same language though, e.g. English to English.)
    • If your theme doesn't have a unique id for each post the plugin will fall back to translating just the content of the post but not the title, date, author, tags, etc. Try the plugin with the default theme (Kubrick) to see how it should work. If you need help modifying your theme just ask in the forums.
    • The CSS background-color of the popup can be specified in the format #5AF or #55AAFF or it can be copied from the body of the page.
    • To exclude certain posts and pages from displaying the "Translate" button put the post and page ID numbers into the field marked "Exclude posts and pages", for example 4, 5, 21. If you use permalinks you may not know your post and page ID's. The post or page ID is the number at the end of the URL when editing a post or page.
    • To exclude a section of a page from being translated enter a jQuery selector (which works just like a CSS selector) in the field marked "Do not translate". For example enter code to exclude the HTML code tag, enter .notranslate to exclude any element where class="notranslate", or enter code, .notranslate to exclude both. See this page for more information or ask any questions in the forums here.
    • Deleting the plugin from the Administration Panel (Plugins > Installed) also deletes the options from the wp_options table in the database.
    • Most formatting, font, color, etc. changes can be made in google-ajax-translation.css or you can override them with your own CSS file
    • The included ajax throbber is black on a white background. You can make your own at 16 by 16 pixels works best.


    • This plugin uses the Google AJAX Language API and the jquery-translate plugin.
    • The "[" and "]" characters in the "Translate" button can be changed in the variables $before_translate and $after_translate
    • The google-ajax-translation.js file is included for reference. It is minified and appended to the file jquery.translate-1.4.1.min.js
    • This plugin automatically uses the jQuery library supplied by your WordPress installation (version 1.3.2 as of April 2010). If your theme or another plugin has another copy of jQuery hard coded into it this plugin may not work.
    • This plugin places the popup and JavaScript into the footer with the wp_footer() function. If your theme doesn't have this function it will not work. See the footer.php file in the default theme to see what it should look like.
    • If you customize your theme you can position the "Translate" button anywhere within the WordPress loop as shown below:
    if( method_exists( $GoogleTranslation, 'google_ajax_translate_button' ) ) {
        $GoogleTranslation -> google_ajax_translate_button();
    1. google-ajax-translation screenshot 1

      Translate popup with languages displayed as text (Safari 4 on Windows XP)

    2. google-ajax-translation screenshot 2

      Translate popup with language flag icons (Firefox 3.5 on Windows XP)

    3. google-ajax-translation screenshot 3

      Translate popup with language flag icons and text (Safari 4 on Windows XP)

    0.6.0 (Nick Marshall)

    • Added a method to be used in custom themes google_ajax_translate_button() which allows the "Translate" button to be placed anywhere within the WordPress loop. (See the FAQ)
    • The "Translate" button position can now be set to "top", "bottom", or "none".
    • The "Exclude pages" field is now "Exclude posts and pages".
    • Added an option to exclude the home page (with the is_home() function).
    • Added an option to exclude a section of a page with a jQuery selector. (See the FAQ)
    • Added rel="nofollow" to the "powered by Google" link.
    • Added an Upgrade Notice section to the readme file.

    0.5.1 (Nick Marshall)

    • Portuguese translation works now. The Google AJAX Language API only accepts the language code "pt-PT", Portuguese from Portugal, rather than just "pt". (Thanks to kurteye for the bug report.)

    0.5.0 (Nick Marshall)

    • Nine new languages are supported by Google translate: Afrikaans, Belarusian, Icelandic, Irish, Macedonian, Malay, Swahili, Welsh, and Yiddish, bringing the total to 52.
    • Added an option to specify the CSS background-color in the format #5AF or #55AAFF.
    • Added an option to copy the CSS background-color from the body of the page. (Inherit for background-color doesn't work in IE6 and IE7.)
    • Added an option to display or hide the horizontal line above or below the [Translate] button. This line was always displayed before.
    • All the options are saved in the options database table as one row. Because of this settings will be have to be reset when you upgrade to this version.
    • If your theme doesn't have a unique id for each post the plugin will fall back to translating just the content of the post but not the title, date, author, tags, etc. Try the plugin with the default theme (Kubrick) to see how it should work.
    • If the popup goes off the right edge of the browser window it's moved to the left.
    • Updated the jquery-translate plugin to version 1.4.1

    0.4.9 (Nick Marshall)

    • Fixed bug where leaving the "Exclude pages" field blank would exclude all pages. Sorry again!

    0.4.8 (Nick Marshall)

    • Refixed the bug where the [Translate] button appears in the_excerpt if it's already 55 words or less. Sorry for the regression!

    0.4.7 (Nick Marshall)

    • Added an option to exclude certain pages from displaying the [Translate] button.
    • If the browser's preferred language isn't English a Translate button is shown on the Administration Panel that translates the panel.
    • Many tweaks to the Administration Panel
    • The list of languages should be left aligned for all themes. Some theme's footers are center aligned which caused the problem.
    • Fixed the Czech flag image (Thanks, maoric)

    0.4.6 (Nick Marshall)

    • The popup is now generated just once at the bottom of the html page and it gets moved around as needed with jQuery and JavaScript. This requires your theme to have the wp_footer() function. This speeds up page loading and improves keyword indexing by search engines. It seems like the popup works properly in Firefox 2 now.
    • Added an option to put the [Translate] button at the top or bottom of posts and pages.
    • Clicking the "powered by Google" link will take you to a full-page Google translation in your browser's preferred language. (This service will refuse to translate a page into the same language though, e.g. English to English.)
    • The future has arrived! The popup window has a simple CSS 3 shadow in browsers such as Firefox 3.5+ and Safari 3+.
    • The JavaScript loads in the footer instead of the head to speed up page loading. This requires your theme to have the wp_footer() function and WordPress 2.8+

    0.4.5 (Nick Marshall)

    • Updated the jquery-translate plugin to version 1.3.9 which fixes an issue with alignment of right-to-left languages.
    • Fixed a bug where the [Translate] button and languages appear in the_excerpt if it's already 55 words or less. The function get_the_excerpt uses the filter wp_trim_excerpt which uses the filter the_content. (Thanks to Eiland for pointing out this problem.)

    0.4.4 (Nick Marshall)

    • The Google language API added alpha support for Persian (Farsi) so Persian was added.

    0.4.3 (Nick Marshall)

    • Added "All" and "None" buttons to Administration Panel to check and uncheck all language boxes. (Suggested by Jørn Eichner.)
    • Added option to display flag icons with text.
    • The popup window formats the languages into a table so CSS3 isn't used any more. The columns should work in all popular browsers. (Firefox 2 doesn't work.)
    • Added sanitization callback functions for all register_setting options.
    • Deleting the plugin from the Administration Panel (Plugins > Installed) also deletes the options from the wp_options table.

    0.4.2 (Nick Marshall)

    • Corrected the Swedish flag image (Thanks, Jørn Eichner)
    • Added option to enable and disable page translation
    • Fixed bug with loading default settings
    • Changed options page to use register_setting function. The plugin requires WordPress version 2.7+

    0.4.1 (Nick Marshall)

    • Fixed php warning when plugin is first activated and default settings are ignored. (Thanks, Jørn Eichner)

    0.4.0 (Nick Marshall)

    • Added an option to enable and disable comment translation.
    • The "Translate" buttons appear only after the document is ready and if JavaScript is enabled.
    • Fixed the comment translation so that it's XHTML valid. (The problem was with the order of the default filter wpautop.)
    • Added all 42 languages currently available from
    • The list of languages appear in a popup window so they take up less space (42 languages is a lot!)
    • The languages are displayed in their own language.
    • If you hover over a language name the tooltip shows the language name in English.
    • The popup window is styled with its own external CSS from google-ajax-translation.css.
    • In Firefox the popup window is in three columns using CSS3. Safari doesn't quite format the columns correctly so I left that out.
    • Added the jQuery-translate plugin to access Google translate. This plugin allows you to get around the character limit of Google translate by breaking up the object into 1000 character strings.
    • The plugin detects the browser's preferred language. (See this page for instructions.)
    • The "Translate" buttons show up in the browser's preferred language if available.
    • The browser's preferred language is put first in the list of languages in the popup.
    • The first time the user clicks on a "Translate" button the tooltip language names are sent off to jQuery-translate and then inserted back into the tooltips so they can be displayed in all 42 languages also. So to the user the plugin is completely self-localized.
    • Added the rest of the flags so there are flag icons for all 42 languages. (These are from )
    • All the flag icons are assembled into one PNG file and displayed as CSS background images sprites, which reduces the number of HTTP requests.
    • Added an AJAX loading throbber image. Make your own at
    • JavaScript has been minified and moved to the end of jquery.translate-1.3.2.min.js. The non-minified source code is google-ajax-translation.js


    • fixed some html-bugs (missing alt-Tags, etc.) (Michael Klein)


    • encapsulate the plugin in a class. No global vars needed anymore, faster code (Michael Klein)
    • Better support of capabilities-model (WP 2.6)

    0.2.0 Thanks Michael Klein from for:

    • Add Flag ICONs link style
    • Add Flag ICONs

    Others changes:

    • Add Admin Configuration Page
    • Link Style: Text and Image
    • Enable/Disable Post Translation
    • Choose languages from the whole list

    0.1.1 Small updates:

    • Working on Admin/Comments pages too
    • Fixed the comment format problem found by Sean


    • Initial Release


    Have questions or suggestions for this plugin?

    Please ask in the forums here.

    1. Please start a new thread for your question, problem, or suggestion. Use the tag google-ajax-translation so that it shows up in the same list.
    2. Please include as much information as possible like: WordPress version, Google AJAX Translation version, a link to your web page
    3. Most problems seem to be theme related so check to see if the plugin works in the default theme (Kubrick).
  28. wp-greet sends greeting cards from your WordPress blog. It works with WordPress-, NextGen- or NextCellentGallery.

    wp-greet is a plugin for the famous WordPress blogging system, giving your users the ability to send greeting cards from your blog.


    • uses WordPress native gallery NextCellentGallery or NextGenGallery for maintainig the greeting card picture
    • storing statistics about the sent greeting cards
    • adding your own css
    • control who can send cards
    • add default subject, header and footer to the greeting cards
    • various settings for sending the mails (SMTP, SSL, PHPMail)
    • supports Antispam Plugins CaptCha! and Math-Comment-Spam-Protection-Plugin
    • sign your greeting cards with your own stamp
    • backgroundmusic for your cards
    • supports individual terms of usage
    • supports confirmation mail processing
    • supports fetching the card online or sent it by mail
    • can send cards in the future
    • WPML certified
    1. Upload to your plugins folder, usually wp-content/plugins/, keeping the directory structure intact (e.g. wp-greet.php should end up in wp-content/plugins/wp-greet/).

    2. Activate the plugin on the plugin screen.

    3. Visit the configuration page (Options -> wp-greet) to configure the plugin (do not forget to add the forms page id)

    4. Optional: If you would like to change the style, just edit wp-greet.css

    How can I make wp-greet work with NextgenGallery Version >= 2.0.0?

    Unfortunately Photocrati did a major redesign of NGG and therfore the connecting filters were removed. You can read about this redesign in the forums. But we can make it work by editing nextgen-gallery/products/photocrati_nextgen/modules/nextgen_basic_gallery/templates/thumbnails/index.php and change one line. from <a href="get_image_url($image))?>" to <a href="get_image_url($image)), $image)?>" You can also fetch the patched file (index.php) from the wp-greet/patch directory and copy it to nextgen-gallery/products/photocrati_nextgen/modules/nextgen_basic_gallery/templates/thumbnails

    If this seems to difficult try using the new interface to WordPress native gallery to embed your greetingcard pictures.

    My greetcard form is wider than my theme. What can I do?

    To adjust the design of your greetingcard page edit the file wp-greet.css. If you have a narrow theme you might adjust the width of the textarea textarea.wp-greet-form { width: 90%; } by replacing the 90% with something smaller than this.

    How can I use the Math Comment Spam Protection Plugin with wp-greet?

    Upload the unzipped directory "math-comment-spam-protection" on your webspace into wp-content/plugins and activate the plugin. Under Settings -> Math Comment Spam klick "Update Options" once even without having changed any options, otherwise the plugin won't work. You don't have to change the text of the error messages, as these are fixed within wp-greet.

    1. wp-greet screenshot 1

      Sending a greetingcard with wp-greet (shows the user interface for entering a greetingcard)

    2. wp-greet screenshot 2

      Preview a greetingcard with wp-greet

    3. wp-greet screenshot 3

      Admin-Dialog of wp-greet

    v5.1 (2016-08-13)

    • removed home path from stamp url for security reasons
    • add background music feature
    • updated readme.txt and plugin icons
    • removed inline default value for fixed image width and replaced it by a standard setting of 100%
    • added dkim support
    • added support for wp-greet-autotext extension
    • switched back link in form to back button
    • added support for selectable stamps (incl. BuddyPress Group Avatars)
    • extended database to store long image urls
    • fixed some PHP7 compatibility issues
    • removed some PHP warnings
    • added option to sen card as Blindcopy

    v5.0 (2015-12-23)

    • fixed thickbox terms of use URL to allow changing width and height in wpg-form.php
    • added several mail parameters to give users more control about mail addresses
    • separated admin dialog for mail settings
    • reordered admin dialog to make it (hopefully) easier to understand
    • added customizable message to be displayer after a confirmation mail has beent sent
    • fixed reschedule future cards thickbox dialog
    • fixed problem with single quotes in message and subject

    v4.9 (2015-12-17)

    • secured html input with wp_kses
    • fixed lost linebreaks using tinymce
    • made message to be displayed after a card has been sent customizable

    v4.8 (2015-12-12)

    • renamed form field title to wpgtitle to avoid collision with WP-Core title field in OEmbed code
    • added pre filled form for use with Premium Selling Cards Plugin
    • fixed problem with missing captcha plugin
    • clean up old dependency for bw-cards and NGG custom fields
    • turn terms of usage thickbox in an inline thickbox to improve security

    v4.7 (2015-03-07)

    • fixed handling of apostrophe in mail addresses
    • added reschedule feature to reorganize future cards
    • fixed static sender in mails other than card mail with attachment
    • adopted to wp-recaptcha >= 4.1
    • use client timezone for future send cards
    • fixed confirmation an cc to sender checkbox setting when send a card to another recipient
    • excluded wp-greet-formpage from homepage view
    • wp-greet.css will only be loaded if you are on a wp-greet form page
    • preset time in timepicker for futuresend
    • removed php notices about missing index
    • adjusted width of terms of usage thickbox

    v4.6 (2014-12-25)

    • fixed a problem with jetpack gallery extensions
    • fixed a bug with WP4 and future send
    • fixed future send problem

    v4.5 (2014-09-06)

    • added greek language thanks to George
    • added NGG/NCG description to mail if activated
    • fixed some typos
    • load javascript only on formspage where is it needed

    v4.4 (2014-07-28)

    • integrated SMTP parameters in to admin dialog
    • added support for SMTP SSL transfer

    v4.3 (2014-06-25)

    • improved compatibility with JetPack Carousel and Jetpack tiled gallery
    • fixed problem with html in link-mail
    • added first responsive approach to the form
    • adopted TinyMCE toolbar to API V4
    • work around WordPress bug 26649
    • added support for WPML
    • fixed html entitties in receiver/sender mail labels
    • new extended dutch translation (thanks to Danny)
    • new extended french translation (thanks to Madelaine)
    • load smilies javascript and css only in frontend
    • added support link

    v4.2 (2014-04-20)

    • fixed quote handling in form when switching from preview back to form
    • fixed some sting handling issues in admin dialog
    • fetch some php warnings
    • adopted to tinyMCE 4 (WP 3.9)

    v4.1 (2014-03-23)

    • added finish translation. Thanks to Pekka Ollikainen
    • fixed checkbox handling in admin dialog

    v4.0 (2014-03-14)

    • fixed cross browser bug with standard text editor
    • added danish translation. Thanks to Cristian Goga.
    • added the possibility to use external links behind images when using WordPress native gallery
    • fixed native gallery and no permalinks gallery view
    • load thickbox only on wp-greet form page for showing the terms of use
    • small fix to make it work with responsive lightbox too
    • fix tinymce and smilies
    • added option to disable load of wp-greet default css rules
    • fixed warning when next cellent gallery
    • fixed some phrases in admin dialog
    • adopted css to TwentyFourteen Theme
    • fixed some typos in english translation

    v3.9 (2013-12-02)

    • update spanish translation. Thanks to Pascal Cousseran
    • added catalan translation. Thanks to Pascal Cousseran
    • fixed problems with card display and escaped html

    v3.8 (2013-12-01)

    • fixed inline images with stamp and some email clients like (
    • fixed inline images for smilies
    • removed some deprecated messages and warnings

    v3.7 (2013-11-08)

    • added some stamps. Thanks to Sam Krieg
    • added TinyMCE support for the greet card form. Nice :-)

    v3.6 (2013-10-20)

    • added russian translation. Thanks to Papuna.
    • fixed some problems with permalinks and native galleries
    • now works with Jetpack Carousel
    • fixed interface to new version of Captcha! plugin

    v3.5 (2013-08-31)

    • added support for WordPress native gallery
    • fixed ereg deprecated warnings
    • fixed wpdb:Escape deprecated warnings

    v3.4 (2013-08-23)

    • added patch for NGG 2.11
    • adopt css to TwentyThirteen

    v3.3 (2013-08-11)

    • fixed one translation string
    • make resend link work with online and offline cards
    • only create log entry if log/card cleaned really delete at least one record
    • added a dirty hack to make wp-greet work again with ngg version >=2.0.0
    • added an admin notice with workaround when a broken NGG is used

    v3.2 (2013-05-09)

    • switched from load_textdomain to load_plugin_textdomain for compatibility reasons
    • added dutch translation. Thanks to Danny van Leeuwen
    • added spanish translation. Thanks to Pascal Cousseran
    • template vars are now accepted in mailheader and mailfooter too
    • check if email was already sent to avoid conflicts with other plugins which are using wp_redirect or similiar
    • clean up some php warnings
    • send each recipient one mail instead of one mail to all recipients for data protection reasons
    • generate unique cid's for image attachments
    • make sure datepicker extension is only loaded with wp-greet form
    • added support for bwcards plugin a selling plattform for greetings cards
    • fixed deprecated warning from add_option
    • fixed dbDelta Syntax
    • fixed sender got multiple CC's when sending to more than one recipient
    • updated datepicker and jqueryui to new version for compatibility with WP >=3.5
    • added romanian translation (Thanks to Bogdan)
    • added resend this card feature
    • extend future send to allow using UTC or timezone settings

    v3.1 (2012-06-07)

    • added support for WP-reCAPTCHA (must be installed and setup correctly to use)
    • fixed some PHP Notices
    • replaced user_level to capability in add_menu_* to get rid of these deprecated warnings

    v3.0 (2012-04-27)

    • use sender mail and name as replyto address even when static sender is set and mailreturnpath is not set
    • fixed sendername in link mails was set to blogname not to entered sendername

    v2.9 (2012-04-21)

    • fixed copy to sender was not sent when using greetcardlinkmails
    • changed to new php mailer interface for adding attachments
    • added css class wp-greet-error for formatting the warning and error messages

    v2.8 (2012-02-07)

    • fixed a problem using online cards without confirmation
    • fixed german translation
    • added english translation for datepicker

    v2.7 (2011-12-21)

    • adopted to HTML5 for compatibility with 3.3

    v2.6 (2011-12-05)

    • added static sender address feature to better support secure providers
    • added a bit more javascript to mark disabled fields in admin dialog
    • added wp collation in create table statements (caused problem with asian collations)
    • fixed received confirmation was sent on every fetch on some configs

    v2.5 (2011-11-12)

    • fixed another conflict wit wordpress mu

    v2.4 (2011-11-05)

    • added partial vietnamese translation, thanks to Diana
    • fix allow gallery and form on onepage
    • added option to use/display the data from ngg in img tag
    • added option to allow sending to multiple recipients
    • added option to allow sending cards in the future (using jquery datepicker, thanks folks, great job)
    • added option to allow sending a confirmation to the sender when the card is fetched
    • fixed incompatibility with wordpress mu in register_activation and deactivation
    • add support for captcha >=V2.08

    v2.3 (2010-12-01)

    • added swedish translation (thanks to Helene)
    • fixed confirmation mail method link generation (get_permalink problem)
    • fixed gallery link geneartion when not using permalinks
    • cc to sender now works even if you are using the "link variant"

    v2.2 (2010-10-01)

    • changed link generation to use wordpress default method
    • added french translation (thanks to Patrick)
    • update plugin to use new MathCommentSpamPlugin interface

    v2.1 (2009-12-05)

    • fixed problem with apostrophs in greetcard subject
    • fixed problem with some permalinks settings
    • added italian translation (thanks to Daniele)

    v2.0 (2009-11-21)

    • fixed process for fetching online without confirmation
    • fixed invalid xhtml in alt attribut during card fetch
    • fixed quote escaping when going back to greet form
    • fixed stamped image condition in conjunction with send image inline
    • fixed invalid xhtml in alt attribut on logging dialog
    • added note when stamp image is not found
    • fixed default value for stamp image
    • fixed re-show of greet form while confirmation
    • fixed admin dialog for control read-only status for stamp input field
    • fixed onlinecard plausi to be only validated if fetch cards online is active
    • fixed empty img width attribute when width parameter is empty (resulted in invalid XHTML)
    • fixed confirmation-link expiration if number of hours is 0 (= never expires)
    • fixed missing translation to german in security dialog
    • added some tooltips to admin dialog

    v1.9 (2009-11-03)

    • fixed XHTML errors in formdialog when using stamps
    • added mandatory field selection feature

    v1.8 (2009-10-12)

    • fixed some XHTML errors in admin dialog
    • fixed timestamp incompatibility between mysql < v4.1 and mysql >= v4.1
    • added admin dialog checkings carddays > fetch online days

    v1.7 (2009-10-11)

    • fixed some minor xhtml errors
    • added new admin dialog security
    • added feature to use an email for sender address verification
    • added terms of usage feature
    • added automatic deletion of log and card entries and parameters
    • added feature to fetch the card online instead of sending it via mail

    v1.6 (2009-08-15)

    • changed debug function name to avoid collision
    • check for checkdnsrr function to exist before using it
    • extend email address validation to be more correct (e.g. accept addresses)
    • switched readme.txt to new changelog format

    v1.5 (2009-06-06)

    • clean up code to avoid warnings in wordpress debug mode
    • add stamp function to add a stamp to greetingcards
    • readme.txt validated
    • added screenshots to package
    • added icon for wordpress menu entry
    • added parameter to set width of stamp

    v1.4 (2009-02-08)

    • fixed missing semicolon in phpmailer-conf.php
    • added none option to disable spam protection
    • fixed bug with quotes in mail-header and mail-footer
    • added option to control the mailtransfer method (smtp or php-mail)
    • fixed Spamlabel was showed, even when no captcha support was selected

    v1.3 (2009-01-03)

    • add support for Math-Comment-Spam-Protection-Plugin
    • add paging for logfile
    • fix bug with ngg >v0.99 and thickbox effect

    v1.2 (2008-11-30)

    • fixed some typos
    • added smiley support
    • added remote ip adress to log information
    • added automatic sender an receiver name
    • disable options deletion during plugin deactivation (seems people like it more having a bit trash in their tables, instead of setting up the plugin every time ;-) )
    • added fields for sender and receiver name

    v1.1 (2008-10-04)

    • integrate ngg without patching it (thanks to Alex Rabe for adding the needed filter hooks)
    • add gallery selection to admin dialog
    • add form page selector to admin dialog
    • fixed quote handling in textarea
    • disable captcha parameter during installation
    • extended css to be more flexible with different themes

    v1.0 (2008-04-14)

    • added captcha support
    • removed dependency to phpmailer package

    v0.9 (2008-04-06)

    • Initial release


    • PHP >=4.3
    • Wordpress >= 3.3.x
    • Optional: NextCellentGallery, NextGenGallery >= v1.00

    update from prior v1.1

    IMPORTANT: Please be sure to remove all files belonging to versions prior to v1.1 before uploading v1.1

    Please be sure to remove the patched version of nggfunctions.php
    which was necessary to integrate wp-greet with NextGenGallery 
    prior to version 1.1

    update to v1.7 and higher

    IMPORTANT: Please be sure to deactivate and activate the plugin one time because the database updates will only be executed during plugin activation

    usage from v1.1 on

    1. Create a page or posting containing the tag [wp-greet].
    2. Remember the permalink of this page/post
    3. Enter the page/post number at the wp-greet admin dialog into the field Form-Post/Page and switch to your favourite gallery plugin
    4. Create a page with your favourite gallery on it using the following syntax, e.g. for ngg: [gallery=1]
    5. thats it, just klick on a picture on the gallery page and send it

    For more details see the online documentation of wp-greet.


    wp-greet comes with english and german translations. if you would like to add a new translation, just take the file wp-greet.pot (in the wp-greet main directory) copy it to .po and edit it to add your translations (e.g. with poedit).

    Meanwhile a swedish, french, italians and vietnames translation was kindly build by other users. See Changelog for credits.

  29. This plugin gives better transliteration of non-ASCII characters in slugs.

    This plugin gives better transliteration of non-ASCII characters in slugs. Currently covers Esperanto, Swedish, Finnish, Danish, Norwegian, German, Russian and Bulgarian. It can also handle dashes.

    When WordPress creates slugs for the titles of posts and pages, and for tags and categories, it makes them all-ASCII, which among other things means removing diacritics (e.g. "é" becomes "e", "ö" becomes "o", "ĉ" becomes "c", etc.). For some languages the default filtering is OK, but for others it gives very bad results. The results for languages that don't even use a Latin script are especially unsatisfactory. The plugin Transliterado provides better transliteration systems for some languages. You can choose which of those systems should be used for your slugs. For some languages more than one transliteration system is available. Transliterado can also go through already existing posts and pages, and redo their slugs, if the user chooses that option. Another option does the same for tags and categories.

    Significant parts of the code comes from the plugins Rustolat by Anton Skorobogatov, BGtoLat by Ognyan Mladenov, and Slugger by Hans Christian Saustrup.

    Maybe you want to add systems for other languages. It's very easy to do. Have a look at the files for the languages that are in the plugin package already. I'll be happy to include any additions that are sent to me: "bertilow" at "".


    Ĉi tiu kromprogramo donas pli bonan transliteradon de ne-Askiaj literoj en URL-nomoj. Nun prizorgataj estas Esperanto, la Sveda, la Finna, la Dana, la Norvega, la Germana, la Rusa kaj la Bulgara.

    Kiam WordPress kreas URL-nomojn por afiŝoj kaj paĝoj, kaj por etikedoj kaj kategorioj, ĝi transformas ilin al Askio, kio interalie signifas, ke ĝi forigas ĉiujn kromsignojn (ekz. "é" fariĝas "e", "ö" fariĝas "o", "ĉ" fariĝas "c", k.t.p.). Por iuj lingvoj la defaŭlta filtrado estas en ordo, sed por aliaj ĝi donas tre malbonan rezulton. Precipe nekontentigaj estas la rezultoj por lingvoj, kiuj eĉ ne uzas la Latinan alfabeton. La kromprogramo Transliterado provizas pli bonajn transliteradajn sistemojn por kelkaj lingvoj. Oni povas elekti, kiuj el tiuj sistemoj estu uzataj por URL-nomoj. Por iuj lingvoj haveblas pli ol unu transliterada sistemo. Transliterado ankaŭ povas prilabori jam ekzistantajn afiŝojn kaj paĝoj, refarante ties URL-nomojn, se la uzanto elektas tiun eblon. Alia eblo faras la samon pri etikedoj kaj kategorioj.

    Gravaj partoj de la kodo venas el la kromprogramoj Rustolat de Anton Skorobogatov, BGtoLat de Ognyan Mladenov, kaj Slugger de Hans Christian Saustrup.

    Eble vi volas aldoni sistemojn por aliaj lingvoj. Tio estas tre facila. Rigardu la dosierojn de tiuj lingvoj, kiuj jam estas en la kromprograma paketo. Mi volonte enmetos aldonojn, kiujn vi sendos al mi: "bertilow" ĉe "".

    1. Upload all files to the /wp-content/plugins/transliterado/ directory
    2. Activate the plugin through the 'Plugins' menu in WordPress


    1. Alŝutu ĉiujn dosierojn al la dosierujo /wp-content/plugins/transliterado/
    2. Aktivigu la kromprogramon en la Kromprograma menuo en WordPress
    1. transliterado screenshot 1

      The interface of Transliterado 0.5 / La interfaco de Transliterado 0.5

    Licence / Licenco

    This plugin is released under the GPL licence. You can use it free of charge.

    Tiu ĉi kromprogramo estas publikigita sub la licenco GPL. Vi rajtas uzi ĝin senkoste.

    Translations / Tradukoj

    The basic language of Transliterado is Esperanto. There are translations into English, Swedish, Finnish, German, Russian and Bulgarian. More translations are of course welcome: "bertilow" at "".

    La baza lingvo de Transliterado estas Esperanto. Ekzistas tradukoj en la Anglan, la Svedan, la Finnan, la Germanan, la Rusan kaj la Bulgaran. Pliaj tradukoj estos bonvenaj: "bertilow" ĉe "".

  30. WordFez is a plugin for bilingual (French-English) posts. It is seamlessly integrated into Wordpress using a TinyMCE plugin.

    WordFez is a plugin for bilingual (French-English) posts. It is seamlessly integrated into Wordpress using a TinyMCE plugin.

    It will add 2 extra buttons in the WYSIWYG interface for French and English language. Each button inserts 2 anchors to surround each language. The anchors are labeled by small flags. The usage is very straight-forward. The plugin comes with a widget to allow each reader to conveniently and instantly switch between the languages.

    You need Wordpress 2.5 at least.

    New in v0.2.1:

    • Compatibility with Wordpress 2.5
    • Fix a small problem in 'alt' fields
    1. Download And unzip the files
    2. Upload all the files into the /wp-content/plugins/wordfez/ directory
    3. Activate the plugin through the 'Plugins' menu in WordPress
    4. Go to Design and then Widgets to add the WordFez widget to your sidebar.
    5. Go to write a Post or a Page (you may need to press 'F5' to refresh the cache).

    Any Question ?

Leave a Reply »

You must log in to post.

About this Topic