IThemes Codex - User contributions [en]

PluginBuddy

2012-05-11T17:45:43Z

Bes: Added username/password error info, /* 3 : Licensing/Login Issues due to Browsers */ section, and numbered other sections

Welcome to the PluginBuddy Knowledge Base - Tutorials, Technical Information, Debugging Information, and more.

=Premium Plugins=
* [[Ajax-Edit-Comments]]
* [[BackupBuddy]]
* [[DisplayBuddy]]
** [[Accordion]]
** [[Billboard]]
** [[Carousel]]
** [[CopiousComments]]
** [[FeaturedPosts]]
** [[Rotating Images]]
** [[RotatingText]]
** [[Slides]]
** [[Slideshow]]
** [[Tipsy]]
** [[VideoShowcase]]
* [[EmailBuddy]]
* [[Frolic]]
* [[LoopBuddy]]
* [[Mobile]]
* [[TailoredLogin]]
* [[ThumbsUp]]
* [[VidEmbed]]

=Free Plugins (active)=
* [[Featured Text]]
* [[PB-Tweet]]
* [[ServerBuddy]]
* [[Tabber Widget]]
* [[ThemeMan]]
* [[S3 URLS]]
* [[YOURLS]]
* [[ContactBuddy]]

=Free Plugins (inactive)=
* [[WP Easy Uploader]]
* [[WP Developer Assistant]]
* [[Easy Theme and Plugin Updater]]
* [[Current Date & Time Widget]]

''[[:Category:PluginBuddy|View all PluginBuddy Wiki Pages]]''

=Misc. Documentation=
==Frequently Asked (Plugin) Questions==
*[[General Plugins FAQ]]

==License Manager Tutorial and Information==
*[[License Manager]]
==PHP Development & Advanced==
*[[.htaccess]]
*[[PHP]]
*[[Arrays]]

[[Category:PluginBuddy]]

=Translations (localization / internationalization)=

Many PluginBuddy plugins come with translation capability. That means such PluginBuddy plugins can be translated (aka localized) to other languages.

===How Translations Work===

PluginBuddy provides the capability to have a translation in such plugins. Anyone wanting to enhance PluginBuddy with specific language translations can do so voluntarily via Translation Files. Translation Files are simply language files created fully and solely by the volunteer community which use the already built in translation-capable features in many of the PluginBuddy plugins to allow such plugins to show text or outputs in different languages. Making PluginBuddy translation-capable is done by PluginBuddy. Creating, updating and sending in any language specific translation files to PluginBuddy is done by the volunteer community.

Anyone can create translation files, package them into the proper format and give PluginBuddy the final translated files that we will try to include in the next update for the plugin in question. We call such awesome people, who create or update the translation files and send us the full translation package files, '''Awesome Translator Volunteers''', and we are really thankful that they take the time to do such an awesome thing.

If you want to help us, you can translate any existing PluginBuddy plugin which supports internationalization (another way of saying localization or translation-capable) and then, once you're fully done, simply let us know in the forums the link to the final language files that we can directly save and simply try to include in any future updates for the plugin(s) in question.

===Tips on how to localize any PluginBuddy Plugin to any non-English language===

The following 9 tips can help you figure out how to approach translations, how to create translations, and how to send us the final translated file for any translation-capable PluginBuddy plugin:

*1 : Many of the PluginBuddy plugins are internationalized, meaning they have the capability to be translated, via actual external translation files, by any non-iThemes-staff Awesome Translator Volunteer who wishes such plugins to be translated to their language.
*2 : If a PluginBuddy plugin is currently not internationalized or you're not sure if it is, you can ask us in the [http://ithemes.com/forum Support Forums] and we'll let you know, or we'll have it included as a future translation feature request. After the translation capability is added to such a plugin, you can submit the actual translation file. Please remember though: we cannot help with creating, understanding or making any language translation files. Our Awesome Translator Volunteers do that voluntarily (you can too! keep on reading) and fully on their own.
*3 : There are MANY resources which teach you how to create and work with WordPress language files. Following are the official 3 directly by the WordPress community:
**1 : [http://codex.wordpress.org/WordPress_in_Your_Language WordPress in Your Language]
**2 : [http://codex.wordpress.org/Translating_WordPress Translating WordPress]
**3 : [http://codex.wordpress.org/I18n_for_WordPress_Developers What WordPress Localization in Plugins is mainly about]
*4 : Translations are sent in from volunteers from all over the world. As a courtesy, we sometimes package the actual language translation files (provided directly by the Awesome Translator Volunteers) in with the final product. If some translation is not included in the actual plugin even when the plugin has the capability to be translated, you can submit the final translation to us for consideration in the next update by posting on our forums OR you can include the translation in your own live or local WordPress install directly for your own use. More info on how to include your own language specific file for your own WordPress sites is in the resources listed in #3 above.
*5 : A translation included in with the final product does not guarantee the accuracy or quality of the translation. These files are from the Awesome Translator Volunteers, and correction of these files is also done by those Awesome Translator Volunteers.
*6 : If a translation is very inaccurate or incomplete, we can put out a request for a new translation from the volunteer community, or remove the translation from the packaged and final product. You can also let us know of any inaccuracies in any existing translation files by the Awesome Volunteers by providing us with the corrected final files. Please remember: we only accept final and full translation files that you yourself have already created or packaged properly. If you let us know only of the actual inaccuracies without providing the final correct files, we cannot make such changes ourselves to the translation files.
*7 : Unfortunately, PluginBuddy cannot work on, help with, create, nor make any updates to any specific translation files you may have, or may be working on, or want to work on. Our Awesome Volunteers do that and simply give us the final files for inclusion or consideration.
*8 : If you have corrections for any existing translation in form of final proper format translation files for an existing language, OR want to provide the final and proper translation files for a new language, please post a new thread in the appropriate product category in the [http://ithemes.com/forum/ PluginBuddy Support Forums] with the final translations files. If you have any support questions on how to create or make language specific translation files, or how translation files work, you can do so on the [http://wordpress.org/support/ WordPress forums], as such support questions are outside the scope of what PluginBuddy support guarantees with your iThemes membership.
*9 : Any final translation file provided by you (or any other Awesome Volunteer) on the support forums will then be saved and filed as a future enhancement request for the future updates of the plugin(s) in question. In your support forum thread, where you share the final complete translation files you inclusion, you can upload your files directly to the forums OR upload them somewhere and link to them in your support forum thread. We will then download and save such files. Remember please: we cannot guarantee looking inside such files or verifying that they are correct in any manner (because of so many languages in the world and so many possible language files everywhere).

Thank you SO MUCH for being interested in providing translation files for our PluginBuddy plugins. We hope you will become one of our Awesome Translator Volunteers, in addition to being our AWESOME CUSTOMER, and create/update any language-specific translation file package and provide it to us so that we can consider including it in future updates.

===Resources for understanding, creating, updating and submitting final translation files===
*Here are the 3 official resources again which you can use to create, update, start work on and finish translation on any of the translation-capable PluginBuddy plugins:
**1 : [http://codex.wordpress.org/WordPress_in_Your_Language WordPress in Your Language]
**2 : [http://codex.wordpress.org/Translating_WordPress Translating WordPress]
**3 : [http://codex.wordpress.org/I18n_for_WordPress_Developers What WordPress Localization in Plugins is mainly about]

=Extra Customizations=
While any extra customization of any PluginBuddy Plugin is beyond the scope of the official support, we do from time to time offer different tips and tutorials on editing the awesome PluginBuddy plugins to better fit your individual needs. All such edits are, however, beyond what is officially supported and provided in the actual plugin admin panel and officially stated features on the individual plugin pages. No official support is provided nor guaranteed in, before, during, after or related to anything resulting from any such edits/customizations.

No support is provided on any of these extra customizations. Any of the steps mentioned in any of these extra custom edits may change at any time depending on newer versions of the plugins being released. Any use or customization of anything, beyond what is provided by default inside the plugin admin menu, means you are proceeding at your own risk and that you accept 100% responsibility and liability for everything you change or modify in any manner in the plugin. Your purchase and use of any PluginBuddy plugin implies and shows that you are buying and using PluginBuddy plugin(s) the way it(they) came in their original unmodified form, with no exceptions.

*Remember:
**[http://pluginbuddy.com/purchase/backupbuddy/ Make a backup of your entire site with BackupBuddy] before making any edits!
** PluginBuddy only supports the official unedited, unmodified versions of all PluginBuddy plugins.
** Use a good text editor to make any file changes. Again, maintain backups!
** Any changes you make to files WILL MOST PROBABLY be lost when the plugin is upgraded to any newer version.
** You are 100% responsible and liable for anything resulting from any of these changes.
** No support is provided nor guaranteed on any of these extra changes in any form or shape, whatsoever, regardless of who suggested these custom edits or suggestions.
** Any extra customization info or suggestion is added voluntarily by PluginBuddy staff to help users as much as possible, even if such customization is outside the scope of any membership support.
** Whether a PluginBuddy staff or representative offered or suggested the edit/customization, another customer or anyone else, PluginBuddy does not officially support nor provide any official support on any such edits.
** We cannot guarantee providing any support on any edits or customization tips we provide.
** Absolutely no support is guaranteed in any manner on any of our free plugins, whether or not there is any customization/edit involved.

=External Plugins Compatibility=

PluginBuddy does not promise, guarantee or provide support for any compatibility with any external plugin. If any PluginBuddy Plugin works without any problems when used with any external plugin in question, that means the PluginBuddy Plugin is most probably working without any issues overall. PluginBuddy is not responsible for making PluginBuddy plugins work in any manner, whether custom, fully, fixed or other, with any external non-PluginBuddy plugins. PluginBuddy is also not responsible for providing any support whatsoever for any external plugin, whether or not such an external plugin is used along with any PluginBuddy plugin.

=Free Plugins=

Free plugins are provided as is. There is no guaranteed support that comes with them. Guaranteed support is limited only and mainly for our premium unmodified plugins.

=Bugs, Features and ETA on new updates=

With every new release of any plugin, there may be a new bug or two. You may also want to have new features added to specific plugins. All existing versions of all plugins can have bugs reported OR new features suggested. All of this is done via the [http://ithemes.com/forum official forums].

New updates are also usually released regularly and at the same time, at very different paces, depending on the current number of bugs, features, new plans and tasks at hand. Therefore it is the official policy that there is NO pre-defined ETA on any bug fix, feature imeplemention OR new update OR new plugin roll-out UNLESS otherwise specified specifically in writing somewhere by an official iThemes employee.

==Bugs, bug reports and bug fixes==

Bug reports are filed and noted as they are encountered (thanks for reporting them to us!). There is never any ETA on any bug fixes unless otherwise noted.

==Feature Requests==

Feature requests and feature suggestions are basically future suggested features that users can suggest, and/or future features PluginBuddy may consider adding to the future versions of the plugin(s) in question (again, thanks for suggesting new features!).

There is no guaranteed ETA on when such feature requests will be implemented, unless otherwise noted. All suggested features are just that: suggestions. They remain suggestions until they're confirmed as officially in the works and to be included. Even then, unless a feature is actually rolled out publicly, there is no guarantee any feature suggestion will be implemented. We do our best to try and accommodate as many feature suggestions as possible.

Also, there is no guarantee that any feature request suggested will be implemented, unless otherwise noted.

==ETA on new updates==

Just like bug fixes and new features, there is never a guaranteed date nor a guaranteed time frame on when new updates will roll out. We work every single day of the week, all the time, on our plugins and thus every day there is something new and improved happening in almost all our plugins daily. Whenever we are ready to release any new updates publicly, you'll find out by seeing the plugin update notice in your WordPress OR in your [http://ithemes.com/member/member.php Member's area].

=What does BETA mean?=

Some of PluginBuddy plugins may be in Beta status OR may have Beta features. BETA simply means that some feature or specific part of the plugin is currently still in testing mode, and can cause issues if not used properly. All BETA plugins/features are not yet 100% stable, and thus should NOT be relied on to be working properly OR working at all. Throughout the iThemes Codex, any time the word "Beta" is used in any form, it refers to Beta plugins, Beta features, Beta status and/or anything related to the Beta nature that is officially announced or mentioned as such by any iThemes staff or on any of the Plugin pages, or in this Codex.

Beta implies that any new features or plugins are very close to being released as 100% working very soon, and that there may still be some issues to fix or test more before removing the Beta status. Since no single software of any kind can be tested under every system and site configuration in the world, the Beta status enables the Beta features to be tested out by as many people on as many different websites and configurations as possible.

*Some points to keep in mind when using any BETA plugin/feature:
**1 : Make [http://pluginbuddy.com/purchase/backupbuddy/ FULL WordPress backups] before using ANY beta feature.
**2 : Beta means that the current software feature is NOT complete, and that you are NOT forced to use such a feature at all. You are advised to WAIT until the BETA status is removed.
**3 : Using any Beta feature of any kind, whether it is an entire plugin or something inside a plugin, means and shows that you are fully accepting any liability for any risks involved.
**4 : Using any Beta feature of any kind, whether it is an entire plugin or something inside a plugin, means and shows that you are fully aware that there are all different kinds of risks involved with such features.
**5 : If you are concerned about your important data or anything bad that might happen as a result of using any Beta feature, do NOT use such Beta features.
**6 : ALWAYS make full [http://pluginbuddy.com/purchase/backupbuddy/ BackupBuddy Backups of all your important data] before using any Beta software, whether that Beta software is from PluginBuddy or from any other place.
**7 : If any issues are found in Beta, they are usually added to the list of bug fixes to be released as a whole, or for the next big update, instead of being updated OR fixed individually on a case by case basis.
**8 : Beta features are recommended to test and play with on test sites/servers and configurations with any dummy data, as long as you have [http://pluginbuddy.com/purchase/backupbuddy/ full backups of all important data] still.
**9 : iThemes is not liable nor cannot be held accountable for any unwanted results resulting from the use of BETA features.
**10 : The very name and nature of BETA shows clearly, without any doubt, that there will most probably be issues and problems involved when such labeled features are used anywhere.
**11 : Support for Beta features may be very limited. We usually simply collect all reports related to Beta features and collect them all for one big update in the future.
**12 : If you lose any important data or settings anywhere, or encounter damaged data or settings anywhere, because of any Beta feature, we will not be able to help you and will simply tell you to revert to your previous [http://pluginbuddy.com/purchase/backupbuddy/ backups]. We will also tell you to always wait for BETA status to be removed before using any such features.

If you do not fully understand what Beta means, OR are not willing to fully accept and be fully liable for any risks involved because of using such Beta software, you should NOT use the Beta software in any manner. In such a case, you should simply wait until the Beta status is removed.

*[http://pluginbuddy.com/what-does-beta-mean/ Blog post announcing what BETA means]

=PluginBuddy Licenses=

In unusual cases, you may run into some of the following licensing issues or errors. The possible solutions are listed below in their own separate sections:

*Error Messages
**'''You have already generated all the keys you have available or your licenses have expired. Please obtain additional licenses or unlicense a site. ERROR L14513-JW.'''
**'''Invalid license key, it has expired, or it is already in use. Please verify the key or contact support for assistance.'''
**'''Username and/or password is invalid. Are you using your iThemes password?'''

==1 : Licenses Issues due to Plugin Conflicts==

Some times, external plugins may cause issues in detaching, deleting, generating OR saving license keys. Such plugins may also cause issues when you want to manually or automatically upgrade plugins when you try to solve licensing issues.

*You may run into this error
**'''Invalid license key, it has expired, or it is already in use. Please verify the key or contact support for assistance.'''

Following is a list of currently known plugins which cause license detaching, deleting, generating OR saving issues. Please disable the following plugins, even temporarily, while you perform all the steps of manually OR automatically upgrading the PluginBuddy plugins in question, and detaching, deleting, generating and saving license keys for them. Keep such plugins disabled UNTIL all license key issues are gone OR at least while you perform these steps.

*Plugins causing PluginBuddy licensing issues
**'''W3 Total Cache or WP Super Cache or WinCache :''' If you are using any caching plugin like '''W3 Total Cache''' or '''WP Super Cache''' or any PHP Extension like WinCache, please disable it temporarily and then carry out any required steps. You can re-enable the plugin or extension in the end after everything works in terms of the licenses.
**Fix: Follow the above steps to fix this issue. [http://ithemes.com/forum/index.php?/topic/19436-backupbuddy-license-issue/#p92171 Steps also explained by BackupBuddy customer Laura (thanks!)]
**'''Any other CACHING or related plugin or extension:''' Try disabling such plugins/extensions, performing the required steps, and then re-activating the Caching or related plugins/extensions in question.

*Related Links
**1 : [http://ithemes.com/forum/topic/26635-error-message-invalid-license-key/page__view__findpost__p__123839 whitewolf deactivated W3 Total Cache, which got rid of the Licensing errors]
**2 : [http://ithemes.com/forum/topic/24881-license-key-is-not-set-yet-or-invalid/page__view__findpost__p__116047 blm03 deactivated W3 Total Cache, which allowed the licenses to save correctly]
**3 : [http://ithemes.com/forum/topic/26022-cant-generate-a-license-for-my-domain/page__view__findpost__p__121072 Disabling WinCache extension for PHP fixes Licensing issues]
**4 : [http://ithemes.com/forum/topic/24737-backupbuddy-manage-licenses/page__view__findpost__p__115187 Karlos deactivated W3 Total Cache, and that fixed the licensing issues]
**5 : [http://ithemes.com/forum/topic/23481-license-issue-pluginbuddy-developer-to-backupbuddy-both-unlimited/page__view__findpost__p__110368 Disabling W3 Total Cache modules allowed Greg to license BackupBuddy without any issues]
**6 : [http://ithemes.com/forum/topic/23275-unable-to-get-license-to-stick/page__pid__109503#entry109503 W3 Total Cache causing licenses to be deleted after a while]
**7 : [http://ithemes.com/forum/topic/22964-cant-find-stylesheet-to-make-adjustments-to-slider/page__view__findpost__p__107933 W3 Total Cache not allowing licenses to be saved properly]
**8 : [http://ithemes.com/forum/topic/22859-bub-licenses-not-taking-effect/page__view__findpost__p__107476 W3 Total Cache not allowing licenses to be saved - easy solution!]
**9 : [http://ithemes.com/forum/index.php?/topic/19079-wont-let-me-set-a-license-key/#p91663 W3 Total Cache plugin conflict and solution]
**10 : [http://ithemes.com/forum/index.php?/topic/19436-backupbuddy-license-issue/#p92171 W3 Total Cache plugin conflict and solution]
**11 : [http://ithemes.com/forum/index.php?/topic/20228-key-does-not-work/#p95697 W3 Total Cache plugin conflict and solution]
**12 : [http://ithemes.com/forum/index.php?/topic/19041-license-problem-causes-loss-of-all-bb-settings-way-to-get-them-back/ WP Super Cache conflict and solution]

==2 : Licensing issues due to different Membership/Account scenarios==

You may run into licensing issues if something unexpected is happening in or to your membership/accounts.

*Having '''multiple accounts''' with the '''same e-mail address'''.
**If you have more than one account with iThemes and use the same e-mail address with all (or more than one of) your accounts, you may run into the following error:
*** '''You have already generated all the keys you have available or your licenses have expired. Please obtain additional licenses or unlicense a site. ERROR L14513-JW'''
**One solution is to have your accounts combined by contacting sales.
**Another solution is to make sure you associate each account with a different e-mail address.
*** [http://ithemes.com/forum/topic/26420-bought-2-site-license-used-on-1-site-cant-generate-key-for-2nd-site/ User having 2 accounts with the same e-mail, getting ERROR L14513-JW, and resolving the issue by making sure their 2 accounts have 2 separate e-mail addresses]

==3 : Licensing/Login Issues due to Browsers==

Sometimes, your browser may have an add-on or extension/module, or a built-in feature, which may interfere with your username or password.

*You may get an error when trying to log into your iThemes account from within the License Manager:
**'''Username and/or password is invalid. Are you using your iThemes password?'''

*Possible solutions:
**You can turn off all add-ons/modules/extensions in your browser and then try logging in again.
**You can try other browsers (Firefox, Chrome, Internet Explorer, Safari, etc) to try and log in.
**This may also be related to your host. Please ask your host if they're blocking any IP address or connections of such types where you log into iThemes from/through your website plugins.

==4 : Other Steps to Resolve Licensing Issues==

There are some reports that some users have issues with their license insides the Licenses area of different PluginBuddy plugins, including BackupBuddy.

Remember: All your PluginBuddy plugins, including BackupBuddy, will CONTINUE WORKING PERFECTLY even with these licensing issues. You can keep using the plugins exactly how you want them even during these licensing issues. Your plugins are NOT affected by this licensing situation in any manner.

Your membership is also completely fine and you have NOT lost any license(s). The issue is happening to some customers who simply need to upgrade manually to the latest version of their plugin, if the automatic upgrade does not work.

*Plugins with the update versions which remove this issue completely
**ALL PluginBuddy Products

*You can upgrade via one of the following:
**Automatically upgrade to the latest version
**Manually update by downloading the latest zip version of your PluginBuddy plugin from your Member's panel and then
***Overwrite your existing plugin directory via FTP with the new files.
***De-activate the existing plugin, delete it via your '''WordPress --> Plugins''' area and then upload the newly downloaded zip file. Then re-activate the plugin.
**That will remove the issue completely.
*DETACH the key and then RE-ATTACH the license key for the specific site in question IF licensing still shows issues AFTER manually upgrading to the latest version of the plugin in question (check your Member's area for the latest version download)
*Also make sure to DETACH the key, DELETE that same AND any other keys related to that specific site from the entire licenses area, and then GENERATE a new key for that site IF detaching and re-attaching the license key does not work AFTER manually upgrading (for example, manually upgrading to the latest BackupBuddy version - all plugins have their own latest version numbers - check your Member's area for the latest version download)

[http://ithemes.com/forum/index.php?/topic/6691-read-this-first-pluginbuddy-licensing-issues/page-2/#p85977 First reports]

PluginBuddy

2012-04-19T19:23:00Z

Bes: Added "Invalid license key, it has expired, or it is already in use. Please verify the key or contact support for assistance." error message listing /* PluginBuddy Licenses */

Welcome to the PluginBuddy Knowledge Base - Tutorials, Technical Information, Debugging Information, and more.

=Premium Plugins=
* [[Ajax-Edit-Comments]]
* [[BackupBuddy]]
* [[DisplayBuddy]]
** [[Accordion]]
** [[Billboard]]
** [[Carousel]]
** [[CopiousComments]]
** [[FeaturedPosts]]
** [[Rotating Images]]
** [[RotatingText]]
** [[Slides]]
** [[Slideshow]]
** [[Tipsy]]
** [[VideoShowcase]]
* [[EmailBuddy]]
* [[Frolic]]
* [[LoopBuddy]]
* [[Mobile]]
* [[TailoredLogin]]
* [[ThumbsUp]]
* [[VidEmbed]]

=Free Plugins (active)=
* [[Featured Text]]
* [[PB-Tweet]]
* [[ServerBuddy]]
* [[Tabber Widget]]
* [[ThemeMan]]
* [[S3 URLS]]
* [[YOURLS]]
* [[ContactBuddy]]

=Free Plugins (inactive)=
* [[WP Easy Uploader]]
* [[WP Developer Assistant]]
* [[Easy Theme and Plugin Updater]]
* [[Current Date & Time Widget]]

''[[:Category:PluginBuddy|View all PluginBuddy Wiki Pages]]''

=Misc. Documentation=
==Frequently Asked (Plugin) Questions==
*[[General Plugins FAQ]]

==License Manager Tutorial and Information==
*[[License Manager]]
==PHP Development & Advanced==
*[[.htaccess]]
*[[PHP]]
*[[Arrays]]

[[Category:PluginBuddy]]

=Translations (localization / internationalization)=

Many PluginBuddy plugins come with translation capability. That means such PluginBuddy plugins can be translated (aka localized) to other languages.

===How Translations Work===

PluginBuddy provides the capability to have a translation in such plugins. Anyone wanting to enhance PluginBuddy with specific language translations can do so voluntarily via Translation Files. Translation Files are simply language files created fully and solely by the volunteer community which use the already built in translation-capable features in many of the PluginBuddy plugins to allow such plugins to show text or outputs in different languages. Making PluginBuddy translation-capable is done by PluginBuddy. Creating, updating and sending in any language specific translation files to PluginBuddy is done by the volunteer community.

Anyone can create translation files, package them into the proper format and give PluginBuddy the final translated files that we will try to include in the next update for the plugin in question. We call such awesome people, who create or update the translation files and send us the full translation package files, '''Awesome Translator Volunteers''', and we are really thankful that they take the time to do such an awesome thing.

If you want to help us, you can translate any existing PluginBuddy plugin which supports internationalization (another way of saying localization or translation-capable) and then, once you're fully done, simply let us know in the forums the link to the final language files that we can directly save and simply try to include in any future updates for the plugin(s) in question.

===Tips on how to localize any PluginBuddy Plugin to any non-English language===

The following 9 tips can help you figure out how to approach translations, how to create translations, and how to send us the final translated file for any translation-capable PluginBuddy plugin:

*1 : Many of the PluginBuddy plugins are internationalized, meaning they have the capability to be translated, via actual external translation files, by any non-iThemes-staff Awesome Translator Volunteer who wishes such plugins to be translated to their language.
*2 : If a PluginBuddy plugin is currently not internationalized or you're not sure if it is, you can ask us in the [http://ithemes.com/forum Support Forums] and we'll let you know, or we'll have it included as a future translation feature request. After the translation capability is added to such a plugin, you can submit the actual translation file. Please remember though: we cannot help with creating, understanding or making any language translation files. Our Awesome Translator Volunteers do that voluntarily (you can too! keep on reading) and fully on their own.
*3 : There are MANY resources which teach you how to create and work with WordPress language files. Following are the official 3 directly by the WordPress community:
**1 : [http://codex.wordpress.org/WordPress_in_Your_Language WordPress in Your Language]
**2 : [http://codex.wordpress.org/Translating_WordPress Translating WordPress]
**3 : [http://codex.wordpress.org/I18n_for_WordPress_Developers What WordPress Localization in Plugins is mainly about]
*4 : Translations are sent in from volunteers from all over the world. As a courtesy, we sometimes package the actual language translation files (provided directly by the Awesome Translator Volunteers) in with the final product. If some translation is not included in the actual plugin even when the plugin has the capability to be translated, you can submit the final translation to us for consideration in the next update by posting on our forums OR you can include the translation in your own live or local WordPress install directly for your own use. More info on how to include your own language specific file for your own WordPress sites is in the resources listed in #3 above.
*5 : A translation included in with the final product does not guarantee the accuracy or quality of the translation. These files are from the Awesome Translator Volunteers, and correction of these files is also done by those Awesome Translator Volunteers.
*6 : If a translation is very inaccurate or incomplete, we can put out a request for a new translation from the volunteer community, or remove the translation from the packaged and final product. You can also let us know of any inaccuracies in any existing translation files by the Awesome Volunteers by providing us with the corrected final files. Please remember: we only accept final and full translation files that you yourself have already created or packaged properly. If you let us know only of the actual inaccuracies without providing the final correct files, we cannot make such changes ourselves to the translation files.
*7 : Unfortunately, PluginBuddy cannot work on, help with, create, nor make any updates to any specific translation files you may have, or may be working on, or want to work on. Our Awesome Volunteers do that and simply give us the final files for inclusion or consideration.
*8 : If you have corrections for any existing translation in form of final proper format translation files for an existing language, OR want to provide the final and proper translation files for a new language, please post a new thread in the appropriate product category in the [http://ithemes.com/forum/ PluginBuddy Support Forums] with the final translations files. If you have any support questions on how to create or make language specific translation files, or how translation files work, you can do so on the [http://wordpress.org/support/ WordPress forums], as such support questions are outside the scope of what PluginBuddy support guarantees with your iThemes membership.
*9 : Any final translation file provided by you (or any other Awesome Volunteer) on the support forums will then be saved and filed as a future enhancement request for the future updates of the plugin(s) in question. In your support forum thread, where you share the final complete translation files you inclusion, you can upload your files directly to the forums OR upload them somewhere and link to them in your support forum thread. We will then download and save such files. Remember please: we cannot guarantee looking inside such files or verifying that they are correct in any manner (because of so many languages in the world and so many possible language files everywhere).

Thank you SO MUCH for being interested in providing translation files for our PluginBuddy plugins. We hope you will become one of our Awesome Translator Volunteers, in addition to being our AWESOME CUSTOMER, and create/update any language-specific translation file package and provide it to us so that we can consider including it in future updates.

===Resources for understanding, creating, updating and submitting final translation files===
*Here are the 3 official resources again which you can use to create, update, start work on and finish translation on any of the translation-capable PluginBuddy plugins:
**1 : [http://codex.wordpress.org/WordPress_in_Your_Language WordPress in Your Language]
**2 : [http://codex.wordpress.org/Translating_WordPress Translating WordPress]
**3 : [http://codex.wordpress.org/I18n_for_WordPress_Developers What WordPress Localization in Plugins is mainly about]

=Extra Customizations=
While any extra customization of any PluginBuddy Plugin is beyond the scope of the official support, we do from time to time offer different tips and tutorials on editing the awesome PluginBuddy plugins to better fit your individual needs. All such edits are, however, beyond what is officially supported and provided in the actual plugin admin panel and officially stated features on the individual plugin pages. No official support is provided nor guaranteed in, before, during, after or related to anything resulting from any such edits/customizations.

No support is provided on any of these extra customizations. Any of the steps mentioned in any of these extra custom edits may change at any time depending on newer versions of the plugins being released. Any use or customization of anything, beyond what is provided by default inside the plugin admin menu, means you are proceeding at your own risk and that you accept 100% responsibility and liability for everything you change or modify in any manner in the plugin. Your purchase and use of any PluginBuddy plugin implies and shows that you are buying and using PluginBuddy plugin(s) the way it(they) came in their original unmodified form, with no exceptions.

*Remember:
**[http://pluginbuddy.com/purchase/backupbuddy/ Make a backup of your entire site with BackupBuddy] before making any edits!
** PluginBuddy only supports the official unedited, unmodified versions of all PluginBuddy plugins.
** Use a good text editor to make any file changes. Again, maintain backups!
** Any changes you make to files WILL MOST PROBABLY be lost when the plugin is upgraded to any newer version.
** You are 100% responsible and liable for anything resulting from any of these changes.
** No support is provided nor guaranteed on any of these extra changes in any form or shape, whatsoever, regardless of who suggested these custom edits or suggestions.
** Any extra customization info or suggestion is added voluntarily by PluginBuddy staff to help users as much as possible, even if such customization is outside the scope of any membership support.
** Whether a PluginBuddy staff or representative offered or suggested the edit/customization, another customer or anyone else, PluginBuddy does not officially support nor provide any official support on any such edits.
** We cannot guarantee providing any support on any edits or customization tips we provide.
** Absolutely no support is guaranteed in any manner on any of our free plugins, whether or not there is any customization/edit involved.

=External Plugins Compatibility=

PluginBuddy does not promise, guarantee or provide support for any compatibility with any external plugin. If any PluginBuddy Plugin works without any problems when used with any external plugin in question, that means the PluginBuddy Plugin is most probably working without any issues overall. PluginBuddy is not responsible for making PluginBuddy plugins work in any manner, whether custom, fully, fixed or other, with any external non-PluginBuddy plugins. PluginBuddy is also not responsible for providing any support whatsoever for any external plugin, whether or not such an external plugin is used along with any PluginBuddy plugin.

=Free Plugins=

Free plugins are provided as is. There is no guaranteed support that comes with them. Guaranteed support is limited only and mainly for our premium unmodified plugins.

=Bugs, Features and ETA on new updates=

With every new release of any plugin, there may be a new bug or two. You may also want to have new features added to specific plugins. All existing versions of all plugins can have bugs reported OR new features suggested. All of this is done via the [http://ithemes.com/forum official forums].

New updates are also usually released regularly and at the same time, at very different paces, depending on the current number of bugs, features, new plans and tasks at hand. Therefore it is the official policy that there is NO pre-defined ETA on any bug fix, feature imeplemention OR new update OR new plugin roll-out UNLESS otherwise specified specifically in writing somewhere by an official iThemes employee.

==Bugs, bug reports and bug fixes==

Bug reports are filed and noted as they are encountered (thanks for reporting them to us!). There is never any ETA on any bug fixes unless otherwise noted.

==Feature Requests==

Feature requests and feature suggestions are basically future suggested features that users can suggest, and/or future features PluginBuddy may consider adding to the future versions of the plugin(s) in question (again, thanks for suggesting new features!).

There is no guaranteed ETA on when such feature requests will be implemented, unless otherwise noted. All suggested features are just that: suggestions. They remain suggestions until they're confirmed as officially in the works and to be included. Even then, unless a feature is actually rolled out publicly, there is no guarantee any feature suggestion will be implemented. We do our best to try and accommodate as many feature suggestions as possible.

Also, there is no guarantee that any feature request suggested will be implemented, unless otherwise noted.

==ETA on new updates==

Just like bug fixes and new features, there is never a guaranteed date nor a guaranteed time frame on when new updates will roll out. We work every single day of the week, all the time, on our plugins and thus every day there is something new and improved happening in almost all our plugins daily. Whenever we are ready to release any new updates publicly, you'll find out by seeing the plugin update notice in your WordPress OR in your [http://ithemes.com/member/member.php Member's area].

=What does BETA mean?=

Some of PluginBuddy plugins may be in Beta status OR may have Beta features. BETA simply means that some feature or specific part of the plugin is currently still in testing mode, and can cause issues if not used properly. All BETA plugins/features are not yet 100% stable, and thus should NOT be relied on to be working properly OR working at all. Throughout the iThemes Codex, any time the word "Beta" is used in any form, it refers to Beta plugins, Beta features, Beta status and/or anything related to the Beta nature that is officially announced or mentioned as such by any iThemes staff or on any of the Plugin pages, or in this Codex.

Beta implies that any new features or plugins are very close to being released as 100% working very soon, and that there may still be some issues to fix or test more before removing the Beta status. Since no single software of any kind can be tested under every system and site configuration in the world, the Beta status enables the Beta features to be tested out by as many people on as many different websites and configurations as possible.

*Some points to keep in mind when using any BETA plugin/feature:
**1 : Make [http://pluginbuddy.com/purchase/backupbuddy/ FULL WordPress backups] before using ANY beta feature.
**2 : Beta means that the current software feature is NOT complete, and that you are NOT forced to use such a feature at all. You are advised to WAIT until the BETA status is removed.
**3 : Using any Beta feature of any kind, whether it is an entire plugin or something inside a plugin, means and shows that you are fully accepting any liability for any risks involved.
**4 : Using any Beta feature of any kind, whether it is an entire plugin or something inside a plugin, means and shows that you are fully aware that there are all different kinds of risks involved with such features.
**5 : If you are concerned about your important data or anything bad that might happen as a result of using any Beta feature, do NOT use such Beta features.
**6 : ALWAYS make full [http://pluginbuddy.com/purchase/backupbuddy/ BackupBuddy Backups of all your important data] before using any Beta software, whether that Beta software is from PluginBuddy or from any other place.
**7 : If any issues are found in Beta, they are usually added to the list of bug fixes to be released as a whole, or for the next big update, instead of being updated OR fixed individually on a case by case basis.
**8 : Beta features are recommended to test and play with on test sites/servers and configurations with any dummy data, as long as you have [http://pluginbuddy.com/purchase/backupbuddy/ full backups of all important data] still.
**9 : iThemes is not liable nor cannot be held accountable for any unwanted results resulting from the use of BETA features.
**10 : The very name and nature of BETA shows clearly, without any doubt, that there will most probably be issues and problems involved when such labeled features are used anywhere.
**11 : Support for Beta features may be very limited. We usually simply collect all reports related to Beta features and collect them all for one big update in the future.
**12 : If you lose any important data or settings anywhere, or encounter damaged data or settings anywhere, because of any Beta feature, we will not be able to help you and will simply tell you to revert to your previous [http://pluginbuddy.com/purchase/backupbuddy/ backups]. We will also tell you to always wait for BETA status to be removed before using any such features.

If you do not fully understand what Beta means, OR are not willing to fully accept and be fully liable for any risks involved because of using such Beta software, you should NOT use the Beta software in any manner. In such a case, you should simply wait until the Beta status is removed.

*[http://pluginbuddy.com/what-does-beta-mean/ Blog post announcing what BETA means]

=PluginBuddy Licenses=

In unusual cases, you may run into some of the following licensing issues or errors. The possible solutions are listed below in their own separate sections:

*Error Messages
**'''You have already generated all the keys you have available or your licenses have expired. Please obtain additional licenses or unlicense a site. ERROR L14513-JW.'''
**'''Invalid license key, it has expired, or it is already in use. Please verify the key or contact support for assistance.'''

==Licenses Issues due to Plugin Conflicts==

Some times, external plugins may cause issues in detaching, deleting, generating OR saving license keys. Such plugins may also cause issues when you want to manually or automatically upgrade plugins when you try to solve licensing issues.

*You may run into this error
**'''Invalid license key, it has expired, or it is already in use. Please verify the key or contact support for assistance.'''

Following is a list of currently known plugins which cause license detaching, deleting, generating OR saving issues. Please disable the following plugins, even temporarily, while you perform all the steps of manually OR automatically upgrading the PluginBuddy plugins in question, and detaching, deleting, generating and saving license keys for them. Keep such plugins disabled UNTIL all license key issues are gone OR at least while you perform these steps.

*Plugins causing PluginBuddy licensing issues
**'''W3 Total Cache or WP Super Cache or WinCache :''' If you are using any caching plugin like '''W3 Total Cache''' or '''WP Super Cache''' or any PHP Extension like WinCache, please disable it temporarily and then carry out any required steps. You can re-enable the plugin or extension in the end after everything works in terms of the licenses.
**Fix: Follow the above steps to fix this issue. [http://ithemes.com/forum/index.php?/topic/19436-backupbuddy-license-issue/#p92171 Steps also explained by BackupBuddy customer Laura (thanks!)]
**'''Any other CACHING or related plugin or extension:''' Try disabling such plugins/extensions, performing the required steps, and then re-activating the Caching or related plugins/extensions in question.

*Related Links
**1 : [http://ithemes.com/forum/topic/26635-error-message-invalid-license-key/page__view__findpost__p__123839 whitewolf deactivated W3 Total Cache, which got rid of the Licensing errors]
**2 : [http://ithemes.com/forum/topic/24881-license-key-is-not-set-yet-or-invalid/page__view__findpost__p__116047 blm03 deactivated W3 Total Cache, which allowed the licenses to save correctly]
**3 : [http://ithemes.com/forum/topic/26022-cant-generate-a-license-for-my-domain/page__view__findpost__p__121072 Disabling WinCache extension for PHP fixes Licensing issues]
**4 : [http://ithemes.com/forum/topic/24737-backupbuddy-manage-licenses/page__view__findpost__p__115187 Karlos deactivated W3 Total Cache, and that fixed the licensing issues]
**5 : [http://ithemes.com/forum/topic/23481-license-issue-pluginbuddy-developer-to-backupbuddy-both-unlimited/page__view__findpost__p__110368 Disabling W3 Total Cache modules allowed Greg to license BackupBuddy without any issues]
**6 : [http://ithemes.com/forum/topic/23275-unable-to-get-license-to-stick/page__pid__109503#entry109503 W3 Total Cache causing licenses to be deleted after a while]
**7 : [http://ithemes.com/forum/topic/22964-cant-find-stylesheet-to-make-adjustments-to-slider/page__view__findpost__p__107933 W3 Total Cache not allowing licenses to be saved properly]
**8 : [http://ithemes.com/forum/topic/22859-bub-licenses-not-taking-effect/page__view__findpost__p__107476 W3 Total Cache not allowing licenses to be saved - easy solution!]
**9 : [http://ithemes.com/forum/index.php?/topic/19079-wont-let-me-set-a-license-key/#p91663 W3 Total Cache plugin conflict and solution]
**10 : [http://ithemes.com/forum/index.php?/topic/19436-backupbuddy-license-issue/#p92171 W3 Total Cache plugin conflict and solution]
**11 : [http://ithemes.com/forum/index.php?/topic/20228-key-does-not-work/#p95697 W3 Total Cache plugin conflict and solution]
**12 : [http://ithemes.com/forum/index.php?/topic/19041-license-problem-causes-loss-of-all-bb-settings-way-to-get-them-back/ WP Super Cache conflict and solution]

==Licensing issues due to different Membership/Account scenarios==

You may run into licensing issues if something unexpected is happening in or to your membership/accounts.

*Having '''multiple accounts''' with the '''same e-mail address'''.
**If you have more than one account with iThemes and use the same e-mail address with all (or more than one of) your accounts, you may run into the following error:
*** '''You have already generated all the keys you have available or your licenses have expired. Please obtain additional licenses or unlicense a site. ERROR L14513-JW'''
**One solution is to have your accounts combined by contacting sales.
**Another solution is to make sure you associate each account with a different e-mail address.
*** [http://ithemes.com/forum/topic/26420-bought-2-site-license-used-on-1-site-cant-generate-key-for-2nd-site/ User having 2 accounts with the same e-mail, getting ERROR L14513-JW, and resolving the issue by making sure their 2 accounts have 2 separate e-mail addresses]

==Other Steps to Resolve Licensing Issues==

There are some reports that some users have issues with their license insides the Licenses area of different PluginBuddy plugins, including BackupBuddy.

Remember: All your PluginBuddy plugins, including BackupBuddy, will CONTINUE WORKING PERFECTLY even with these licensing issues. You can keep using the plugins exactly how you want them even during these licensing issues. Your plugins are NOT affected by this licensing situation in any manner.

Your membership is also completely fine and you have NOT lost any license(s). The issue is happening to some customers who simply need to upgrade manually to the latest version of their plugin, if the automatic upgrade does not work.

*Plugins with the update versions which remove this issue completely
**ALL PluginBuddy Products

*You can upgrade via one of the following:
**Automatically upgrade to the latest version
**Manually update by downloading the latest zip version of your PluginBuddy plugin from your Member's panel and then
***Overwrite your existing plugin directory via FTP with the new files.
***De-activate the existing plugin, delete it via your '''WordPress --> Plugins''' area and then upload the newly downloaded zip file. Then re-activate the plugin.
**That will remove the issue completely.
*DETACH the key and then RE-ATTACH the license key for the specific site in question IF licensing still shows issues AFTER manually upgrading to the latest version of the plugin in question (check your Member's area for the latest version download)
*Also make sure to DETACH the key, DELETE that same AND any other keys related to that specific site from the entire licenses area, and then GENERATE a new key for that site IF detaching and re-attaching the license key does not work AFTER manually upgrading (for example, manually upgrading to the latest BackupBuddy version - all plugins have their own latest version numbers - check your Member's area for the latest version download)

[http://ithemes.com/forum/index.php?/topic/6691-read-this-first-pluginbuddy-licensing-issues/page-2/#p85977 First reports]

PluginBuddy

2012-04-19T19:19:57Z

Bes: Added http://ithemes.com/forum/topic/26635-error-message-invalid-license-key/page__view__findpost__p__123839 example /* Licenses Issues due to Plugin Conflicts */

Welcome to the PluginBuddy Knowledge Base - Tutorials, Technical Information, Debugging Information, and more.

=Premium Plugins=
* [[Ajax-Edit-Comments]]
* [[BackupBuddy]]
* [[DisplayBuddy]]
** [[Accordion]]
** [[Billboard]]
** [[Carousel]]
** [[CopiousComments]]
** [[FeaturedPosts]]
** [[Rotating Images]]
** [[RotatingText]]
** [[Slides]]
** [[Slideshow]]
** [[Tipsy]]
** [[VideoShowcase]]
* [[EmailBuddy]]
* [[Frolic]]
* [[LoopBuddy]]
* [[Mobile]]
* [[TailoredLogin]]
* [[ThumbsUp]]
* [[VidEmbed]]

=Free Plugins (active)=
* [[Featured Text]]
* [[PB-Tweet]]
* [[ServerBuddy]]
* [[Tabber Widget]]
* [[ThemeMan]]
* [[S3 URLS]]
* [[YOURLS]]
* [[ContactBuddy]]

=Free Plugins (inactive)=
* [[WP Easy Uploader]]
* [[WP Developer Assistant]]
* [[Easy Theme and Plugin Updater]]
* [[Current Date & Time Widget]]

''[[:Category:PluginBuddy|View all PluginBuddy Wiki Pages]]''

=Misc. Documentation=
==Frequently Asked (Plugin) Questions==
*[[General Plugins FAQ]]

==License Manager Tutorial and Information==
*[[License Manager]]
==PHP Development & Advanced==
*[[.htaccess]]
*[[PHP]]
*[[Arrays]]

[[Category:PluginBuddy]]

=Translations (localization / internationalization)=

Many PluginBuddy plugins come with translation capability. That means such PluginBuddy plugins can be translated (aka localized) to other languages.

===How Translations Work===

PluginBuddy provides the capability to have a translation in such plugins. Anyone wanting to enhance PluginBuddy with specific language translations can do so voluntarily via Translation Files. Translation Files are simply language files created fully and solely by the volunteer community which use the already built in translation-capable features in many of the PluginBuddy plugins to allow such plugins to show text or outputs in different languages. Making PluginBuddy translation-capable is done by PluginBuddy. Creating, updating and sending in any language specific translation files to PluginBuddy is done by the volunteer community.

Anyone can create translation files, package them into the proper format and give PluginBuddy the final translated files that we will try to include in the next update for the plugin in question. We call such awesome people, who create or update the translation files and send us the full translation package files, '''Awesome Translator Volunteers''', and we are really thankful that they take the time to do such an awesome thing.

If you want to help us, you can translate any existing PluginBuddy plugin which supports internationalization (another way of saying localization or translation-capable) and then, once you're fully done, simply let us know in the forums the link to the final language files that we can directly save and simply try to include in any future updates for the plugin(s) in question.

===Tips on how to localize any PluginBuddy Plugin to any non-English language===

The following 9 tips can help you figure out how to approach translations, how to create translations, and how to send us the final translated file for any translation-capable PluginBuddy plugin:

*1 : Many of the PluginBuddy plugins are internationalized, meaning they have the capability to be translated, via actual external translation files, by any non-iThemes-staff Awesome Translator Volunteer who wishes such plugins to be translated to their language.
*2 : If a PluginBuddy plugin is currently not internationalized or you're not sure if it is, you can ask us in the [http://ithemes.com/forum Support Forums] and we'll let you know, or we'll have it included as a future translation feature request. After the translation capability is added to such a plugin, you can submit the actual translation file. Please remember though: we cannot help with creating, understanding or making any language translation files. Our Awesome Translator Volunteers do that voluntarily (you can too! keep on reading) and fully on their own.
*3 : There are MANY resources which teach you how to create and work with WordPress language files. Following are the official 3 directly by the WordPress community:
**1 : [http://codex.wordpress.org/WordPress_in_Your_Language WordPress in Your Language]
**2 : [http://codex.wordpress.org/Translating_WordPress Translating WordPress]
**3 : [http://codex.wordpress.org/I18n_for_WordPress_Developers What WordPress Localization in Plugins is mainly about]
*4 : Translations are sent in from volunteers from all over the world. As a courtesy, we sometimes package the actual language translation files (provided directly by the Awesome Translator Volunteers) in with the final product. If some translation is not included in the actual plugin even when the plugin has the capability to be translated, you can submit the final translation to us for consideration in the next update by posting on our forums OR you can include the translation in your own live or local WordPress install directly for your own use. More info on how to include your own language specific file for your own WordPress sites is in the resources listed in #3 above.
*5 : A translation included in with the final product does not guarantee the accuracy or quality of the translation. These files are from the Awesome Translator Volunteers, and correction of these files is also done by those Awesome Translator Volunteers.
*6 : If a translation is very inaccurate or incomplete, we can put out a request for a new translation from the volunteer community, or remove the translation from the packaged and final product. You can also let us know of any inaccuracies in any existing translation files by the Awesome Volunteers by providing us with the corrected final files. Please remember: we only accept final and full translation files that you yourself have already created or packaged properly. If you let us know only of the actual inaccuracies without providing the final correct files, we cannot make such changes ourselves to the translation files.
*7 : Unfortunately, PluginBuddy cannot work on, help with, create, nor make any updates to any specific translation files you may have, or may be working on, or want to work on. Our Awesome Volunteers do that and simply give us the final files for inclusion or consideration.
*8 : If you have corrections for any existing translation in form of final proper format translation files for an existing language, OR want to provide the final and proper translation files for a new language, please post a new thread in the appropriate product category in the [http://ithemes.com/forum/ PluginBuddy Support Forums] with the final translations files. If you have any support questions on how to create or make language specific translation files, or how translation files work, you can do so on the [http://wordpress.org/support/ WordPress forums], as such support questions are outside the scope of what PluginBuddy support guarantees with your iThemes membership.
*9 : Any final translation file provided by you (or any other Awesome Volunteer) on the support forums will then be saved and filed as a future enhancement request for the future updates of the plugin(s) in question. In your support forum thread, where you share the final complete translation files you inclusion, you can upload your files directly to the forums OR upload them somewhere and link to them in your support forum thread. We will then download and save such files. Remember please: we cannot guarantee looking inside such files or verifying that they are correct in any manner (because of so many languages in the world and so many possible language files everywhere).

Thank you SO MUCH for being interested in providing translation files for our PluginBuddy plugins. We hope you will become one of our Awesome Translator Volunteers, in addition to being our AWESOME CUSTOMER, and create/update any language-specific translation file package and provide it to us so that we can consider including it in future updates.

===Resources for understanding, creating, updating and submitting final translation files===
*Here are the 3 official resources again which you can use to create, update, start work on and finish translation on any of the translation-capable PluginBuddy plugins:
**1 : [http://codex.wordpress.org/WordPress_in_Your_Language WordPress in Your Language]
**2 : [http://codex.wordpress.org/Translating_WordPress Translating WordPress]
**3 : [http://codex.wordpress.org/I18n_for_WordPress_Developers What WordPress Localization in Plugins is mainly about]

=Extra Customizations=
While any extra customization of any PluginBuddy Plugin is beyond the scope of the official support, we do from time to time offer different tips and tutorials on editing the awesome PluginBuddy plugins to better fit your individual needs. All such edits are, however, beyond what is officially supported and provided in the actual plugin admin panel and officially stated features on the individual plugin pages. No official support is provided nor guaranteed in, before, during, after or related to anything resulting from any such edits/customizations.

No support is provided on any of these extra customizations. Any of the steps mentioned in any of these extra custom edits may change at any time depending on newer versions of the plugins being released. Any use or customization of anything, beyond what is provided by default inside the plugin admin menu, means you are proceeding at your own risk and that you accept 100% responsibility and liability for everything you change or modify in any manner in the plugin. Your purchase and use of any PluginBuddy plugin implies and shows that you are buying and using PluginBuddy plugin(s) the way it(they) came in their original unmodified form, with no exceptions.

*Remember:
**[http://pluginbuddy.com/purchase/backupbuddy/ Make a backup of your entire site with BackupBuddy] before making any edits!
** PluginBuddy only supports the official unedited, unmodified versions of all PluginBuddy plugins.
** Use a good text editor to make any file changes. Again, maintain backups!
** Any changes you make to files WILL MOST PROBABLY be lost when the plugin is upgraded to any newer version.
** You are 100% responsible and liable for anything resulting from any of these changes.
** No support is provided nor guaranteed on any of these extra changes in any form or shape, whatsoever, regardless of who suggested these custom edits or suggestions.
** Any extra customization info or suggestion is added voluntarily by PluginBuddy staff to help users as much as possible, even if such customization is outside the scope of any membership support.
** Whether a PluginBuddy staff or representative offered or suggested the edit/customization, another customer or anyone else, PluginBuddy does not officially support nor provide any official support on any such edits.
** We cannot guarantee providing any support on any edits or customization tips we provide.
** Absolutely no support is guaranteed in any manner on any of our free plugins, whether or not there is any customization/edit involved.

=External Plugins Compatibility=

PluginBuddy does not promise, guarantee or provide support for any compatibility with any external plugin. If any PluginBuddy Plugin works without any problems when used with any external plugin in question, that means the PluginBuddy Plugin is most probably working without any issues overall. PluginBuddy is not responsible for making PluginBuddy plugins work in any manner, whether custom, fully, fixed or other, with any external non-PluginBuddy plugins. PluginBuddy is also not responsible for providing any support whatsoever for any external plugin, whether or not such an external plugin is used along with any PluginBuddy plugin.

=Free Plugins=

Free plugins are provided as is. There is no guaranteed support that comes with them. Guaranteed support is limited only and mainly for our premium unmodified plugins.

=Bugs, Features and ETA on new updates=

With every new release of any plugin, there may be a new bug or two. You may also want to have new features added to specific plugins. All existing versions of all plugins can have bugs reported OR new features suggested. All of this is done via the [http://ithemes.com/forum official forums].

New updates are also usually released regularly and at the same time, at very different paces, depending on the current number of bugs, features, new plans and tasks at hand. Therefore it is the official policy that there is NO pre-defined ETA on any bug fix, feature imeplemention OR new update OR new plugin roll-out UNLESS otherwise specified specifically in writing somewhere by an official iThemes employee.

==Bugs, bug reports and bug fixes==

Bug reports are filed and noted as they are encountered (thanks for reporting them to us!). There is never any ETA on any bug fixes unless otherwise noted.

==Feature Requests==

Feature requests and feature suggestions are basically future suggested features that users can suggest, and/or future features PluginBuddy may consider adding to the future versions of the plugin(s) in question (again, thanks for suggesting new features!).

There is no guaranteed ETA on when such feature requests will be implemented, unless otherwise noted. All suggested features are just that: suggestions. They remain suggestions until they're confirmed as officially in the works and to be included. Even then, unless a feature is actually rolled out publicly, there is no guarantee any feature suggestion will be implemented. We do our best to try and accommodate as many feature suggestions as possible.

Also, there is no guarantee that any feature request suggested will be implemented, unless otherwise noted.

==ETA on new updates==

Just like bug fixes and new features, there is never a guaranteed date nor a guaranteed time frame on when new updates will roll out. We work every single day of the week, all the time, on our plugins and thus every day there is something new and improved happening in almost all our plugins daily. Whenever we are ready to release any new updates publicly, you'll find out by seeing the plugin update notice in your WordPress OR in your [http://ithemes.com/member/member.php Member's area].

=What does BETA mean?=

Some of PluginBuddy plugins may be in Beta status OR may have Beta features. BETA simply means that some feature or specific part of the plugin is currently still in testing mode, and can cause issues if not used properly. All BETA plugins/features are not yet 100% stable, and thus should NOT be relied on to be working properly OR working at all. Throughout the iThemes Codex, any time the word "Beta" is used in any form, it refers to Beta plugins, Beta features, Beta status and/or anything related to the Beta nature that is officially announced or mentioned as such by any iThemes staff or on any of the Plugin pages, or in this Codex.

Beta implies that any new features or plugins are very close to being released as 100% working very soon, and that there may still be some issues to fix or test more before removing the Beta status. Since no single software of any kind can be tested under every system and site configuration in the world, the Beta status enables the Beta features to be tested out by as many people on as many different websites and configurations as possible.

*Some points to keep in mind when using any BETA plugin/feature:
**1 : Make [http://pluginbuddy.com/purchase/backupbuddy/ FULL WordPress backups] before using ANY beta feature.
**2 : Beta means that the current software feature is NOT complete, and that you are NOT forced to use such a feature at all. You are advised to WAIT until the BETA status is removed.
**3 : Using any Beta feature of any kind, whether it is an entire plugin or something inside a plugin, means and shows that you are fully accepting any liability for any risks involved.
**4 : Using any Beta feature of any kind, whether it is an entire plugin or something inside a plugin, means and shows that you are fully aware that there are all different kinds of risks involved with such features.
**5 : If you are concerned about your important data or anything bad that might happen as a result of using any Beta feature, do NOT use such Beta features.
**6 : ALWAYS make full [http://pluginbuddy.com/purchase/backupbuddy/ BackupBuddy Backups of all your important data] before using any Beta software, whether that Beta software is from PluginBuddy or from any other place.
**7 : If any issues are found in Beta, they are usually added to the list of bug fixes to be released as a whole, or for the next big update, instead of being updated OR fixed individually on a case by case basis.
**8 : Beta features are recommended to test and play with on test sites/servers and configurations with any dummy data, as long as you have [http://pluginbuddy.com/purchase/backupbuddy/ full backups of all important data] still.
**9 : iThemes is not liable nor cannot be held accountable for any unwanted results resulting from the use of BETA features.
**10 : The very name and nature of BETA shows clearly, without any doubt, that there will most probably be issues and problems involved when such labeled features are used anywhere.
**11 : Support for Beta features may be very limited. We usually simply collect all reports related to Beta features and collect them all for one big update in the future.
**12 : If you lose any important data or settings anywhere, or encounter damaged data or settings anywhere, because of any Beta feature, we will not be able to help you and will simply tell you to revert to your previous [http://pluginbuddy.com/purchase/backupbuddy/ backups]. We will also tell you to always wait for BETA status to be removed before using any such features.

If you do not fully understand what Beta means, OR are not willing to fully accept and be fully liable for any risks involved because of using such Beta software, you should NOT use the Beta software in any manner. In such a case, you should simply wait until the Beta status is removed.

*[http://pluginbuddy.com/what-does-beta-mean/ Blog post announcing what BETA means]

=PluginBuddy Licenses=

In unusual cases, you may run into some of the following licensing issues or errors. The possible solutions are listed below in their own separate sections:

*Error Messages
**'''You have already generated all the keys you have available or your licenses have expired. Please obtain additional licenses or unlicense a site. ERROR L14513-JW.'''

==Licenses Issues due to Plugin Conflicts==

Some times, external plugins may cause issues in detaching, deleting, generating OR saving license keys. Such plugins may also cause issues when you want to manually or automatically upgrade plugins when you try to solve licensing issues.

Following is a list of currently known plugins which cause license detaching, deleting, generating OR saving issues. Please disable the following plugins, even temporarily, while you perform all the steps of manually OR automatically upgrading the PluginBuddy plugins in question, and detaching, deleting, generating and saving license keys for them. Keep such plugins disabled UNTIL all license key issues are gone OR at least while you perform these steps.

*Plugins causing PluginBuddy licensing issues
**'''W3 Total Cache or WP Super Cache or WinCache :''' If you are using any caching plugin like '''W3 Total Cache''' or '''WP Super Cache''' or any PHP Extension like WinCache, please disable it temporarily and then carry out any required steps. You can re-enable the plugin or extension in the end after everything works in terms of the licenses.
***Fix: Follow the above steps to fix this issue. [http://ithemes.com/forum/index.php?/topic/19436-backupbuddy-license-issue/#p92171 Steps also explained by BackupBuddy customer Laura (thanks!)]
**'''Any other CACHING or related plugin or extension:''' Try disabling such plugins/extensions, performing the required steps, and then re-activating the Caching or related plugins/extensions in question.

*Related Links
**1 : [http://ithemes.com/forum/topic/26635-error-message-invalid-license-key/page__view__findpost__p__123839 whitewolf deactivated W3 Total Cache, which got rid of the Licensing errors]
**2 : [http://ithemes.com/forum/topic/24881-license-key-is-not-set-yet-or-invalid/page__view__findpost__p__116047 blm03 deactivated W3 Total Cache, which allowed the licenses to save correctly]
**3 : [http://ithemes.com/forum/topic/26022-cant-generate-a-license-for-my-domain/page__view__findpost__p__121072 Disabling WinCache extension for PHP fixes Licensing issues]
**4 : [http://ithemes.com/forum/topic/24737-backupbuddy-manage-licenses/page__view__findpost__p__115187 Karlos deactivated W3 Total Cache, and that fixed the licensing issues]
**5 : [http://ithemes.com/forum/topic/23481-license-issue-pluginbuddy-developer-to-backupbuddy-both-unlimited/page__view__findpost__p__110368 Disabling W3 Total Cache modules allowed Greg to license BackupBuddy without any issues]
**6 : [http://ithemes.com/forum/topic/23275-unable-to-get-license-to-stick/page__pid__109503#entry109503 W3 Total Cache causing licenses to be deleted after a while]
**7 : [http://ithemes.com/forum/topic/22964-cant-find-stylesheet-to-make-adjustments-to-slider/page__view__findpost__p__107933 W3 Total Cache not allowing licenses to be saved properly]
**8 : [http://ithemes.com/forum/topic/22859-bub-licenses-not-taking-effect/page__view__findpost__p__107476 W3 Total Cache not allowing licenses to be saved - easy solution!]
**9 : [http://ithemes.com/forum/index.php?/topic/19079-wont-let-me-set-a-license-key/#p91663 W3 Total Cache plugin conflict and solution]
**10 : [http://ithemes.com/forum/index.php?/topic/19436-backupbuddy-license-issue/#p92171 W3 Total Cache plugin conflict and solution]
**11 : [http://ithemes.com/forum/index.php?/topic/20228-key-does-not-work/#p95697 W3 Total Cache plugin conflict and solution]
**12 : [http://ithemes.com/forum/index.php?/topic/19041-license-problem-causes-loss-of-all-bb-settings-way-to-get-them-back/ WP Super Cache conflict and solution]

==Licensing issues due to different Membership/Account scenarios==

You may run into licensing issues if something unexpected is happening in or to your membership/accounts.

*Having '''multiple accounts''' with the '''same e-mail address'''.
**If you have more than one account with iThemes and use the same e-mail address with all (or more than one of) your accounts, you may run into the following error:
*** '''You have already generated all the keys you have available or your licenses have expired. Please obtain additional licenses or unlicense a site. ERROR L14513-JW'''
**One solution is to have your accounts combined by contacting sales.
**Another solution is to make sure you associate each account with a different e-mail address.
*** [http://ithemes.com/forum/topic/26420-bought-2-site-license-used-on-1-site-cant-generate-key-for-2nd-site/ User having 2 accounts with the same e-mail, getting ERROR L14513-JW, and resolving the issue by making sure their 2 accounts have 2 separate e-mail addresses]

==Other Steps to Resolve Licensing Issues==

There are some reports that some users have issues with their license insides the Licenses area of different PluginBuddy plugins, including BackupBuddy.

Remember: All your PluginBuddy plugins, including BackupBuddy, will CONTINUE WORKING PERFECTLY even with these licensing issues. You can keep using the plugins exactly how you want them even during these licensing issues. Your plugins are NOT affected by this licensing situation in any manner.

Your membership is also completely fine and you have NOT lost any license(s). The issue is happening to some customers who simply need to upgrade manually to the latest version of their plugin, if the automatic upgrade does not work.

*Plugins with the update versions which remove this issue completely
**ALL PluginBuddy Products

*You can upgrade via one of the following:
**Automatically upgrade to the latest version
**Manually update by downloading the latest zip version of your PluginBuddy plugin from your Member's panel and then
***Overwrite your existing plugin directory via FTP with the new files.
***De-activate the existing plugin, delete it via your '''WordPress --> Plugins''' area and then upload the newly downloaded zip file. Then re-activate the plugin.
**That will remove the issue completely.
*DETACH the key and then RE-ATTACH the license key for the specific site in question IF licensing still shows issues AFTER manually upgrading to the latest version of the plugin in question (check your Member's area for the latest version download)
*Also make sure to DETACH the key, DELETE that same AND any other keys related to that specific site from the entire licenses area, and then GENERATE a new key for that site IF detaching and re-attaching the license key does not work AFTER manually upgrading (for example, manually upgrading to the latest BackupBuddy version - all plugins have their own latest version numbers - check your Member's area for the latest version download)

[http://ithemes.com/forum/index.php?/topic/6691-read-this-first-pluginbuddy-licensing-issues/page-2/#p85977 First reports]

LoopBuddy

2012-04-16T17:44:30Z

Bes: Added info/link to explain how to Import and Export Queries and Layouts./* Example Queries/Layouts */

'''Release date:''' July 19, 2011

==LoopBuddy Overview==

LoopBuddy is a tool that overwrites a WordPress Loop using a combination of a custom query and a custom Loop layout. You can also create your own Loops using the LoopBuddy shortcode and LoopBuddy widget.

===Query Editor===

If LoopBuddy was a body, the Query Editor would be the brain, with the Layout Editor being the outside bodily appearance.

[[File:Query_editor.png|400px|border|LoopBuddy Query Editor]]

With the Query Editor, you can create Query Groups. Each Query Group defines what data a WordPress Loop is supposed to pull in.

With the Query Editor, you can define:

* Which posts to gather
* Whether pagination or comments are enabled
* Whether to use the default post ID (if on a single post or page)
* and much, much more...

[[File:Query_editor_options.png|400px|border|Query Editor Options]]

===Layout Editor===

The Layout Editor controls how a particular WordPress Loop is supposed to be structured. At the heart of the Layout Editor is Layout Tags. There are several Layout Tags built-in, but you can use the LoopBuddy Hooks to create your own custom Layout Tag and Layout Tag Items.

[[File:Layout_editor.png|400px|border|LoopBuddy Layout Editor]]

With the Layout Editor, simply drag Layout Tags into the appropriate area. If you create a new Layout, there are several default tags that are added automatically.

[[File:Layout_editor_options.png|500px|border|Layout Editor Options]]

===Global Settings===

The Global LoopBuddy Settings allow you to globally override a default WordPress Loop. If your theme doesn't support the Loop Standard, you'll see an error message at the top.

If your theme does support the Loop Standard, you can use the options to override the default WordPress Loops in various areas of the site.

Although LoopBuddy attempts to work without a custom Query, it is highly advisable to use a custom Query and Layout.

[[File:Loopbuddy_settings.png|500px|border|General Settings]]

===Import/Export===

Within the Query and Layout lists pages, you can export/import the items so you can use the same Queries/Layouts on a different site.

This is the same page as where you create new Queries or Layouts.

===LoopBuddy Widget===

You can use the LoopBuddy Widget to display a LoopBuddy Query/Layout in any widgetized area of a site. Please note that you must have a Query AND a Layout for the widget to work.

===LoopBuddy Shortcode===

The LoopBuddy shortcode takes two attributes: a Query ID and a Layout ID. Please note that you must have a Query AND a Layout for the widget to work.

Simply insert the shortcode into a post or page:

<pre class='brush:php'>
[loopbuddy query_id='0' layout_id='0']
</pre>

===LoopBuddy Full 1 Hour Webinar===

Learn the ins and outs of LoopBuddy with the following 1 hour Webinar, made by our very own [http://www.webdesign.com Webdesign.com]
{{#ev:vimeo|26482158|580|363}}

==The Loop Standard==
The Loop Standard divides a loop into two main concepts: a loop and one or more entries.

Both a loop and an entry have three sections: a header, a content section, and a footer. The header contains title information, any meta information, and any necessary navigation links. The content section contains the content relevant to that loop or entry. The footer section is a place to hold additional or duplicate meta information and navigation links.

===The Loop Explained===

The content of a loop is a bit more complex than the content of an entry as a loop's content contains the entries. To better visualize this, here is the basic structure described so far:

* Loop
** Header
*** title
*** navigation
*** meta
** Content
*** Entry
**** Header
***** title
***** navigation
***** meta
**** Content
**** Footer
***** navigation
***** meta
*** Additional entries...
*** Footer
**** navigation
**** meta

The idea is that each section is broken out in a repeatable pattern. This makes styling easier as any content that follows this form can be styled without having to first read through the code in order to understand the structure.

You may notice that there are titles, navigation, and meta for both the entries and the loop. This is because some titles, navigation, and meta are relevant to the loop (the title archive, navigating between pages of posts, or information about an author in an author archive) while other titles, navigation, and meta are relevant to the entry (the blog post's title, navigating through a page split into multiple pages, or a blog post's category information). The rule of thumb is that if the information is specific to an individual post's, page's, etc content, it is an entry-level structure; otherwise, it is a loop-level structure.

Each of these sections have a specific class in the Loop Standard. Here is the structure again with the classes replacing the names:

* loop
** loop-header
*** loop-title
*** loop-utility
*** loop-meta
** loop-content
*** hentry
**** entry-header
***** entry-title
***** entry-utility
***** entry-meta
**** entry-content
**** entry-footer
***** entry-utility
***** entry-meta
*** hentry...
** loop-footer
*** loop-utility
*** loop-meta

Notice the "hentry" class. This looks odd but is actually generated by WordPress internally. It is produced by the <code>post_class()</code> function that is in 2010 and 2011 theme template files. So when you see "hentry", know that this is simply the div that looks like :

<pre class='brush:php'>
<div <?php post_class(); ?>></div>
</pre>

Here is the standard loop in practice:
* loop
** loop-header
*** loop-title (page-title)
** loop-content
*** hentry
**** entry-header (title)
***** entry-title (post-title)
***** entry-meta (post-meta)
***** entry-meta date (date)
**** entry-content (post-content)
**** entry-footer (meta-bottom)
***** entry-meta alignright (alignright)
***** entry-meta alignleft (meta-bottom-left)
*** hentry...
** loop-footer
*** loop-utility (paging)

Not all the elements from above structure examples were used since not all were needed. In the end, only three elements had to be added. The rest of the changes were simply modifying or adding classes to conform to the Loop Standard structure. For some elements, such as "date", the "date" class remained while also getting the "entry-meta" class. This makes it clear what type of structure it is while still giving the additional meaning of it being a container for the date.

===Modifying a Theme to Use LoopBuddy===

Here's an example of TwentyTen's index.php file before it begins loading the various templates:

<pre class='brush:php'>
<?php if ( ! dynamic_loop() ) : ?>
<div class="loop">
<?php
/* Run the loop to output the posts.
* If you want to overload this in a child theme then include a file
* called loop-index.php and that will be used instead.
*/
get_template_part( 'loop', 'index' );
?>
</div>
<?php endif; ?>
</pre>

When <code>dynamic_loop()</code> is executed, LoopBuddy searches to see if this particular loop should be overridden. If not, the normal loop executes. If so, then LoopBuddy overwrites the content of the loop with LoopBuddy content.

===Example of TwentyTen Using the Loop Standard===
Here's an example TwentyTen Loop converted to using the Loop Standard

<pre class='brush:php'>
<?php if ( have_posts() ) while ( have_posts() ) : the_post(); ?>

<div class="loop-content">
<div id="nav-above" class="navigation loop-utility loop-utility-above">
<div class="nav-previous"><?php previous_post_link( '%link', '<span class="meta-nav">' . _x( '←', 'Previous post link', 'twentyten' ) . '</span> %title' ); ?></div>
<div class="nav-next"><?php next_post_link( '%link', '%title <span class="meta-nav">' . _x( '→', 'Next post link', 'twentyten' ) . '</span>' ); ?></div>
</div>

<div id="post-<?php the_ID(); ?>" <?php post_class(); ?>>
<div class="entry-header">
<h1 class="entry-title"><?php the_title(); ?></h1>

<div class="entry-meta">
<?php twentyten_posted_on(); ?>
</div>
</div>
<div class="entry-content">
<?php the_content(); ?>
<?php wp_link_pages( array( 'before' => '<div class="page-link">' . __( 'Pages:', 'twentyten' ), 'after' => '</div>' ) ); ?>
</div>
<div class="entry-footer">
<?php if ( get_the_author_meta( 'description' ) ) : // If a user has filled out their description, show a bio on their entries ?>
<div id="entry-author-info" class="entry-meta entry-meta-below">
<div id="author-avatar">
<?php echo get_avatar( get_the_author_meta( 'user_email' ), apply_filters( 'twentyten_author_bio_avatar_size', 60 ) ); ?>
</div>
<div id="author-description">
<h2><?php printf( esc_attr__( 'About %s', 'twentyten' ), get_the_author() ); ?></h2>
<?php the_author_meta( 'description' ); ?>
<div id="author-link">
<a href="<?php echo get_author_posts_url( get_the_author_meta( 'ID' ) ); ?>">
<?php printf( __( 'View all posts by %s <span class="meta-nav">→</span>', 'twentyten' ), get_the_author() ); ?>
</a>
</div>
</div>
</div>
<?php endif; ?>

<div class="entry-utility">
<?php twentyten_posted_in(); ?>
<?php edit_post_link( __( 'Edit', 'twentyten' ), '<span class="edit-link">', '</span>' ); ?>
</div>
</div>
</div>
<div class="loop-footer">
<div id="nav-below" class="navigation loop-utility loop-utility-below">
<div class="nav-previous"><?php previous_post_link( '%link', '<span class="meta-nav">' . _x( '←', 'Previous post link', 'twentyten' ) . '</span> %title' ); ?></div>
<div class="nav-next"><?php next_post_link( '%link', '%title <span class="meta-nav">' . _x( '→', 'Next post link', 'twentyten' ) . '</span>' ); ?></div>
</div>
</div>

<?php comments_template( '', true ); ?>
</div>

<?php endwhile; // end of the loop. ?>

</pre>

After updating the template files, go through the theme's style.css file in order to update class references to match the new ones. Here are some basic replacements to make:

* .page-title → .loop-title
* .title → .entry-header
* .post-title [h1, h2, h3, etc] (any instance of .post-title followed by a header tag) → .entry-title
* .post-title → .entry-title
* .post-meta → .entry-meta
* .post-content → .entry-content
* .meta-top → .entry-header
* .meta-bottom → .entry-footer
* .post → .hentry
* .paging → .loop-utility

===Showing LoopBuddy Theme Support===

After you've modified your theme's loops, show LoopBuddy that your theme supports it by adding in the following line to your theme's functions.php file:

<pre class='brush:php'>
// Add support for the Loop Standard
add_theme_support( 'loop-standard' );
</pre>

===Adding the Dynamic Loop Function to Your Theme===
The Dynamic Loop function must be added to your theme's functions.php file. This is achieved by adding the following code to the end of the function.php file:

<pre class='brush:php'>
// Add dynamic_loop function for LoopBuddy

/*
Copyright 2011 iThemes (email: support@ithemes.com)

Written by Chris Jean
Version 0.0.1

Version History
0.0.1 - 2011-02-28 - Chris Jean
Initial version
*/

if ( ! function_exists( 'dynamic_loop' ) ) {
function dynamic_loop() {
global $dynamic_loop_handlers;

if ( empty( $dynamic_loop_handlers ) || ! is_array( $dynamic_loop_handlers ) )
return false;

ksort( $dynamic_loop_handlers );

foreach ( (array) $dynamic_loop_handlers as $handlers ) {
foreach ( (array) $handlers as $function ) {
if ( is_callable( $function ) && ( false != call_user_func( $function ) ) ) {
return true;
}
}
}

return false;
}
}

if ( ! function_exists( 'register_dynamic_loop_handler' ) ) {
function register_dynamic_loop_handler( $function, $priority = 10 ) {
global $dynamic_loop_handlers;

if ( ! is_numeric( $priority ) )
$priority = 10;

if ( ! isset( $dynamic_loop_handlers ) || ! is_array( $dynamic_loop_handlers ) )
$dynamic_loop_handlers = array();

if ( ! isset( $dynamic_loop_handlers[$priority] ) || ! is_array( $dynamic_loop_handlers[$priority] ) )
$dynamic_loop_handlers[$priority] = array();

$dynamic_loop_handlers[$priority][] = $function;
}
}

</pre>

==LoopBuddy Downloads==

===Example TwentyEleven Theme===

Here's an example TwentyEleven theme that has been modified to be compatible with LoopBuddy.

[[Media:twentyeleven-loopstandard.zip|TwentyEleven Loop Standard]]

===Example Layout Tag===

Check out the LoopBuddy Marquee Plugin: [[Media:Loopbuddy_marquee.zip|LoopBuddy Marquee]] as an example of creating custom tags.

===Example Queries/Layouts===

Please see below for a ZIP file of some sample layouts and queries that can be imported.

[[Media:Loopbuddy_export.zip|LoopBuddy Export File]]

You can import any Query or Layout into LoopBuddy via the [[#Import/Export|Import/Export]] section.

==LoopBuddy Query==
The LoopBuddy Query is where you create Queries, which in turn create and produce the Loops you want in WordPress. From showing certain posts to the number of posts, categories, posts with specific meta values and more, the '''LoopBuddy Query''' area is where you specify exactly what should be shown, and exactly what should not be shown, in a LoopBuddy output.

===Advanced Meta Queries===

With LoopBuddy 1.2, LoopBuddy Queries now allow you to perform some very powerful advanced Meta queries. Here is a video explaining and giving some examples of the advanced meta queries:

{{#ev:youtube|4snQn7PDylE|580|363}}
*[http://pluginbuddy.com/loopbuddy-1-2-released/ Blog Post announcing Advanced Meta Queries in LoopBuddy 1.2]

===Advanced Taxonomy Queries===

With LoopBuddy 1.2, LoopBuddy Queries now allow you to perform some very powerful advanced Taxonomy queries. Here is a video explaining and giving some examples of the advanced Taxonomy queries:

{{#ev:youtube|ta0GZA5jz9g|580|363}}
*[http://pluginbuddy.com/loopbuddy-1-2-released/ Blog Post announcing Advanced Taxonomy Queries in LoopBuddy 1.2]

==Hooks==

LoopBuddy allows you to create custom tags for the Layout editor. This is advanced functionality, so please don't attempt these steps if you are not intimately familiar with PHP and how LoopBuddy operates.

To create the custom tag, you must use the following hooks.

===Creating a new Custom Tag===

<pre class="brush:php">
<?php
add_filter( 'pb_loopbuddy_custom_tags', 'my_custom_tag_add' );
function my_custom_tag_add( $custom_tags ) {
//Always return $custom_tags
$custom_tags[ 'start_wrap' ] = array(
'My Tag Label',
array(
'wrap' => 'div',
'custom_class' => 'default class'
)
);
return $custom_tags;
} //end my_custom_tag_add

//Start off with the tag name, give the tag a label, and pass it which items it supports (all should ideally contain the 'wrap' and 'custom_class' items
?>
</pre>

Here are some built in tag items that you can choose from:

* link_text
* custom_url
* custom_class
* link_title
* before_text
* after_text
* meta_key
* max_width
* max_height
* shortcode
* author_link_destination
* user_profile
* permalink
* attachment_link_display
* separator
* text
* date_format
* comment_number_zero
* comment_number_one
* comment_number_more
* post_date
* bloginfo
* content_more
* url_display
* image_size

===Creating a new custom tag item===

<pre class='brush:php'>
<?php
add_filter( 'pb_loopbuddy_tag_items', 'my_custom_item_add' );
function my_custom_item_add( $loopbuddy_items ) {
//Always return $loopbuddy_items

$loopbuddy_items[ 'my_custom_item' ] = array(
'function' => 'callback_function',
'args' => array(
'label' => __( 'Link Text', 'LION' ),
'tip' => __( 'Optional text for link. Leave blank to use link as the text.', 'LION' ),
'options' => array( 'option1', 'option2' )
)
);
return $loopbuddy_items;
} //end my_custom_item_add

/* $settings are the arguments passed for the tag item and looks like this
[label] => HTML Wrapper
[tip] => Choose which HTML element to wrap around the item
[options] => Array
(
[0] => none
[1] => span
[2] => div
[3] => p
[4] => h1
[5] => h2
[6] => h3
[7] => h4
[8] => h5
[9] => h6
)

[key] => wrap
[settings] => Array
(
[image_size] => thumbnail
[max_width] =>
[max_height] =>
[wrap] => p
[before_text] =>
[after_text] =>
[custom_url] =>
[custom_class] => attachment
[tag] => wp_get_attachment_image
)

)
*/
function callback_function( $settings ) {
$defaults = array(
'key' => '',
'label' => '',
'tip' => false,
'settings' => array(),
'options' => array()
);
extract( wp_parse_args( $settings, $defaults ) );
//Output HTML for the item
} //end callback_function

?>
</pre>

===Callback function for displaying the tag - pb_loopbuddy_tag_callback-{tag_name}===
<pre class='brush:php'>
<?php
/*$settings contains the tag items and the tag item's value
Example
Array
(
[image_size] => thumbnail
[max_width] =>
[max_height] =>
[wrap] => p
[before_text] =>
[after_text] =>
[custom_url] =>
[custom_class] => attachment
[tag] => wp_get_attachment_image
)
*/

//Add header code
add_action( 'pb_loopbuddy_tag_header-mytagname', 'my_custom_tag_header' );
function my_custom_tag_header( $settings ) {
echo "my header, notes, or other code";
//Render your tag based on its settings
} //end my_custom_tag_header

//Add footer code
add_action( 'pb_loopbuddy_tag_footer-mytagname', 'my_custom_tag_footer' );
function my_custom_tag_footer( $settings ) {
echo "my footer, notes, or other code";
//Render your tag based on its settings
} //end my_custom_tag_header

add_filter( 'pb_loopbuddy_tag_supports-mytagname', 'my_custom_tag_supports' );
//Return an array of what tag items the tag supports
function my_custom_tag_supports( $support_tag_items ) {
return array( 'wrap', 'link_text', 'before_text', 'after_text', 'custom_class' );
//Render your tag based on its settings
} //end my_custom_tag_supports
?>
</pre>

===Rendering the Tag on the Front-end - pb_loopbuddy_render-{tag_name}===

<pre class="brush:php">
<?php
add_filter( 'pb_loopbuddy_render-mytagname', 'mytagname_frontend', 10, 2 );
function mytagname_frontend( $post_object, $tag_items ) {
/* $tag_items look like this
(
[wrap] => none
[link_text] => Edit Post
[before_text] =>
[after_text] =>
[custom_url] =>
[custom_class] =>
[tag] => edit_post_link
)
*/
$return = false; //Populate the $return variable
$return = pluginbuddy_loopbuddy_render_slotitems::get_output( $return, $post_object, $tag_items, true ); //The last argument is skip_before text
return $return;
} //end mytagname_frontend
?>
</pre>

===Ignoring Post Types in the Layout Editor===

There will be certain post types that are public and have a public user interface, but the user would still not like to be able to configure override settings in the LoopBuddy Settings page.

A plugin author can use the following hook to remove these post types:

<pre class="brush:php">
<?php
add_filter( 'pb_loopbuddy_exclude_post_types', 'myplugin_exclude_post_types' );
function myplugin_exclude_post_types( $post_types_to_exclude ) {
$post_types_to_exclude[] = 'my_custom_post_type';
return $post_types_to_exclude;
}
?>
</pre>

==Shortcodes==

Shortcodes basically allow almost any plugin or custom code to be plugged in anywhere in WordPress.

LoopBuddy supports shortcodes fully, allowing you to put any shortcode, whether from a plugin or your own, into any place in LoopBuddy Layout, including the '''Pre-Loop Text / HTML''', '''Post-Loop Text / HTML''' and '''No Results Text / HTML''' sections. This probably makes the already powerful LoopBuddy the only most powerful way to control all your content, loops and display on your site.

[http://ithemes.com/codex/page/General_WordPress_Related#Editing_or_Adding_Stuff_to_Functions.php Info on editing or adding stuff to Functions.php]

===Show Category/Taxonomy Description on NON-Archive pages via Shortcode===

Category Descriptions are a little more sophisticated than other post related variables because if there is more than one category being used, then it will be hard for WordPress to display ALL descriptions nicely OR one category (which one?).

*Outside of archive pages, to display Category Descriptions (or any taxonomy description) you have to do the following:
**1 : Put the following anywhere (usually near the end of the file) in your theme's custom functions.php file (it creates a shortcode you'll use to display the description of a Category or any Taxonomy):
<pre class="brush:php">add_action( 'init', 'lb_cat_init' );
function lb_cat_init() {
add_shortcode('taxdescription', 'lb_the_description');
} //end lb_cat_init
function lb_the_description() {
global $post;
if ( !is_object( $post ) ) return;
$terms = get_post_meta( $post->ID, 'description_terms', true );
$taxonomy = get_post_meta( $post->ID, 'description_taxonomy', true );
$return = '';
if ( $terms && $taxonomy ) {
if ( !is_array( $terms ) ) {
$terms = explode( ',', $terms );
}
foreach ( $terms as $term_name ) {
$term = get_term_by( 'slug', $term_name, $taxonomy );
if ( !$term ) continue;
$description = get_term_field( 'description', $term->term_id, $term->taxonomy );
if ( empty( $description ) || !$description ) continue;
$return .= apply_filters( 'pb_the_content', $description );
}
}
return $return;
} //end lb_the_description</pre>
**2 : In the posts you want to show the category description, add the following 2 custom field names and values:
'''Custom Field Name''' ----- '''Custom Field Value'''

description_taxonomy ----- category

description_terms ----- books '''''(OR any category name you have)'''''

**3 : Add a Shortcode Tag to your LoopBuddy layout which has the following shortcode in it:

<code><strong>[taxdescription]</strong></code>

That will show the category description anywhere you put the shortcode.

*Links with related info:
**[http://ithemes.com/forum/index.php?/topic/18153-use-of-category-description/ Use of Category Description - LoopBuddy Forums]
**[http://codex.wordpress.org/Function_Reference/category_description category_description on WordPress Codex]
**[http://codex.wordpress.org/Function_Reference/term_description term_description on WordPress Codex]

===Show Custom Page Title for Same LoopBuddy Layout on Different Pages via Shortcode===

*One awesome example of using Shortcodes with LoopBuddy is to show a custom page title, along with any LoopBuddy Layout content, where different pages use the same LoopBuddy Layout. Our awesome LoopBuddy customer Bruce provided the following info to help you all with that:
**1 : Put the following anywhere (usually near the end of the file) in your theme's custom functions.php file:
<pre class="brush:php">
function return_title() {
return '<h1>'.get_the_title().'</h1>';
}
add_shortcode('pg_title', 'return_title');</pre>
**2 : Add
<code><strong>[pg_title]</strong></code>

anywhere in the LoopBuddy Layout where you want to show the custom page title.

That will show the custom page title just for that specific post/page where the Layout is being shown.
*Related links:
**[http://ithemes.com/forum/index.php?/topic/18046-displaying-the-page-title-on-which-i-am-using-loop-buddy/ LoopBuddy user Bruce asking about and then sharing the code to show custom Page Titles on each Page where the same LoopBuddy Layout is used]

==External Plugins Compatibility==

LoopBuddy is one of those rare plugins which can play well with many external plugins. However, any external plugin compatibility is NOT guaranteed in any manner, since external plugins are not covered nor supported by PluginBuddy in any manner or fashion.

If there is a problem when any other plugin is used with LoopBuddy, it does not mean there is a bug in LoopBuddy. First you should check if there is a problem in the other plugin (since LoopBuddy already currently works without any issues in each and every aspect of its publicized features). Then you have to see if the problem exists when the other plugin is de-activated and LoopBuddy is kept activated. Only after such steps and more analysis can we at PluginBuddy devote any time or resources to see whether or not there is something in LoopBuddy that can be fixed, enhanced or improved to make it work better with the external plugin in question, if that external plugin is not the source of the problem.

===Custom Post Types===
At this time, Custom Post Types UI is the only supported plugin in LoopBuddy for creating custom post types. We recommend you try and use that to create post types.

Otherwise, you should add custom post types directly to your functions.php file in your current theme.

*Related links
**[http://wordpress.org/extend/plugins/custom-post-type-ui/ Custom Post Types UI plugin]
**[http://codex.wordpress.org/Post_Types Creating Post Types in WordPress]

===Page Navigation===

At this time, WP-PageNavi is the only supported plugin in LoopBuddy for having custom page navigation. We strongly recommend you try it for any of your custom page navigation needs.

*Related link
**[http://wordpress.org/extend/plugins/wp-pagenavi/ WP PageNavi WordPress Plugin]

===Customize Excerpts===

At this time, Advanced Excerpt is the only supported plugin in LoopBuddy for allowing custom lengths and formatting for excerpts in WordPress.

*Related link
**[http://wordpress.org/extend/plugins/advanced-excerpt/ Advanced Excerpt WordPress Plugin]

==LoopBuddy FAQ==

Here are some frequently asked or encountered LoopBuddy questions and setups, and their answers.

===Sort Custom Field Values by Meta Value (Character or Numeric)===

*Custom Field values can be sorted by meta value (character or numeric).
*Only ONE meta item can be used to sort at one time.
**Using multiple meta items will assume you would like an advanced meta query, and sorting will be ignored in such a case. '''This is a WordPress limitation.'''
*Sort Custom Field Values via the following steps (assuming you already have several posts with the same custom field):
**1 : Change the Order By parameter to either "'''Meta Value'''" or "'''Numeric Meta Value'''".
**2 : Go to Post Meta Parameters and click "'''Add Meta'''".
**3 : Set the '''Meta Key''' and '''Meta Values''' you would like to search for and sort by.
**4 : Save the query.
**5 : Assign the query to a post or section and observe the results.

===LoopBuddy does not work on static Posts page===

*LoopBuddy will NOT work on pages set as Static Posts Page in '''WordPress --> Settings --> Reading --> Front Page Displays --> Posts Page''' section. There is a good reason for it and a great workaround.
** Reason
***The Reading Screen in the WordPress Settings [http://codex.wordpress.org/Settings_Reading_Screen Settings --> Reading Screen Settings] is necessary when you want to tell WordPress that your blog content doesn't reside on the home page.
***For example, you have selected a Front Page, which will tell WordPress, "Use this page instead of showing a default blog layout."
***Since there is technically no longer a blog layout, WordPress wants to know, "Where can I find your blog content?"
***This is how WordPress works, and not a LoopBuddy bug. There is a great flawless way to get exactly what you want with the below workarounds, though.
**Workaround (any one of this will work - we recommend the PREFERRED LoopBuddy way to do it!)
*** Not have a section on your site with your blog content (readers will only be able to access your posts via category and date archives).
*** Create a page to point WordPress to, and WordPress will take care of the rest and display the appropriate blog content.
*** '''PREFERRED:''' With LoopBuddy, however, you don't have to specify a "Blog" section in WordPress.
**** You can create a regular page.
**** Allow LoopBuddy to create a blog section for you either via '''LoopBuddy --> Settings''' option OR by choosing the '''LoopBuddy options in the Post/Page Editor page''' for the page you just created.
**** WordPress doesn't need to know about it in this particular case, and it won't hurt your site in the least. You do NOT have to change the '''WordPress --> Settings --> Reading --> Front Page Displays --> Posts Page''' settings for this option to work perfectly.
*Threads and pages with more detailed info of the setup and info related to the above exact solutions
**http://ithemes.com/forum/index.php?/topic/17845-unable-to-get-loopbuddy-working/
**http://codex.wordpress.org/Settings_Reading_Screen

===Make a Custom Field (or almost anything) Clickable===
With the power of different tags in LoopBuddy Layout, you can make almost anything clickable without editing a single file. This is extremely useful when you want to make something like a Custom Field, which is text by default, clickable automatically in any or every loop.
*Steps to perform in your LoopBuddy Layout:
**1 : Start with a Text tag (first Text tag) which has the content: <code><a href="</code>
**2 : Next comes anything, including a Custom Field tag. This is the link.
**3 : Now comes another Text tag (second Text tag) which has the content: <code>"></code>
**4 : Now comes anything to show the link. It can be the same Custom Field tag again as #2 above, another custom field, or any text or image you wish.
**5 : Another Text tag (3rd Text tag) with the following content: <code></a></code>
That's it!
*Related thread
**http://ithemes.com/forum/index.php?/topic/16971-text-before-single-custom-field-and-url/

===Search within a LoopBuddy Query===

You can have search widgets which actually search specific LoopBuddy queries for the parameters you specify. There are many different ways of achieving this with LoopBuddy.

Check out the forum thread [http://ithemes.com/forum/index.php?/topic/16606-searching-within-a-loopbuddy-query/ Searching Within a LoopBuddy Query] for more details.

===Change OLDER POSTS and NEWER POSTS pagination text===

You can change the "'''Older posts'''" and "'''Newer posts'''" text to say anything by editing those words in your '''''wp-content/plugins/loopbuddy/loopbuddy.php''''' file on lines 1336 and 1337. They will look like the following:

<pre brush="php">
div class="nav-previous"><?php next_posts_link( __( '<span class="meta-nav">←</span> Older posts', 'it-l10n-loopbuddy' ) ); ?></div>
<div class="nav-next"><?php previous_posts_link( __( 'Newer posts <span class="meta-nav">→</span>', 'it-l10n-loopbuddy' ) ); ?></div>
</pre>

Only change the "'''Older posts'''" and "'''Newer posts'''" text in the above to say anything else you wish.

*Related forum thread
**http://ithemes.com/forum/index.php?/topic/19863-pagination-text/

==Video Tutorials and Tips==
These different video tutorials and tips can help you figure out more things about LoopBuddy. Remember, these videos show LoopBuddy and related things that were the most recent/updated as of the date of that video. Things may have changed in actual LoopBuddy since then.
# [http://ithemes.com/forum/index.php?/topic/18160-loop-buddy-placement/#p85184 Show custom static homepage content and 3 latest blog excerpts under it]

==Additional Resources==
# [http://pluginbuddy.com/purchase/backupbuddy/ Purchase BackupBuddy]
# [http://pluginbuddy.com/tutorials/ PluginBuddy Tutorials]
# [http://pluginbuddy.com/ PluginBuddy.com]
# [http://pluginbuddy.com/support/ Support Forums]

[[Category:PluginBuddy]]

LoopBuddy

2012-04-16T17:40:58Z

Bes: Clarified where to find Import/Export /* Import/Export */

'''Release date:''' July 19, 2011

==LoopBuddy Overview==

LoopBuddy is a tool that overwrites a WordPress Loop using a combination of a custom query and a custom Loop layout. You can also create your own Loops using the LoopBuddy shortcode and LoopBuddy widget.

===Query Editor===

If LoopBuddy was a body, the Query Editor would be the brain, with the Layout Editor being the outside bodily appearance.

[[File:Query_editor.png|400px|border|LoopBuddy Query Editor]]

With the Query Editor, you can create Query Groups. Each Query Group defines what data a WordPress Loop is supposed to pull in.

With the Query Editor, you can define:

* Which posts to gather
* Whether pagination or comments are enabled
* Whether to use the default post ID (if on a single post or page)
* and much, much more...

[[File:Query_editor_options.png|400px|border|Query Editor Options]]

===Layout Editor===

The Layout Editor controls how a particular WordPress Loop is supposed to be structured. At the heart of the Layout Editor is Layout Tags. There are several Layout Tags built-in, but you can use the LoopBuddy Hooks to create your own custom Layout Tag and Layout Tag Items.

[[File:Layout_editor.png|400px|border|LoopBuddy Layout Editor]]

With the Layout Editor, simply drag Layout Tags into the appropriate area. If you create a new Layout, there are several default tags that are added automatically.

[[File:Layout_editor_options.png|500px|border|Layout Editor Options]]

===Global Settings===

The Global LoopBuddy Settings allow you to globally override a default WordPress Loop. If your theme doesn't support the Loop Standard, you'll see an error message at the top.

If your theme does support the Loop Standard, you can use the options to override the default WordPress Loops in various areas of the site.

Although LoopBuddy attempts to work without a custom Query, it is highly advisable to use a custom Query and Layout.

[[File:Loopbuddy_settings.png|500px|border|General Settings]]

===Import/Export===

Within the Query and Layout lists pages, you can export/import the items so you can use the same Queries/Layouts on a different site.

This is the same page as where you create new Queries or Layouts.

===LoopBuddy Widget===

You can use the LoopBuddy Widget to display a LoopBuddy Query/Layout in any widgetized area of a site. Please note that you must have a Query AND a Layout for the widget to work.

===LoopBuddy Shortcode===

The LoopBuddy shortcode takes two attributes: a Query ID and a Layout ID. Please note that you must have a Query AND a Layout for the widget to work.

Simply insert the shortcode into a post or page:

<pre class='brush:php'>
[loopbuddy query_id='0' layout_id='0']
</pre>

===LoopBuddy Full 1 Hour Webinar===

Learn the ins and outs of LoopBuddy with the following 1 hour Webinar, made by our very own [http://www.webdesign.com Webdesign.com]
{{#ev:vimeo|26482158|580|363}}

==The Loop Standard==
The Loop Standard divides a loop into two main concepts: a loop and one or more entries.

Both a loop and an entry have three sections: a header, a content section, and a footer. The header contains title information, any meta information, and any necessary navigation links. The content section contains the content relevant to that loop or entry. The footer section is a place to hold additional or duplicate meta information and navigation links.

===The Loop Explained===

The content of a loop is a bit more complex than the content of an entry as a loop's content contains the entries. To better visualize this, here is the basic structure described so far:

* Loop
** Header
*** title
*** navigation
*** meta
** Content
*** Entry
**** Header
***** title
***** navigation
***** meta
**** Content
**** Footer
***** navigation
***** meta
*** Additional entries...
*** Footer
**** navigation
**** meta

The idea is that each section is broken out in a repeatable pattern. This makes styling easier as any content that follows this form can be styled without having to first read through the code in order to understand the structure.

You may notice that there are titles, navigation, and meta for both the entries and the loop. This is because some titles, navigation, and meta are relevant to the loop (the title archive, navigating between pages of posts, or information about an author in an author archive) while other titles, navigation, and meta are relevant to the entry (the blog post's title, navigating through a page split into multiple pages, or a blog post's category information). The rule of thumb is that if the information is specific to an individual post's, page's, etc content, it is an entry-level structure; otherwise, it is a loop-level structure.

Each of these sections have a specific class in the Loop Standard. Here is the structure again with the classes replacing the names:

* loop
** loop-header
*** loop-title
*** loop-utility
*** loop-meta
** loop-content
*** hentry
**** entry-header
***** entry-title
***** entry-utility
***** entry-meta
**** entry-content
**** entry-footer
***** entry-utility
***** entry-meta
*** hentry...
** loop-footer
*** loop-utility
*** loop-meta

Notice the "hentry" class. This looks odd but is actually generated by WordPress internally. It is produced by the <code>post_class()</code> function that is in 2010 and 2011 theme template files. So when you see "hentry", know that this is simply the div that looks like :

<pre class='brush:php'>
<div <?php post_class(); ?>></div>
</pre>

Here is the standard loop in practice:
* loop
** loop-header
*** loop-title (page-title)
** loop-content
*** hentry
**** entry-header (title)
***** entry-title (post-title)
***** entry-meta (post-meta)
***** entry-meta date (date)
**** entry-content (post-content)
**** entry-footer (meta-bottom)
***** entry-meta alignright (alignright)
***** entry-meta alignleft (meta-bottom-left)
*** hentry...
** loop-footer
*** loop-utility (paging)

Not all the elements from above structure examples were used since not all were needed. In the end, only three elements had to be added. The rest of the changes were simply modifying or adding classes to conform to the Loop Standard structure. For some elements, such as "date", the "date" class remained while also getting the "entry-meta" class. This makes it clear what type of structure it is while still giving the additional meaning of it being a container for the date.

===Modifying a Theme to Use LoopBuddy===

Here's an example of TwentyTen's index.php file before it begins loading the various templates:

<pre class='brush:php'>
<?php if ( ! dynamic_loop() ) : ?>
<div class="loop">
<?php
/* Run the loop to output the posts.
* If you want to overload this in a child theme then include a file
* called loop-index.php and that will be used instead.
*/
get_template_part( 'loop', 'index' );
?>
</div>
<?php endif; ?>
</pre>

When <code>dynamic_loop()</code> is executed, LoopBuddy searches to see if this particular loop should be overridden. If not, the normal loop executes. If so, then LoopBuddy overwrites the content of the loop with LoopBuddy content.

===Example of TwentyTen Using the Loop Standard===
Here's an example TwentyTen Loop converted to using the Loop Standard

<pre class='brush:php'>
<?php if ( have_posts() ) while ( have_posts() ) : the_post(); ?>

<div class="loop-content">
<div id="nav-above" class="navigation loop-utility loop-utility-above">
<div class="nav-previous"><?php previous_post_link( '%link', '<span class="meta-nav">' . _x( '←', 'Previous post link', 'twentyten' ) . '</span> %title' ); ?></div>
<div class="nav-next"><?php next_post_link( '%link', '%title <span class="meta-nav">' . _x( '→', 'Next post link', 'twentyten' ) . '</span>' ); ?></div>
</div>

<div id="post-<?php the_ID(); ?>" <?php post_class(); ?>>
<div class="entry-header">
<h1 class="entry-title"><?php the_title(); ?></h1>

<div class="entry-meta">
<?php twentyten_posted_on(); ?>
</div>
</div>
<div class="entry-content">
<?php the_content(); ?>
<?php wp_link_pages( array( 'before' => '<div class="page-link">' . __( 'Pages:', 'twentyten' ), 'after' => '</div>' ) ); ?>
</div>
<div class="entry-footer">
<?php if ( get_the_author_meta( 'description' ) ) : // If a user has filled out their description, show a bio on their entries ?>
<div id="entry-author-info" class="entry-meta entry-meta-below">
<div id="author-avatar">
<?php echo get_avatar( get_the_author_meta( 'user_email' ), apply_filters( 'twentyten_author_bio_avatar_size', 60 ) ); ?>
</div>
<div id="author-description">
<h2><?php printf( esc_attr__( 'About %s', 'twentyten' ), get_the_author() ); ?></h2>
<?php the_author_meta( 'description' ); ?>
<div id="author-link">
<a href="<?php echo get_author_posts_url( get_the_author_meta( 'ID' ) ); ?>">
<?php printf( __( 'View all posts by %s <span class="meta-nav">→</span>', 'twentyten' ), get_the_author() ); ?>
</a>
</div>
</div>
</div>
<?php endif; ?>

<div class="entry-utility">
<?php twentyten_posted_in(); ?>
<?php edit_post_link( __( 'Edit', 'twentyten' ), '<span class="edit-link">', '</span>' ); ?>
</div>
</div>
</div>
<div class="loop-footer">
<div id="nav-below" class="navigation loop-utility loop-utility-below">
<div class="nav-previous"><?php previous_post_link( '%link', '<span class="meta-nav">' . _x( '←', 'Previous post link', 'twentyten' ) . '</span> %title' ); ?></div>
<div class="nav-next"><?php next_post_link( '%link', '%title <span class="meta-nav">' . _x( '→', 'Next post link', 'twentyten' ) . '</span>' ); ?></div>
</div>
</div>

<?php comments_template( '', true ); ?>
</div>

<?php endwhile; // end of the loop. ?>

</pre>

After updating the template files, go through the theme's style.css file in order to update class references to match the new ones. Here are some basic replacements to make:

* .page-title → .loop-title
* .title → .entry-header
* .post-title [h1, h2, h3, etc] (any instance of .post-title followed by a header tag) → .entry-title
* .post-title → .entry-title
* .post-meta → .entry-meta
* .post-content → .entry-content
* .meta-top → .entry-header
* .meta-bottom → .entry-footer
* .post → .hentry
* .paging → .loop-utility

===Showing LoopBuddy Theme Support===

After you've modified your theme's loops, show LoopBuddy that your theme supports it by adding in the following line to your theme's functions.php file:

<pre class='brush:php'>
// Add support for the Loop Standard
add_theme_support( 'loop-standard' );
</pre>

===Adding the Dynamic Loop Function to Your Theme===
The Dynamic Loop function must be added to your theme's functions.php file. This is achieved by adding the following code to the end of the function.php file:

<pre class='brush:php'>
// Add dynamic_loop function for LoopBuddy

/*
Copyright 2011 iThemes (email: support@ithemes.com)

Written by Chris Jean
Version 0.0.1

Version History
0.0.1 - 2011-02-28 - Chris Jean
Initial version
*/

if ( ! function_exists( 'dynamic_loop' ) ) {
function dynamic_loop() {
global $dynamic_loop_handlers;

if ( empty( $dynamic_loop_handlers ) || ! is_array( $dynamic_loop_handlers ) )
return false;

ksort( $dynamic_loop_handlers );

foreach ( (array) $dynamic_loop_handlers as $handlers ) {
foreach ( (array) $handlers as $function ) {
if ( is_callable( $function ) && ( false != call_user_func( $function ) ) ) {
return true;
}
}
}

return false;
}
}

if ( ! function_exists( 'register_dynamic_loop_handler' ) ) {
function register_dynamic_loop_handler( $function, $priority = 10 ) {
global $dynamic_loop_handlers;

if ( ! is_numeric( $priority ) )
$priority = 10;

if ( ! isset( $dynamic_loop_handlers ) || ! is_array( $dynamic_loop_handlers ) )
$dynamic_loop_handlers = array();

if ( ! isset( $dynamic_loop_handlers[$priority] ) || ! is_array( $dynamic_loop_handlers[$priority] ) )
$dynamic_loop_handlers[$priority] = array();

$dynamic_loop_handlers[$priority][] = $function;
}
}

</pre>

==LoopBuddy Downloads==

===Example TwentyEleven Theme===

Here's an example TwentyEleven theme that has been modified to be compatible with LoopBuddy.

[[Media:twentyeleven-loopstandard.zip|TwentyEleven Loop Standard]]

===Example Layout Tag===

Check out the LoopBuddy Marquee Plugin: [[Media:Loopbuddy_marquee.zip|LoopBuddy Marquee]] as an example of creating custom tags.

===Example Queries/Layouts===

Please see below for a ZIP file of some sample layouts and queries that can be imported.

[[Media:Loopbuddy_export.zip|LoopBuddy Export File]]

==LoopBuddy Query==
The LoopBuddy Query is where you create Queries, which in turn create and produce the Loops you want in WordPress. From showing certain posts to the number of posts, categories, posts with specific meta values and more, the '''LoopBuddy Query''' area is where you specify exactly what should be shown, and exactly what should not be shown, in a LoopBuddy output.

===Advanced Meta Queries===

With LoopBuddy 1.2, LoopBuddy Queries now allow you to perform some very powerful advanced Meta queries. Here is a video explaining and giving some examples of the advanced meta queries:

{{#ev:youtube|4snQn7PDylE|580|363}}
*[http://pluginbuddy.com/loopbuddy-1-2-released/ Blog Post announcing Advanced Meta Queries in LoopBuddy 1.2]

===Advanced Taxonomy Queries===

With LoopBuddy 1.2, LoopBuddy Queries now allow you to perform some very powerful advanced Taxonomy queries. Here is a video explaining and giving some examples of the advanced Taxonomy queries:

{{#ev:youtube|ta0GZA5jz9g|580|363}}
*[http://pluginbuddy.com/loopbuddy-1-2-released/ Blog Post announcing Advanced Taxonomy Queries in LoopBuddy 1.2]

==Hooks==

LoopBuddy allows you to create custom tags for the Layout editor. This is advanced functionality, so please don't attempt these steps if you are not intimately familiar with PHP and how LoopBuddy operates.

To create the custom tag, you must use the following hooks.

===Creating a new Custom Tag===

<pre class="brush:php">
<?php
add_filter( 'pb_loopbuddy_custom_tags', 'my_custom_tag_add' );
function my_custom_tag_add( $custom_tags ) {
//Always return $custom_tags
$custom_tags[ 'start_wrap' ] = array(
'My Tag Label',
array(
'wrap' => 'div',
'custom_class' => 'default class'
)
);
return $custom_tags;
} //end my_custom_tag_add

//Start off with the tag name, give the tag a label, and pass it which items it supports (all should ideally contain the 'wrap' and 'custom_class' items
?>
</pre>

Here are some built in tag items that you can choose from:

* link_text
* custom_url
* custom_class
* link_title
* before_text
* after_text
* meta_key
* max_width
* max_height
* shortcode
* author_link_destination
* user_profile
* permalink
* attachment_link_display
* separator
* text
* date_format
* comment_number_zero
* comment_number_one
* comment_number_more
* post_date
* bloginfo
* content_more
* url_display
* image_size

===Creating a new custom tag item===

<pre class='brush:php'>
<?php
add_filter( 'pb_loopbuddy_tag_items', 'my_custom_item_add' );
function my_custom_item_add( $loopbuddy_items ) {
//Always return $loopbuddy_items

$loopbuddy_items[ 'my_custom_item' ] = array(
'function' => 'callback_function',
'args' => array(
'label' => __( 'Link Text', 'LION' ),
'tip' => __( 'Optional text for link. Leave blank to use link as the text.', 'LION' ),
'options' => array( 'option1', 'option2' )
)
);
return $loopbuddy_items;
} //end my_custom_item_add

/* $settings are the arguments passed for the tag item and looks like this
[label] => HTML Wrapper
[tip] => Choose which HTML element to wrap around the item
[options] => Array
(
[0] => none
[1] => span
[2] => div
[3] => p
[4] => h1
[5] => h2
[6] => h3
[7] => h4
[8] => h5
[9] => h6
)

[key] => wrap
[settings] => Array
(
[image_size] => thumbnail
[max_width] =>
[max_height] =>
[wrap] => p
[before_text] =>
[after_text] =>
[custom_url] =>
[custom_class] => attachment
[tag] => wp_get_attachment_image
)

)
*/
function callback_function( $settings ) {
$defaults = array(
'key' => '',
'label' => '',
'tip' => false,
'settings' => array(),
'options' => array()
);
extract( wp_parse_args( $settings, $defaults ) );
//Output HTML for the item
} //end callback_function

?>
</pre>

===Callback function for displaying the tag - pb_loopbuddy_tag_callback-{tag_name}===
<pre class='brush:php'>
<?php
/*$settings contains the tag items and the tag item's value
Example
Array
(
[image_size] => thumbnail
[max_width] =>
[max_height] =>
[wrap] => p
[before_text] =>
[after_text] =>
[custom_url] =>
[custom_class] => attachment
[tag] => wp_get_attachment_image
)
*/

//Add header code
add_action( 'pb_loopbuddy_tag_header-mytagname', 'my_custom_tag_header' );
function my_custom_tag_header( $settings ) {
echo "my header, notes, or other code";
//Render your tag based on its settings
} //end my_custom_tag_header

//Add footer code
add_action( 'pb_loopbuddy_tag_footer-mytagname', 'my_custom_tag_footer' );
function my_custom_tag_footer( $settings ) {
echo "my footer, notes, or other code";
//Render your tag based on its settings
} //end my_custom_tag_header

add_filter( 'pb_loopbuddy_tag_supports-mytagname', 'my_custom_tag_supports' );
//Return an array of what tag items the tag supports
function my_custom_tag_supports( $support_tag_items ) {
return array( 'wrap', 'link_text', 'before_text', 'after_text', 'custom_class' );
//Render your tag based on its settings
} //end my_custom_tag_supports
?>
</pre>

===Rendering the Tag on the Front-end - pb_loopbuddy_render-{tag_name}===

<pre class="brush:php">
<?php
add_filter( 'pb_loopbuddy_render-mytagname', 'mytagname_frontend', 10, 2 );
function mytagname_frontend( $post_object, $tag_items ) {
/* $tag_items look like this
(
[wrap] => none
[link_text] => Edit Post
[before_text] =>
[after_text] =>
[custom_url] =>
[custom_class] =>
[tag] => edit_post_link
)
*/
$return = false; //Populate the $return variable
$return = pluginbuddy_loopbuddy_render_slotitems::get_output( $return, $post_object, $tag_items, true ); //The last argument is skip_before text
return $return;
} //end mytagname_frontend
?>
</pre>

===Ignoring Post Types in the Layout Editor===

There will be certain post types that are public and have a public user interface, but the user would still not like to be able to configure override settings in the LoopBuddy Settings page.

A plugin author can use the following hook to remove these post types:

<pre class="brush:php">
<?php
add_filter( 'pb_loopbuddy_exclude_post_types', 'myplugin_exclude_post_types' );
function myplugin_exclude_post_types( $post_types_to_exclude ) {
$post_types_to_exclude[] = 'my_custom_post_type';
return $post_types_to_exclude;
}
?>
</pre>

==Shortcodes==

Shortcodes basically allow almost any plugin or custom code to be plugged in anywhere in WordPress.

LoopBuddy supports shortcodes fully, allowing you to put any shortcode, whether from a plugin or your own, into any place in LoopBuddy Layout, including the '''Pre-Loop Text / HTML''', '''Post-Loop Text / HTML''' and '''No Results Text / HTML''' sections. This probably makes the already powerful LoopBuddy the only most powerful way to control all your content, loops and display on your site.

[http://ithemes.com/codex/page/General_WordPress_Related#Editing_or_Adding_Stuff_to_Functions.php Info on editing or adding stuff to Functions.php]

===Show Category/Taxonomy Description on NON-Archive pages via Shortcode===

Category Descriptions are a little more sophisticated than other post related variables because if there is more than one category being used, then it will be hard for WordPress to display ALL descriptions nicely OR one category (which one?).

*Outside of archive pages, to display Category Descriptions (or any taxonomy description) you have to do the following:
**1 : Put the following anywhere (usually near the end of the file) in your theme's custom functions.php file (it creates a shortcode you'll use to display the description of a Category or any Taxonomy):
<pre class="brush:php">add_action( 'init', 'lb_cat_init' );
function lb_cat_init() {
add_shortcode('taxdescription', 'lb_the_description');
} //end lb_cat_init
function lb_the_description() {
global $post;
if ( !is_object( $post ) ) return;
$terms = get_post_meta( $post->ID, 'description_terms', true );
$taxonomy = get_post_meta( $post->ID, 'description_taxonomy', true );
$return = '';
if ( $terms && $taxonomy ) {
if ( !is_array( $terms ) ) {
$terms = explode( ',', $terms );
}
foreach ( $terms as $term_name ) {
$term = get_term_by( 'slug', $term_name, $taxonomy );
if ( !$term ) continue;
$description = get_term_field( 'description', $term->term_id, $term->taxonomy );
if ( empty( $description ) || !$description ) continue;
$return .= apply_filters( 'pb_the_content', $description );
}
}
return $return;
} //end lb_the_description</pre>
**2 : In the posts you want to show the category description, add the following 2 custom field names and values:
'''Custom Field Name''' ----- '''Custom Field Value'''

description_taxonomy ----- category

description_terms ----- books '''''(OR any category name you have)'''''

**3 : Add a Shortcode Tag to your LoopBuddy layout which has the following shortcode in it:

<code><strong>[taxdescription]</strong></code>

That will show the category description anywhere you put the shortcode.

*Links with related info:
**[http://ithemes.com/forum/index.php?/topic/18153-use-of-category-description/ Use of Category Description - LoopBuddy Forums]
**[http://codex.wordpress.org/Function_Reference/category_description category_description on WordPress Codex]
**[http://codex.wordpress.org/Function_Reference/term_description term_description on WordPress Codex]

===Show Custom Page Title for Same LoopBuddy Layout on Different Pages via Shortcode===

*One awesome example of using Shortcodes with LoopBuddy is to show a custom page title, along with any LoopBuddy Layout content, where different pages use the same LoopBuddy Layout. Our awesome LoopBuddy customer Bruce provided the following info to help you all with that:
**1 : Put the following anywhere (usually near the end of the file) in your theme's custom functions.php file:
<pre class="brush:php">
function return_title() {
return '<h1>'.get_the_title().'</h1>';
}
add_shortcode('pg_title', 'return_title');</pre>
**2 : Add
<code><strong>[pg_title]</strong></code>

anywhere in the LoopBuddy Layout where you want to show the custom page title.

That will show the custom page title just for that specific post/page where the Layout is being shown.
*Related links:
**[http://ithemes.com/forum/index.php?/topic/18046-displaying-the-page-title-on-which-i-am-using-loop-buddy/ LoopBuddy user Bruce asking about and then sharing the code to show custom Page Titles on each Page where the same LoopBuddy Layout is used]

==External Plugins Compatibility==

LoopBuddy is one of those rare plugins which can play well with many external plugins. However, any external plugin compatibility is NOT guaranteed in any manner, since external plugins are not covered nor supported by PluginBuddy in any manner or fashion.

If there is a problem when any other plugin is used with LoopBuddy, it does not mean there is a bug in LoopBuddy. First you should check if there is a problem in the other plugin (since LoopBuddy already currently works without any issues in each and every aspect of its publicized features). Then you have to see if the problem exists when the other plugin is de-activated and LoopBuddy is kept activated. Only after such steps and more analysis can we at PluginBuddy devote any time or resources to see whether or not there is something in LoopBuddy that can be fixed, enhanced or improved to make it work better with the external plugin in question, if that external plugin is not the source of the problem.

===Custom Post Types===
At this time, Custom Post Types UI is the only supported plugin in LoopBuddy for creating custom post types. We recommend you try and use that to create post types.

Otherwise, you should add custom post types directly to your functions.php file in your current theme.

*Related links
**[http://wordpress.org/extend/plugins/custom-post-type-ui/ Custom Post Types UI plugin]
**[http://codex.wordpress.org/Post_Types Creating Post Types in WordPress]

===Page Navigation===

At this time, WP-PageNavi is the only supported plugin in LoopBuddy for having custom page navigation. We strongly recommend you try it for any of your custom page navigation needs.

*Related link
**[http://wordpress.org/extend/plugins/wp-pagenavi/ WP PageNavi WordPress Plugin]

===Customize Excerpts===

At this time, Advanced Excerpt is the only supported plugin in LoopBuddy for allowing custom lengths and formatting for excerpts in WordPress.

*Related link
**[http://wordpress.org/extend/plugins/advanced-excerpt/ Advanced Excerpt WordPress Plugin]

==LoopBuddy FAQ==

Here are some frequently asked or encountered LoopBuddy questions and setups, and their answers.

===Sort Custom Field Values by Meta Value (Character or Numeric)===

*Custom Field values can be sorted by meta value (character or numeric).
*Only ONE meta item can be used to sort at one time.
**Using multiple meta items will assume you would like an advanced meta query, and sorting will be ignored in such a case. '''This is a WordPress limitation.'''
*Sort Custom Field Values via the following steps (assuming you already have several posts with the same custom field):
**1 : Change the Order By parameter to either "'''Meta Value'''" or "'''Numeric Meta Value'''".
**2 : Go to Post Meta Parameters and click "'''Add Meta'''".
**3 : Set the '''Meta Key''' and '''Meta Values''' you would like to search for and sort by.
**4 : Save the query.
**5 : Assign the query to a post or section and observe the results.

===LoopBuddy does not work on static Posts page===

*LoopBuddy will NOT work on pages set as Static Posts Page in '''WordPress --> Settings --> Reading --> Front Page Displays --> Posts Page''' section. There is a good reason for it and a great workaround.
** Reason
***The Reading Screen in the WordPress Settings [http://codex.wordpress.org/Settings_Reading_Screen Settings --> Reading Screen Settings] is necessary when you want to tell WordPress that your blog content doesn't reside on the home page.
***For example, you have selected a Front Page, which will tell WordPress, "Use this page instead of showing a default blog layout."
***Since there is technically no longer a blog layout, WordPress wants to know, "Where can I find your blog content?"
***This is how WordPress works, and not a LoopBuddy bug. There is a great flawless way to get exactly what you want with the below workarounds, though.
**Workaround (any one of this will work - we recommend the PREFERRED LoopBuddy way to do it!)
*** Not have a section on your site with your blog content (readers will only be able to access your posts via category and date archives).
*** Create a page to point WordPress to, and WordPress will take care of the rest and display the appropriate blog content.
*** '''PREFERRED:''' With LoopBuddy, however, you don't have to specify a "Blog" section in WordPress.
**** You can create a regular page.
**** Allow LoopBuddy to create a blog section for you either via '''LoopBuddy --> Settings''' option OR by choosing the '''LoopBuddy options in the Post/Page Editor page''' for the page you just created.
**** WordPress doesn't need to know about it in this particular case, and it won't hurt your site in the least. You do NOT have to change the '''WordPress --> Settings --> Reading --> Front Page Displays --> Posts Page''' settings for this option to work perfectly.
*Threads and pages with more detailed info of the setup and info related to the above exact solutions
**http://ithemes.com/forum/index.php?/topic/17845-unable-to-get-loopbuddy-working/
**http://codex.wordpress.org/Settings_Reading_Screen

===Make a Custom Field (or almost anything) Clickable===
With the power of different tags in LoopBuddy Layout, you can make almost anything clickable without editing a single file. This is extremely useful when you want to make something like a Custom Field, which is text by default, clickable automatically in any or every loop.
*Steps to perform in your LoopBuddy Layout:
**1 : Start with a Text tag (first Text tag) which has the content: <code><a href="</code>
**2 : Next comes anything, including a Custom Field tag. This is the link.
**3 : Now comes another Text tag (second Text tag) which has the content: <code>"></code>
**4 : Now comes anything to show the link. It can be the same Custom Field tag again as #2 above, another custom field, or any text or image you wish.
**5 : Another Text tag (3rd Text tag) with the following content: <code></a></code>
That's it!
*Related thread
**http://ithemes.com/forum/index.php?/topic/16971-text-before-single-custom-field-and-url/

===Search within a LoopBuddy Query===

You can have search widgets which actually search specific LoopBuddy queries for the parameters you specify. There are many different ways of achieving this with LoopBuddy.

Check out the forum thread [http://ithemes.com/forum/index.php?/topic/16606-searching-within-a-loopbuddy-query/ Searching Within a LoopBuddy Query] for more details.

===Change OLDER POSTS and NEWER POSTS pagination text===

You can change the "'''Older posts'''" and "'''Newer posts'''" text to say anything by editing those words in your '''''wp-content/plugins/loopbuddy/loopbuddy.php''''' file on lines 1336 and 1337. They will look like the following:

<pre brush="php">
div class="nav-previous"><?php next_posts_link( __( '<span class="meta-nav">←</span> Older posts', 'it-l10n-loopbuddy' ) ); ?></div>
<div class="nav-next"><?php previous_posts_link( __( 'Newer posts <span class="meta-nav">→</span>', 'it-l10n-loopbuddy' ) ); ?></div>
</pre>

Only change the "'''Older posts'''" and "'''Newer posts'''" text in the above to say anything else you wish.

*Related forum thread
**http://ithemes.com/forum/index.php?/topic/19863-pagination-text/

==Video Tutorials and Tips==
These different video tutorials and tips can help you figure out more things about LoopBuddy. Remember, these videos show LoopBuddy and related things that were the most recent/updated as of the date of that video. Things may have changed in actual LoopBuddy since then.
# [http://ithemes.com/forum/index.php?/topic/18160-loop-buddy-placement/#p85184 Show custom static homepage content and 3 latest blog excerpts under it]

==Additional Resources==
# [http://pluginbuddy.com/purchase/backupbuddy/ Purchase BackupBuddy]
# [http://pluginbuddy.com/tutorials/ PluginBuddy Tutorials]
# [http://pluginbuddy.com/ PluginBuddy.com]
# [http://pluginbuddy.com/support/ Support Forums]

[[Category:PluginBuddy]]

PluginBuddy

2012-04-16T17:37:22Z

Bes: Added Licensing Issue Errors message and info to get started, and created /* Licensing issues due to different Membership/Account scenarios */ section

Welcome to the PluginBuddy Knowledge Base - Tutorials, Technical Information, Debugging Information, and more.

=Premium Plugins=
* [[Ajax-Edit-Comments]]
* [[BackupBuddy]]
* [[DisplayBuddy]]
** [[Accordion]]
** [[Billboard]]
** [[Carousel]]
** [[CopiousComments]]
** [[FeaturedPosts]]
** [[Rotating Images]]
** [[RotatingText]]
** [[Slides]]
** [[Slideshow]]
** [[Tipsy]]
** [[VideoShowcase]]
* [[EmailBuddy]]
* [[Frolic]]
* [[LoopBuddy]]
* [[Mobile]]
* [[TailoredLogin]]
* [[ThumbsUp]]
* [[VidEmbed]]

=Free Plugins (active)=
* [[Featured Text]]
* [[PB-Tweet]]
* [[ServerBuddy]]
* [[Tabber Widget]]
* [[ThemeMan]]
* [[S3 URLS]]
* [[YOURLS]]
* [[ContactBuddy]]

=Free Plugins (inactive)=
* [[WP Easy Uploader]]
* [[WP Developer Assistant]]
* [[Easy Theme and Plugin Updater]]
* [[Current Date & Time Widget]]

''[[:Category:PluginBuddy|View all PluginBuddy Wiki Pages]]''

=Misc. Documentation=
==Frequently Asked (Plugin) Questions==
*[[General Plugins FAQ]]

==License Manager Tutorial and Information==
*[[License Manager]]
==PHP Development & Advanced==
*[[.htaccess]]
*[[PHP]]
*[[Arrays]]

[[Category:PluginBuddy]]

=Translations (localization / internationalization)=

Many PluginBuddy plugins come with translation capability. That means such PluginBuddy plugins can be translated (aka localized) to other languages.

===How Translations Work===

PluginBuddy provides the capability to have a translation in such plugins. Anyone wanting to enhance PluginBuddy with specific language translations can do so voluntarily via Translation Files. Translation Files are simply language files created fully and solely by the volunteer community which use the already built in translation-capable features in many of the PluginBuddy plugins to allow such plugins to show text or outputs in different languages. Making PluginBuddy translation-capable is done by PluginBuddy. Creating, updating and sending in any language specific translation files to PluginBuddy is done by the volunteer community.

Anyone can create translation files, package them into the proper format and give PluginBuddy the final translated files that we will try to include in the next update for the plugin in question. We call such awesome people, who create or update the translation files and send us the full translation package files, '''Awesome Translator Volunteers''', and we are really thankful that they take the time to do such an awesome thing.

If you want to help us, you can translate any existing PluginBuddy plugin which supports internationalization (another way of saying localization or translation-capable) and then, once you're fully done, simply let us know in the forums the link to the final language files that we can directly save and simply try to include in any future updates for the plugin(s) in question.

===Tips on how to localize any PluginBuddy Plugin to any non-English language===

The following 9 tips can help you figure out how to approach translations, how to create translations, and how to send us the final translated file for any translation-capable PluginBuddy plugin:

*1 : Many of the PluginBuddy plugins are internationalized, meaning they have the capability to be translated, via actual external translation files, by any non-iThemes-staff Awesome Translator Volunteer who wishes such plugins to be translated to their language.
*2 : If a PluginBuddy plugin is currently not internationalized or you're not sure if it is, you can ask us in the [http://ithemes.com/forum Support Forums] and we'll let you know, or we'll have it included as a future translation feature request. After the translation capability is added to such a plugin, you can submit the actual translation file. Please remember though: we cannot help with creating, understanding or making any language translation files. Our Awesome Translator Volunteers do that voluntarily (you can too! keep on reading) and fully on their own.
*3 : There are MANY resources which teach you how to create and work with WordPress language files. Following are the official 3 directly by the WordPress community:
**1 : [http://codex.wordpress.org/WordPress_in_Your_Language WordPress in Your Language]
**2 : [http://codex.wordpress.org/Translating_WordPress Translating WordPress]
**3 : [http://codex.wordpress.org/I18n_for_WordPress_Developers What WordPress Localization in Plugins is mainly about]
*4 : Translations are sent in from volunteers from all over the world. As a courtesy, we sometimes package the actual language translation files (provided directly by the Awesome Translator Volunteers) in with the final product. If some translation is not included in the actual plugin even when the plugin has the capability to be translated, you can submit the final translation to us for consideration in the next update by posting on our forums OR you can include the translation in your own live or local WordPress install directly for your own use. More info on how to include your own language specific file for your own WordPress sites is in the resources listed in #3 above.
*5 : A translation included in with the final product does not guarantee the accuracy or quality of the translation. These files are from the Awesome Translator Volunteers, and correction of these files is also done by those Awesome Translator Volunteers.
*6 : If a translation is very inaccurate or incomplete, we can put out a request for a new translation from the volunteer community, or remove the translation from the packaged and final product. You can also let us know of any inaccuracies in any existing translation files by the Awesome Volunteers by providing us with the corrected final files. Please remember: we only accept final and full translation files that you yourself have already created or packaged properly. If you let us know only of the actual inaccuracies without providing the final correct files, we cannot make such changes ourselves to the translation files.
*7 : Unfortunately, PluginBuddy cannot work on, help with, create, nor make any updates to any specific translation files you may have, or may be working on, or want to work on. Our Awesome Volunteers do that and simply give us the final files for inclusion or consideration.
*8 : If you have corrections for any existing translation in form of final proper format translation files for an existing language, OR want to provide the final and proper translation files for a new language, please post a new thread in the appropriate product category in the [http://ithemes.com/forum/ PluginBuddy Support Forums] with the final translations files. If you have any support questions on how to create or make language specific translation files, or how translation files work, you can do so on the [http://wordpress.org/support/ WordPress forums], as such support questions are outside the scope of what PluginBuddy support guarantees with your iThemes membership.
*9 : Any final translation file provided by you (or any other Awesome Volunteer) on the support forums will then be saved and filed as a future enhancement request for the future updates of the plugin(s) in question. In your support forum thread, where you share the final complete translation files you inclusion, you can upload your files directly to the forums OR upload them somewhere and link to them in your support forum thread. We will then download and save such files. Remember please: we cannot guarantee looking inside such files or verifying that they are correct in any manner (because of so many languages in the world and so many possible language files everywhere).

Thank you SO MUCH for being interested in providing translation files for our PluginBuddy plugins. We hope you will become one of our Awesome Translator Volunteers, in addition to being our AWESOME CUSTOMER, and create/update any language-specific translation file package and provide it to us so that we can consider including it in future updates.

===Resources for understanding, creating, updating and submitting final translation files===
*Here are the 3 official resources again which you can use to create, update, start work on and finish translation on any of the translation-capable PluginBuddy plugins:
**1 : [http://codex.wordpress.org/WordPress_in_Your_Language WordPress in Your Language]
**2 : [http://codex.wordpress.org/Translating_WordPress Translating WordPress]
**3 : [http://codex.wordpress.org/I18n_for_WordPress_Developers What WordPress Localization in Plugins is mainly about]

=Extra Customizations=
While any extra customization of any PluginBuddy Plugin is beyond the scope of the official support, we do from time to time offer different tips and tutorials on editing the awesome PluginBuddy plugins to better fit your individual needs. All such edits are, however, beyond what is officially supported and provided in the actual plugin admin panel and officially stated features on the individual plugin pages. No official support is provided nor guaranteed in, before, during, after or related to anything resulting from any such edits/customizations.

No support is provided on any of these extra customizations. Any of the steps mentioned in any of these extra custom edits may change at any time depending on newer versions of the plugins being released. Any use or customization of anything, beyond what is provided by default inside the plugin admin menu, means you are proceeding at your own risk and that you accept 100% responsibility and liability for everything you change or modify in any manner in the plugin. Your purchase and use of any PluginBuddy plugin implies and shows that you are buying and using PluginBuddy plugin(s) the way it(they) came in their original unmodified form, with no exceptions.

*Remember:
**[http://pluginbuddy.com/purchase/backupbuddy/ Make a backup of your entire site with BackupBuddy] before making any edits!
** PluginBuddy only supports the official unedited, unmodified versions of all PluginBuddy plugins.
** Use a good text editor to make any file changes. Again, maintain backups!
** Any changes you make to files WILL MOST PROBABLY be lost when the plugin is upgraded to any newer version.
** You are 100% responsible and liable for anything resulting from any of these changes.
** No support is provided nor guaranteed on any of these extra changes in any form or shape, whatsoever, regardless of who suggested these custom edits or suggestions.
** Any extra customization info or suggestion is added voluntarily by PluginBuddy staff to help users as much as possible, even if such customization is outside the scope of any membership support.
** Whether a PluginBuddy staff or representative offered or suggested the edit/customization, another customer or anyone else, PluginBuddy does not officially support nor provide any official support on any such edits.
** We cannot guarantee providing any support on any edits or customization tips we provide.
** Absolutely no support is guaranteed in any manner on any of our free plugins, whether or not there is any customization/edit involved.

=External Plugins Compatibility=

PluginBuddy does not promise, guarantee or provide support for any compatibility with any external plugin. If any PluginBuddy Plugin works without any problems when used with any external plugin in question, that means the PluginBuddy Plugin is most probably working without any issues overall. PluginBuddy is not responsible for making PluginBuddy plugins work in any manner, whether custom, fully, fixed or other, with any external non-PluginBuddy plugins. PluginBuddy is also not responsible for providing any support whatsoever for any external plugin, whether or not such an external plugin is used along with any PluginBuddy plugin.

=Free Plugins=

Free plugins are provided as is. There is no guaranteed support that comes with them. Guaranteed support is limited only and mainly for our premium unmodified plugins.

=Bugs, Features and ETA on new updates=

With every new release of any plugin, there may be a new bug or two. You may also want to have new features added to specific plugins. All existing versions of all plugins can have bugs reported OR new features suggested. All of this is done via the [http://ithemes.com/forum official forums].

New updates are also usually released regularly and at the same time, at very different paces, depending on the current number of bugs, features, new plans and tasks at hand. Therefore it is the official policy that there is NO pre-defined ETA on any bug fix, feature imeplemention OR new update OR new plugin roll-out UNLESS otherwise specified specifically in writing somewhere by an official iThemes employee.

==Bugs, bug reports and bug fixes==

Bug reports are filed and noted as they are encountered (thanks for reporting them to us!). There is never any ETA on any bug fixes unless otherwise noted.

==Feature Requests==

Feature requests and feature suggestions are basically future suggested features that users can suggest, and/or future features PluginBuddy may consider adding to the future versions of the plugin(s) in question (again, thanks for suggesting new features!).

There is no guaranteed ETA on when such feature requests will be implemented, unless otherwise noted. All suggested features are just that: suggestions. They remain suggestions until they're confirmed as officially in the works and to be included. Even then, unless a feature is actually rolled out publicly, there is no guarantee any feature suggestion will be implemented. We do our best to try and accommodate as many feature suggestions as possible.

Also, there is no guarantee that any feature request suggested will be implemented, unless otherwise noted.

==ETA on new updates==

Just like bug fixes and new features, there is never a guaranteed date nor a guaranteed time frame on when new updates will roll out. We work every single day of the week, all the time, on our plugins and thus every day there is something new and improved happening in almost all our plugins daily. Whenever we are ready to release any new updates publicly, you'll find out by seeing the plugin update notice in your WordPress OR in your [http://ithemes.com/member/member.php Member's area].

=What does BETA mean?=

Some of PluginBuddy plugins may be in Beta status OR may have Beta features. BETA simply means that some feature or specific part of the plugin is currently still in testing mode, and can cause issues if not used properly. All BETA plugins/features are not yet 100% stable, and thus should NOT be relied on to be working properly OR working at all. Throughout the iThemes Codex, any time the word "Beta" is used in any form, it refers to Beta plugins, Beta features, Beta status and/or anything related to the Beta nature that is officially announced or mentioned as such by any iThemes staff or on any of the Plugin pages, or in this Codex.

Beta implies that any new features or plugins are very close to being released as 100% working very soon, and that there may still be some issues to fix or test more before removing the Beta status. Since no single software of any kind can be tested under every system and site configuration in the world, the Beta status enables the Beta features to be tested out by as many people on as many different websites and configurations as possible.

*Some points to keep in mind when using any BETA plugin/feature:
**1 : Make [http://pluginbuddy.com/purchase/backupbuddy/ FULL WordPress backups] before using ANY beta feature.
**2 : Beta means that the current software feature is NOT complete, and that you are NOT forced to use such a feature at all. You are advised to WAIT until the BETA status is removed.
**3 : Using any Beta feature of any kind, whether it is an entire plugin or something inside a plugin, means and shows that you are fully accepting any liability for any risks involved.
**4 : Using any Beta feature of any kind, whether it is an entire plugin or something inside a plugin, means and shows that you are fully aware that there are all different kinds of risks involved with such features.
**5 : If you are concerned about your important data or anything bad that might happen as a result of using any Beta feature, do NOT use such Beta features.
**6 : ALWAYS make full [http://pluginbuddy.com/purchase/backupbuddy/ BackupBuddy Backups of all your important data] before using any Beta software, whether that Beta software is from PluginBuddy or from any other place.
**7 : If any issues are found in Beta, they are usually added to the list of bug fixes to be released as a whole, or for the next big update, instead of being updated OR fixed individually on a case by case basis.
**8 : Beta features are recommended to test and play with on test sites/servers and configurations with any dummy data, as long as you have [http://pluginbuddy.com/purchase/backupbuddy/ full backups of all important data] still.
**9 : iThemes is not liable nor cannot be held accountable for any unwanted results resulting from the use of BETA features.
**10 : The very name and nature of BETA shows clearly, without any doubt, that there will most probably be issues and problems involved when such labeled features are used anywhere.
**11 : Support for Beta features may be very limited. We usually simply collect all reports related to Beta features and collect them all for one big update in the future.
**12 : If you lose any important data or settings anywhere, or encounter damaged data or settings anywhere, because of any Beta feature, we will not be able to help you and will simply tell you to revert to your previous [http://pluginbuddy.com/purchase/backupbuddy/ backups]. We will also tell you to always wait for BETA status to be removed before using any such features.

If you do not fully understand what Beta means, OR are not willing to fully accept and be fully liable for any risks involved because of using such Beta software, you should NOT use the Beta software in any manner. In such a case, you should simply wait until the Beta status is removed.

*[http://pluginbuddy.com/what-does-beta-mean/ Blog post announcing what BETA means]

=PluginBuddy Licenses=

In unusual cases, you may run into some of the following licensing issues or errors. The possible solutions are listed below in their own separate sections:

*Error Messages
**'''You have already generated all the keys you have available or your licenses have expired. Please obtain additional licenses or unlicense a site. ERROR L14513-JW.'''

==Licenses Issues due to Plugin Conflicts==

Some times, external plugins may cause issues in detaching, deleting, generating OR saving license keys. Such plugins may also cause issues when you want to manually or automatically upgrade plugins when you try to solve licensing issues.

Following is a list of currently known plugins which cause license detaching, deleting, generating OR saving issues. Please disable the following plugins, even temporarily, while you perform all the steps of manually OR automatically upgrading the PluginBuddy plugins in question, and detaching, deleting, generating and saving license keys for them. Keep such plugins disabled UNTIL all license key issues are gone OR at least while you perform these steps.

*Plugins causing PluginBuddy licensing issues
**'''W3 Total Cache or WP Super Cache or WinCache :''' If you are using any caching plugin like '''W3 Total Cache''' or '''WP Super Cache''' or any PHP Extension like WinCache, please disable it temporarily and then carry out any required steps. You can re-enable the plugin or extension in the end after everything works in terms of the licenses.
***Fix: Follow the above steps to fix this issue. [http://ithemes.com/forum/index.php?/topic/19436-backupbuddy-license-issue/#p92171 Steps also explained by BackupBuddy customer Laura (thanks!)]
**'''Any other CACHING or related plugin or extension:''' Try disabling such plugins/extensions, performing the required steps, and then re-activating the Caching or related plugins/extensions in question.

*Related Links
**1 : [http://ithemes.com/forum/topic/24881-license-key-is-not-set-yet-or-invalid/page__view__findpost__p__116047 blm03 deactivated W3 Total Cache, which allowed the licenses to save correctly]
**2 : [http://ithemes.com/forum/topic/26022-cant-generate-a-license-for-my-domain/page__view__findpost__p__121072 Disabling WinCache extension for PHP fixes Licensing issues]
**3 : [http://ithemes.com/forum/topic/24737-backupbuddy-manage-licenses/page__view__findpost__p__115187 Karlos deactivated W3 Total Cache, and that fixed the licensing issues]
**4 : [http://ithemes.com/forum/topic/23481-license-issue-pluginbuddy-developer-to-backupbuddy-both-unlimited/page__view__findpost__p__110368 Disabling W3 Total Cache modules allowed Greg to license BackupBuddy without any issues]
**5 : [http://ithemes.com/forum/topic/23275-unable-to-get-license-to-stick/page__pid__109503#entry109503 W3 Total Cache causing licenses to be deleted after a while]
**6 : [http://ithemes.com/forum/topic/22964-cant-find-stylesheet-to-make-adjustments-to-slider/page__view__findpost__p__107933 W3 Total Cache not allowing licenses to be saved properly]
**7 : [http://ithemes.com/forum/topic/22859-bub-licenses-not-taking-effect/page__view__findpost__p__107476 W3 Total Cache not allowing licenses to be saved - easy solution!]
**8 : [http://ithemes.com/forum/index.php?/topic/19079-wont-let-me-set-a-license-key/#p91663 W3 Total Cache plugin conflict and solution]
**9 : [http://ithemes.com/forum/index.php?/topic/19436-backupbuddy-license-issue/#p92171 W3 Total Cache plugin conflict and solution]
**10 : [http://ithemes.com/forum/index.php?/topic/20228-key-does-not-work/#p95697 W3 Total Cache plugin conflict and solution]
**11 : [http://ithemes.com/forum/index.php?/topic/19041-license-problem-causes-loss-of-all-bb-settings-way-to-get-them-back/ WP Super Cache conflict and solution]

==Licensing issues due to different Membership/Account scenarios==

You may run into licensing issues if something unexpected is happening in or to your membership/accounts.

*Having '''multiple accounts''' with the '''same e-mail address'''.
**If you have more than one account with iThemes and use the same e-mail address with all (or more than one of) your accounts, you may run into the following error:
*** '''You have already generated all the keys you have available or your licenses have expired. Please obtain additional licenses or unlicense a site. ERROR L14513-JW'''
**One solution is to have your accounts combined by contacting sales.
**Another solution is to make sure you associate each account with a different e-mail address.
*** [http://ithemes.com/forum/topic/26420-bought-2-site-license-used-on-1-site-cant-generate-key-for-2nd-site/ User having 2 accounts with the same e-mail, getting ERROR L14513-JW, and resolving the issue by making sure their 2 accounts have 2 separate e-mail addresses]

==Other Steps to Resolve Licensing Issues==

There are some reports that some users have issues with their license insides the Licenses area of different PluginBuddy plugins, including BackupBuddy.

Remember: All your PluginBuddy plugins, including BackupBuddy, will CONTINUE WORKING PERFECTLY even with these licensing issues. You can keep using the plugins exactly how you want them even during these licensing issues. Your plugins are NOT affected by this licensing situation in any manner.

Your membership is also completely fine and you have NOT lost any license(s). The issue is happening to some customers who simply need to upgrade manually to the latest version of their plugin, if the automatic upgrade does not work.

*Plugins with the update versions which remove this issue completely
**ALL PluginBuddy Products

*You can upgrade via one of the following:
**Automatically upgrade to the latest version
**Manually update by downloading the latest zip version of your PluginBuddy plugin from your Member's panel and then
***Overwrite your existing plugin directory via FTP with the new files.
***De-activate the existing plugin, delete it via your '''WordPress --> Plugins''' area and then upload the newly downloaded zip file. Then re-activate the plugin.
**That will remove the issue completely.
*DETACH the key and then RE-ATTACH the license key for the specific site in question IF licensing still shows issues AFTER manually upgrading to the latest version of the plugin in question (check your Member's area for the latest version download)
*Also make sure to DETACH the key, DELETE that same AND any other keys related to that specific site from the entire licenses area, and then GENERATE a new key for that site IF detaching and re-attaching the license key does not work AFTER manually upgrading (for example, manually upgrading to the latest BackupBuddy version - all plugins have their own latest version numbers - check your Member's area for the latest version download)

[http://ithemes.com/forum/index.php?/topic/6691-read-this-first-pluginbuddy-licensing-issues/page-2/#p85977 First reports]

PluginBuddy

2012-04-03T19:13:17Z

Bes: Added info for WinCache PHP extension /* Licenses Issues due to Plugin Conflicts */

Welcome to the PluginBuddy Knowledge Base - Tutorials, Technical Information, Debugging Information, and more.

=Premium Plugins=
* [[Ajax-Edit-Comments]]
* [[BackupBuddy]]
* [[DisplayBuddy]]
** [[Accordion]]
** [[Billboard]]
** [[Carousel]]
** [[CopiousComments]]
** [[FeaturedPosts]]
** [[Rotating Images]]
** [[RotatingText]]
** [[Slides]]
** [[Slideshow]]
** [[Tipsy]]
** [[VideoShowcase]]
* [[EmailBuddy]]
* [[Frolic]]
* [[LoopBuddy]]
* [[Mobile]]
* [[TailoredLogin]]
* [[ThumbsUp]]
* [[VidEmbed]]

=Free Plugins (active)=
* [[Featured Text]]
* [[PB-Tweet]]
* [[ServerBuddy]]
* [[Tabber Widget]]
* [[ThemeMan]]
* [[S3 URLS]]
* [[YOURLS]]
* [[ContactBuddy]]

=Free Plugins (inactive)=
* [[WP Easy Uploader]]
* [[WP Developer Assistant]]
* [[Easy Theme and Plugin Updater]]
* [[Current Date & Time Widget]]

''[[:Category:PluginBuddy|View all PluginBuddy Wiki Pages]]''

=Misc. Documentation=
==Frequently Asked (Plugin) Questions==
*[[General Plugins FAQ]]

==License Manager Tutorial and Information==
*[[License Manager]]
==PHP Development & Advanced==
*[[.htaccess]]
*[[PHP]]
*[[Arrays]]

[[Category:PluginBuddy]]

=Translations (localization / internationalization)=

Many PluginBuddy plugins come with translation capability. That means such PluginBuddy plugins can be translated (aka localized) to other languages.

===How Translations Work===

PluginBuddy provides the capability to have a translation in such plugins. Anyone wanting to enhance PluginBuddy with specific language translations can do so voluntarily via Translation Files. Translation Files are simply language files created fully and solely by the volunteer community which use the already built in translation-capable features in many of the PluginBuddy plugins to allow such plugins to show text or outputs in different languages. Making PluginBuddy translation-capable is done by PluginBuddy. Creating, updating and sending in any language specific translation files to PluginBuddy is done by the volunteer community.

Anyone can create translation files, package them into the proper format and give PluginBuddy the final translated files that we will try to include in the next update for the plugin in question. We call such awesome people, who create or update the translation files and send us the full translation package files, '''Awesome Translator Volunteers''', and we are really thankful that they take the time to do such an awesome thing.

If you want to help us, you can translate any existing PluginBuddy plugin which supports internationalization (another way of saying localization or translation-capable) and then, once you're fully done, simply let us know in the forums the link to the final language files that we can directly save and simply try to include in any future updates for the plugin(s) in question.

===Tips on how to localize any PluginBuddy Plugin to any non-English language===

The following 9 tips can help you figure out how to approach translations, how to create translations, and how to send us the final translated file for any translation-capable PluginBuddy plugin:

*1 : Many of the PluginBuddy plugins are internationalized, meaning they have the capability to be translated, via actual external translation files, by any non-iThemes-staff Awesome Translator Volunteer who wishes such plugins to be translated to their language.
*2 : If a PluginBuddy plugin is currently not internationalized or you're not sure if it is, you can ask us in the [http://ithemes.com/forum Support Forums] and we'll let you know, or we'll have it included as a future translation feature request. After the translation capability is added to such a plugin, you can submit the actual translation file. Please remember though: we cannot help with creating, understanding or making any language translation files. Our Awesome Translator Volunteers do that voluntarily (you can too! keep on reading) and fully on their own.
*3 : There are MANY resources which teach you how to create and work with WordPress language files. Following are the official 3 directly by the WordPress community:
**1 : [http://codex.wordpress.org/WordPress_in_Your_Language WordPress in Your Language]
**2 : [http://codex.wordpress.org/Translating_WordPress Translating WordPress]
**3 : [http://codex.wordpress.org/I18n_for_WordPress_Developers What WordPress Localization in Plugins is mainly about]
*4 : Translations are sent in from volunteers from all over the world. As a courtesy, we sometimes package the actual language translation files (provided directly by the Awesome Translator Volunteers) in with the final product. If some translation is not included in the actual plugin even when the plugin has the capability to be translated, you can submit the final translation to us for consideration in the next update by posting on our forums OR you can include the translation in your own live or local WordPress install directly for your own use. More info on how to include your own language specific file for your own WordPress sites is in the resources listed in #3 above.
*5 : A translation included in with the final product does not guarantee the accuracy or quality of the translation. These files are from the Awesome Translator Volunteers, and correction of these files is also done by those Awesome Translator Volunteers.
*6 : If a translation is very inaccurate or incomplete, we can put out a request for a new translation from the volunteer community, or remove the translation from the packaged and final product. You can also let us know of any inaccuracies in any existing translation files by the Awesome Volunteers by providing us with the corrected final files. Please remember: we only accept final and full translation files that you yourself have already created or packaged properly. If you let us know only of the actual inaccuracies without providing the final correct files, we cannot make such changes ourselves to the translation files.
*7 : Unfortunately, PluginBuddy cannot work on, help with, create, nor make any updates to any specific translation files you may have, or may be working on, or want to work on. Our Awesome Volunteers do that and simply give us the final files for inclusion or consideration.
*8 : If you have corrections for any existing translation in form of final proper format translation files for an existing language, OR want to provide the final and proper translation files for a new language, please post a new thread in the appropriate product category in the [http://ithemes.com/forum/ PluginBuddy Support Forums] with the final translations files. If you have any support questions on how to create or make language specific translation files, or how translation files work, you can do so on the [http://wordpress.org/support/ WordPress forums], as such support questions are outside the scope of what PluginBuddy support guarantees with your iThemes membership.
*9 : Any final translation file provided by you (or any other Awesome Volunteer) on the support forums will then be saved and filed as a future enhancement request for the future updates of the plugin(s) in question. In your support forum thread, where you share the final complete translation files you inclusion, you can upload your files directly to the forums OR upload them somewhere and link to them in your support forum thread. We will then download and save such files. Remember please: we cannot guarantee looking inside such files or verifying that they are correct in any manner (because of so many languages in the world and so many possible language files everywhere).

Thank you SO MUCH for being interested in providing translation files for our PluginBuddy plugins. We hope you will become one of our Awesome Translator Volunteers, in addition to being our AWESOME CUSTOMER, and create/update any language-specific translation file package and provide it to us so that we can consider including it in future updates.

===Resources for understanding, creating, updating and submitting final translation files===
*Here are the 3 official resources again which you can use to create, update, start work on and finish translation on any of the translation-capable PluginBuddy plugins:
**1 : [http://codex.wordpress.org/WordPress_in_Your_Language WordPress in Your Language]
**2 : [http://codex.wordpress.org/Translating_WordPress Translating WordPress]
**3 : [http://codex.wordpress.org/I18n_for_WordPress_Developers What WordPress Localization in Plugins is mainly about]

=Extra Customizations=
While any extra customization of any PluginBuddy Plugin is beyond the scope of the official support, we do from time to time offer different tips and tutorials on editing the awesome PluginBuddy plugins to better fit your individual needs. All such edits are, however, beyond what is officially supported and provided in the actual plugin admin panel and officially stated features on the individual plugin pages. No official support is provided nor guaranteed in, before, during, after or related to anything resulting from any such edits/customizations.

No support is provided on any of these extra customizations. Any of the steps mentioned in any of these extra custom edits may change at any time depending on newer versions of the plugins being released. Any use or customization of anything, beyond what is provided by default inside the plugin admin menu, means you are proceeding at your own risk and that you accept 100% responsibility and liability for everything you change or modify in any manner in the plugin. Your purchase and use of any PluginBuddy plugin implies and shows that you are buying and using PluginBuddy plugin(s) the way it(they) came in their original unmodified form, with no exceptions.

*Remember:
**[http://pluginbuddy.com/purchase/backupbuddy/ Make a backup of your entire site with BackupBuddy] before making any edits!
** PluginBuddy only supports the official unedited, unmodified versions of all PluginBuddy plugins.
** Use a good text editor to make any file changes. Again, maintain backups!
** Any changes you make to files WILL MOST PROBABLY be lost when the plugin is upgraded to any newer version.
** You are 100% responsible and liable for anything resulting from any of these changes.
** No support is provided nor guaranteed on any of these extra changes in any form or shape, whatsoever, regardless of who suggested these custom edits or suggestions.
** Any extra customization info or suggestion is added voluntarily by PluginBuddy staff to help users as much as possible, even if such customization is outside the scope of any membership support.
** Whether a PluginBuddy staff or representative offered or suggested the edit/customization, another customer or anyone else, PluginBuddy does not officially support nor provide any official support on any such edits.
** We cannot guarantee providing any support on any edits or customization tips we provide.
** Absolutely no support is guaranteed in any manner on any of our free plugins, whether or not there is any customization/edit involved.

=External Plugins Compatibility=

PluginBuddy does not promise, guarantee or provide support for any compatibility with any external plugin. If any PluginBuddy Plugin works without any problems when used with any external plugin in question, that means the PluginBuddy Plugin is most probably working without any issues overall. PluginBuddy is not responsible for making PluginBuddy plugins work in any manner, whether custom, fully, fixed or other, with any external non-PluginBuddy plugins. PluginBuddy is also not responsible for providing any support whatsoever for any external plugin, whether or not such an external plugin is used along with any PluginBuddy plugin.

=Free Plugins=

Free plugins are provided as is. There is no guaranteed support that comes with them. Guaranteed support is limited only and mainly for our premium unmodified plugins.

=Bugs, Features and ETA on new updates=

With every new release of any plugin, there may be a new bug or two. You may also want to have new features added to specific plugins. All existing versions of all plugins can have bugs reported OR new features suggested. All of this is done via the [http://ithemes.com/forum official forums].

New updates are also usually released regularly and at the same time, at very different paces, depending on the current number of bugs, features, new plans and tasks at hand. Therefore it is the official policy that there is NO pre-defined ETA on any bug fix, feature imeplemention OR new update OR new plugin roll-out UNLESS otherwise specified specifically in writing somewhere by an official iThemes employee.

==Bugs, bug reports and bug fixes==

Bug reports are filed and noted as they are encountered (thanks for reporting them to us!). There is never any ETA on any bug fixes unless otherwise noted.

==Feature Requests==

Feature requests and feature suggestions are basically future suggested features that users can suggest, and/or future features PluginBuddy may consider adding to the future versions of the plugin(s) in question (again, thanks for suggesting new features!).

There is no guaranteed ETA on when such feature requests will be implemented, unless otherwise noted. All suggested features are just that: suggestions. They remain suggestions until they're confirmed as officially in the works and to be included. Even then, unless a feature is actually rolled out publicly, there is no guarantee any feature suggestion will be implemented. We do our best to try and accommodate as many feature suggestions as possible.

Also, there is no guarantee that any feature request suggested will be implemented, unless otherwise noted.

==ETA on new updates==

Just like bug fixes and new features, there is never a guaranteed date nor a guaranteed time frame on when new updates will roll out. We work every single day of the week, all the time, on our plugins and thus every day there is something new and improved happening in almost all our plugins daily. Whenever we are ready to release any new updates publicly, you'll find out by seeing the plugin update notice in your WordPress OR in your [http://ithemes.com/member/member.php Member's area].

=What does BETA mean?=

Some of PluginBuddy plugins may be in Beta status OR may have Beta features. BETA simply means that some feature or specific part of the plugin is currently still in testing mode, and can cause issues if not used properly. All BETA plugins/features are not yet 100% stable, and thus should NOT be relied on to be working properly OR working at all. Throughout the iThemes Codex, any time the word "Beta" is used in any form, it refers to Beta plugins, Beta features, Beta status and/or anything related to the Beta nature that is officially announced or mentioned as such by any iThemes staff or on any of the Plugin pages, or in this Codex.

Beta implies that any new features or plugins are very close to being released as 100% working very soon, and that there may still be some issues to fix or test more before removing the Beta status. Since no single software of any kind can be tested under every system and site configuration in the world, the Beta status enables the Beta features to be tested out by as many people on as many different websites and configurations as possible.

*Some points to keep in mind when using any BETA plugin/feature:
**1 : Make [http://pluginbuddy.com/purchase/backupbuddy/ FULL WordPress backups] before using ANY beta feature.
**2 : Beta means that the current software feature is NOT complete, and that you are NOT forced to use such a feature at all. You are advised to WAIT until the BETA status is removed.
**3 : Using any Beta feature of any kind, whether it is an entire plugin or something inside a plugin, means and shows that you are fully accepting any liability for any risks involved.
**4 : Using any Beta feature of any kind, whether it is an entire plugin or something inside a plugin, means and shows that you are fully aware that there are all different kinds of risks involved with such features.
**5 : If you are concerned about your important data or anything bad that might happen as a result of using any Beta feature, do NOT use such Beta features.
**6 : ALWAYS make full [http://pluginbuddy.com/purchase/backupbuddy/ BackupBuddy Backups of all your important data] before using any Beta software, whether that Beta software is from PluginBuddy or from any other place.
**7 : If any issues are found in Beta, they are usually added to the list of bug fixes to be released as a whole, or for the next big update, instead of being updated OR fixed individually on a case by case basis.
**8 : Beta features are recommended to test and play with on test sites/servers and configurations with any dummy data, as long as you have [http://pluginbuddy.com/purchase/backupbuddy/ full backups of all important data] still.
**9 : iThemes is not liable nor cannot be held accountable for any unwanted results resulting from the use of BETA features.
**10 : The very name and nature of BETA shows clearly, without any doubt, that there will most probably be issues and problems involved when such labeled features are used anywhere.
**11 : Support for Beta features may be very limited. We usually simply collect all reports related to Beta features and collect them all for one big update in the future.
**12 : If you lose any important data or settings anywhere, or encounter damaged data or settings anywhere, because of any Beta feature, we will not be able to help you and will simply tell you to revert to your previous [http://pluginbuddy.com/purchase/backupbuddy/ backups]. We will also tell you to always wait for BETA status to be removed before using any such features.

If you do not fully understand what Beta means, OR are not willing to fully accept and be fully liable for any risks involved because of using such Beta software, you should NOT use the Beta software in any manner. In such a case, you should simply wait until the Beta status is removed.

*[http://pluginbuddy.com/what-does-beta-mean/ Blog post announcing what BETA means]

=PluginBuddy Licenses=

==Licenses Issues due to Plugin Conflicts==

Some times, external plugins may cause issues in detaching, deleting, generating OR saving license keys. Such plugins may also cause issues when you want to manually or automatically upgrade plugins when you try to solve licensing issues.

Following is a list of currently known plugins which cause license detaching, deleting, generating OR saving issues. Please disable the following plugins, even temporarily, while you perform all the steps of manually OR automatically upgrading the PluginBuddy plugins in question, and detaching, deleting, generating and saving license keys for them. Keep such plugins disabled UNTIL all license key issues are gone OR at least while you perform these steps.

*Plugins causing PluginBuddy licensing issues
**'''W3 Total Cache or WP Super Cache or WinCache :''' If you are using any caching plugin like '''W3 Total Cache''' or '''WP Super Cache''' or any PHP Extension like WinCache, please disable it temporarily and then carry out any required steps. You can re-enable the plugin or extension in the end after everything works in terms of the licenses.
***Fix: Follow the above steps to fix this issue. [http://ithemes.com/forum/index.php?/topic/19436-backupbuddy-license-issue/#p92171 Steps also explained by BackupBuddy customer Laura (thanks!)]
**'''Any other CACHING or related plugin or extension:''' Try disabling such plugins/extensions, performing the required steps, and then re-activating the Caching or related plugins/extensions in question.

*Related Links
**1 : [http://ithemes.com/forum/topic/24881-license-key-is-not-set-yet-or-invalid/page__view__findpost__p__116047 blm03 deactivated W3 Total Cache, which allowed the licenses to save correctly]
**2 : [http://ithemes.com/forum/topic/26022-cant-generate-a-license-for-my-domain/page__view__findpost__p__121072 Disabling WinCache extension for PHP fixes Licensing issues]
**3 : [http://ithemes.com/forum/topic/24737-backupbuddy-manage-licenses/page__view__findpost__p__115187 Karlos deactivated W3 Total Cache, and that fixed the licensing issues]
**4 : [http://ithemes.com/forum/topic/23481-license-issue-pluginbuddy-developer-to-backupbuddy-both-unlimited/page__view__findpost__p__110368 Disabling W3 Total Cache modules allowed Greg to license BackupBuddy without any issues]
**5 : [http://ithemes.com/forum/topic/23275-unable-to-get-license-to-stick/page__pid__109503#entry109503 W3 Total Cache causing licenses to be deleted after a while]
**6 : [http://ithemes.com/forum/topic/22964-cant-find-stylesheet-to-make-adjustments-to-slider/page__view__findpost__p__107933 W3 Total Cache not allowing licenses to be saved properly]
**7 : [http://ithemes.com/forum/topic/22859-bub-licenses-not-taking-effect/page__view__findpost__p__107476 W3 Total Cache not allowing licenses to be saved - easy solution!]
**8 : [http://ithemes.com/forum/index.php?/topic/19079-wont-let-me-set-a-license-key/#p91663 W3 Total Cache plugin conflict and solution]
**9 : [http://ithemes.com/forum/index.php?/topic/19436-backupbuddy-license-issue/#p92171 W3 Total Cache plugin conflict and solution]
**10 : [http://ithemes.com/forum/index.php?/topic/20228-key-does-not-work/#p95697 W3 Total Cache plugin conflict and solution]
**11 : [http://ithemes.com/forum/index.php?/topic/19041-license-problem-causes-loss-of-all-bb-settings-way-to-get-them-back/ WP Super Cache conflict and solution]

==Other Steps to Resolve Licensing Issues==

There are some reports that some users have issues with their license insides the Licenses area of different PluginBuddy plugins, including BackupBuddy.

Remember: All your PluginBuddy plugins, including BackupBuddy, will CONTINUE WORKING PERFECTLY even with these licensing issues. You can keep using the plugins exactly how you want them even during these licensing issues. Your plugins are NOT affected by this licensing situation in any manner.

Your membership is also completely fine and you have NOT lost any license(s). The issue is happening to some customers who simply need to upgrade manually to the latest version of their plugin, if the automatic upgrade does not work.

*Plugins with the update versions which remove this issue completely
**ALL PluginBuddy Products

*You can upgrade via one of the following:
**Automatically upgrade to the latest version
**Manually update by downloading the latest zip version of your PluginBuddy plugin from your Member's panel and then
***Overwrite your existing plugin directory via FTP with the new files.
***De-activate the existing plugin, delete it via your '''WordPress --> Plugins''' area and then upload the newly downloaded zip file. Then re-activate the plugin.
**That will remove the issue completely.
*DETACH the key and then RE-ATTACH the license key for the specific site in question IF licensing still shows issues AFTER manually upgrading to the latest version of the plugin in question (check your Member's area for the latest version download)
*Also make sure to DETACH the key, DELETE that same AND any other keys related to that specific site from the entire licenses area, and then GENERATE a new key for that site IF detaching and re-attaching the license key does not work AFTER manually upgrading (for example, manually upgrading to the latest BackupBuddy version - all plugins have their own latest version numbers - check your Member's area for the latest version download)

[http://ithemes.com/forum/index.php?/topic/6691-read-this-first-pluginbuddy-licensing-issues/page-2/#p85977 First reports]

ContactBuddy

2012-03-21T19:16:09Z

Bes: Added /* Change Label Names */ section

ContactBuddy is a plugin that allows users to add a simple contact form to widgets, posts, and pages on their website. The ContactBuddy forms contain the following fields: name, email, subject, message, and have the option of adding a recaptcha validator. Submissions to the forms are sent to the email address set by the admin.

[http://pluginbuddy.com/free-wordpress-plugins/contactbuddy/ Check out ContactBuddy]

Also check out our famous [http://pluginbuddy.com/purchase/emailbuddy/ EmailBuddy], which allows you to send email broadcasts to subscribers. It is a fully in-house email newsletter solution for your WordPress!

'''ContactBuddy is a free plugin, and thus support on it is limited and not guaranteed in any manner.''' Check out our [http://ithemes.com/codex/page/PluginBuddy#Free_Plugins Free Plugins] policies.

==Customize ContactBuddy==

====Extra Customizations Policies====
[http://ithemes.com/codex/page/PluginBuddy#Extra_Customizations Check out the official policy and details on any Extra Customizations]

====Change Input Fields====
You can change the width, border color or anything else for input fields in ContactBuddy by putting the related styling in your current WordPress theme's custom CSS file.

*For example, to change the width and border colors of the input fields, you add the following to your theme's CSS file:

<pre brush="css">
.contactbuddy-form ul li input.cbfit {
max-width:500px !important; /* change this to any width */
border-color: #004080; /* change this to any color */
}
</pre>
*Related thread
**http://ithemes.com/forum/index.php?/topic/18238-contact-buddy/

====Remove Bullets in OLDER IE Browsers====
Full info and fix available in the [http://ithemes.com/codex/page/General_Plugins_FAQ#Plugin_Display_Issue General PluginBuddy "Remove Bullets in OLDER IE Browsers" section].
*Related link:
**http://ithemes.com/forum/index.php?/topic/18347-another-css-issue/

====Allow Longer Admin Email Recipient Field====
By default, the ContactBuddy "Recipient Email Address" field allows up to 45 characters of data. This means you can enter in one or more than one comma-separated email addresses, as long as they all fit within the 45 character limit of that field. This can be changed to your needs.

'''In admin.php file, inside contactbuddy/classes folder, on line 293, change the "''45''" values (listed twice) to the exact numeric value that you would like.'''

That will change the length of the Recipient Email Address field in the ContactBuddy admin panel, allowing you to enter longer or more than one comma-separated email addresses.

*Related link
**http://ithemes.com/forum/index.php?/topic/18108-contact-buddy-quick-question/

====Change Label Names====

You can change the label names in ContactBuddy by modifying the contactbuddy.php file.

[http://ithemes.com/forum/topic/23854-add-label-elements/ See how to change label names in ContactBuddy]

BackupBuddy Multisite

2012-03-20T19:33:27Z

Bes: Replaced old image with new image of where to get ImportBuddy as of 2.2.35 /* BackupBuddy's IMPORTBUDDY.PHP File */

BackupBuddy Multisite is the '''NEW BETA''' feature of the latest BackupBuddy which allows you to backup, migrate, restore OR copy your Multisite from one location to another, or back to the same location. '''BETA''' means that at this time, any new error or problem may occur including, but not limited to, the restore not importing image links properly, sub-domains OR sub-directory paths giving permalink errors, helping your cat escape from your home, and more.

This page is updated regularly every week, since we are working with all our Multisite customers DAILY in getting more features, fixes and enhancements into BackupBuddy Beta updates as fast as we can. Soon, the BETA status will be removed to signify the official fully supported and fully tested '''BackupBuddy Multisite''' release. [http://ithemes.com/codex/index.php?title=BackupBuddy_Multisite&action=submit#Support_Questions Please let us know of any suggestions or questions in the forums]!

As of version 2.2.14, the single BackupBuddy product contains BOTH the standard BackupBuddy AND the new BackupBuddy Multisite Beta. Your single BackupBuddy does it all!

=Getting BackupBuddy Multisite=

====BackupBuddy Backup Plugin====
BackupBuddy Multisite BETA is now an integral part of BackupBuddy itself. You simply [http://pluginbuddy.com/purchase/backupbuddy/ Get BackupBuddy] and then download it from your [http://ithemes.com/member/member.php Member's Area].

====BackupBuddy's IMPORTBUDDY.PHP File====
The importbuddy.php file, which is the awesome file that helps you MIGRATE/RESTORE your BackupBuddy backups, now has a BETA version also that is used when you want to migrate or restore your BackupBuddy Multisite backups. You must use the BETA importbuddy.php to restore/migrate any BackupBuddy Multisite backup file.

* Here is an image of your '''BackupBuddy --> Backup & Restore''' area, where the latest BETA importbuddy.php download link is:
**[[File:Download-importbuddy-bes-zain.png|Image of where the latest BETA importbuddy.php download link is]]

=Installing BackupBuddy Multisite=

Since BackupBuddy Multisite BETA is now part of BackupBuddy, the Installation steps are now integrated and the differences explained in the [http://ithemes.com/codex/page/Installing_BackupBuddy standard BackupBuddy Installation] section.

=Running Backup, Migrating OR Restoring with BackupBuddy Multisite BETA=

Here is an actual video, from one of our many webinars (we have many regular webinars planned), with details on how to migrate or restore with BackupBuddy:

{{#ev:youtube|WYhLIK3KfK4|600|BackupBuddy Multisite}}

=Frequently Asked Questions=

====WordPress Multisite Domain Mapping and BackupBuddy Multisite====

BackupBuddy Multisite works perfectly with WordPress Multisite Domain Mapping. Here is a detailed video of what is possible and how it's exactly done (better to see something in addition to reading about it too ;) ):

{{#ev:youtube|oDM5v2Ymk1M|600|BackupBuddy Multisite}}

====Limitations of Multisite====

There are 2 limitations (and for good reasons) in WordPress Multisite itself which BackupBuddy of course goes through automatically:
* 1 : If your multisite install is sub-domain based, you cannot migrate or restore to a sub-directory within your web root.
* 2 : You can not change from sub-domains to sub-directories using BackupBuddy Multisite. You can not use BackupBuddy to migrate from a sub-domain based install to sub-directories or vice-versa.

====Known Issues====

The following are known issues of BackupBuddy Multisite:

* 1 : You can not currently migrate a Multiste installation to a sub-directory, or migrate a Multisite installation based in a sub-directory back to the root of the domain. We are currently working on enabling this feature.
* 2: You can not duplicate a mapped domain. We are currently working on enabling this feature.

====Support Questions====

All BackupBuddy Multisite support questions can be asked in the official [http://ithemes.com/forum/backupbuddy-ms/ BackupBuddy Multisite Forums].

All non-Multisite related BackupBuddy support questions can be asked in the official [http://ithemes.com/forum/backupbuddy/ BackupBuddy Forums].

All BackupBuddy Pre-Sales questions, for Multisite OR non-Multisite backups and restores/migrations, can be asked on the [http://ithemes.com/forum/pre-sales-and-other-inquiries/ Pre-Sales Forums], via the Live Chat (the Panda icon on top of [http://pluginbuddy.com/purchase/backupbuddy/ Get BackupBuddy Multisite] page), or by emailing sales@ithemes.com

=Additional Resources=
====Official Pages====
*[http://pluginbuddy.com/purchase/backupbuddy/ Get BackupBuddy]
*[http://ithemes.com/codex/page/BackupBuddy BackupBuddy Codex - Self-Hosted and Multisite combined]
====Blog Posts====
*[http://pluginbuddy.com/5-reasons-to-love-backupbuddy-with-new-wordpress-multisite-support/ 5 Reasons to Love BackupBuddy with Multisite Support - Blog Article]
*[http://pluginbuddy.com/backupbuddy-multisite-migration-expanded-features-in-beta-coming-soon/ BackupBuddy Multisite Migration - Expanded Features in Beta - Announcement]
*[http://pluginbuddy.com/backupbuddy-ms-released-as-a-beta/ BackupBuddy Multisite Released as Beta - Announcement]
*[http://pluginbuddy.com/how-backupbuddy-changed-my-business-model/ How BackupBuddy changed one of our customer's entire business model!]

File:Download-importbuddy-bes-zain.png

2012-03-20T19:32:34Z

Bes: Latest ImportBuddy shipped with BackupBuddy 2.2.35

Latest ImportBuddy shipped with BackupBuddy 2.2.35

PluginBuddy

2012-03-06T20:44:20Z

Bes: Change name a bit to clarify the purpose of the section /* Licensing Issues */

Welcome to the PluginBuddy Knowledge Base - Tutorials, Technical Information, Debugging Information, and more.

=Premium Plugins=
* [[Ajax-Edit-Comments]]
* [[BackupBuddy]]
* [[DisplayBuddy]]
** [[Accordion]]
** [[Billboard]]
** [[Carousel]]
** [[CopiousComments]]
** [[FeaturedPosts]]
** [[Rotating Images]]
** [[RotatingText]]
** [[Slides]]
** [[Slideshow]]
** [[Tipsy]]
** [[VideoShowcase]]
* [[EmailBuddy]]
* [[Frolic]]
* [[LoopBuddy]]
* [[Mobile]]
* [[TailoredLogin]]
* [[ThumbsUp]]
* [[VidEmbed]]

=Free Plugins (active)=
* [[Featured Text]]
* [[PB-Tweet]]
* [[ServerBuddy]]
* [[Tabber Widget]]
* [[ThemeMan]]
* [[S3 URLS]]
* [[YOURLS]]
* [[ContactBuddy]]

=Free Plugins (inactive)=
* [[WP Easy Uploader]]
* [[WP Developer Assistant]]
* [[Easy Theme and Plugin Updater]]
* [[Current Date & Time Widget]]

''[[:Category:PluginBuddy|View all PluginBuddy Wiki Pages]]''

=Misc. Documentation=
==Frequently Asked (Plugin) Questions==
*[[General Plugins FAQ]]

==License Manager Tutorial and Information==
*[[License Manager]]
==PHP Development & Advanced==
*[[.htaccess]]
*[[PHP]]
*[[Arrays]]

[[Category:PluginBuddy]]

=Translations (localization / internationalization)=

Many PluginBuddy plugins come with translation capability. That means such PluginBuddy plugins can be translated (aka localized) to other languages.

===How Translations Work===

PluginBuddy provides the capability to have a translation in such plugins. Anyone wanting to enhance PluginBuddy with specific language translations can do so voluntarily via Translation Files. Translation Files are simply language files created fully and solely by the volunteer community which use the already built in translation-capable features in many of the PluginBuddy plugins to allow such plugins to show text or outputs in different languages. Making PluginBuddy translation-capable is done by PluginBuddy. Creating, updating and sending in any language specific translation files to PluginBuddy is done by the volunteer community.

Anyone can create translation files, package them into the proper format and give PluginBuddy the final translated files that we will try to include in the next update for the plugin in question. We call such awesome people, who create or update the translation files and send us the full translation package files, '''Awesome Translator Volunteers''', and we are really thankful that they take the time to do such an awesome thing.

If you want to help us, you can translate any existing PluginBuddy plugin which supports internationalization (another way of saying localization or translation-capable) and then, once you're fully done, simply let us know in the forums the link to the final language files that we can directly save and simply try to include in any future updates for the plugin(s) in question.

===Tips on how to localize any PluginBuddy Plugin to any non-English language===

The following 9 tips can help you figure out how to approach translations, how to create translations, and how to send us the final translated file for any translation-capable PluginBuddy plugin:

*1 : Many of the PluginBuddy plugins are internationalized, meaning they have the capability to be translated, via actual external translation files, by any non-iThemes-staff Awesome Translator Volunteer who wishes such plugins to be translated to their language.
*2 : If a PluginBuddy plugin is currently not internationalized or you're not sure if it is, you can ask us in the [http://ithemes.com/forum Support Forums] and we'll let you know, or we'll have it included as a future translation feature request. After the translation capability is added to such a plugin, you can submit the actual translation file. Please remember though: we cannot help with creating, understanding or making any language translation files. Our Awesome Translator Volunteers do that voluntarily (you can too! keep on reading) and fully on their own.
*3 : There are MANY resources which teach you how to create and work with WordPress language files. Following are the official 3 directly by the WordPress community:
**1 : [http://codex.wordpress.org/WordPress_in_Your_Language WordPress in Your Language]
**2 : [http://codex.wordpress.org/Translating_WordPress Translating WordPress]
**3 : [http://codex.wordpress.org/I18n_for_WordPress_Developers What WordPress Localization in Plugins is mainly about]
*4 : Translations are sent in from volunteers from all over the world. As a courtesy, we sometimes package the actual language translation files (provided directly by the Awesome Translator Volunteers) in with the final product. If some translation is not included in the actual plugin even when the plugin has the capability to be translated, you can submit the final translation to us for consideration in the next update by posting on our forums OR you can include the translation in your own live or local WordPress install directly for your own use. More info on how to include your own language specific file for your own WordPress sites is in the resources listed in #3 above.
*5 : A translation included in with the final product does not guarantee the accuracy or quality of the translation. These files are from the Awesome Translator Volunteers, and correction of these files is also done by those Awesome Translator Volunteers.
*6 : If a translation is very inaccurate or incomplete, we can put out a request for a new translation from the volunteer community, or remove the translation from the packaged and final product. You can also let us know of any inaccuracies in any existing translation files by the Awesome Volunteers by providing us with the corrected final files. Please remember: we only accept final and full translation files that you yourself have already created or packaged properly. If you let us know only of the actual inaccuracies without providing the final correct files, we cannot make such changes ourselves to the translation files.
*7 : Unfortunately, PluginBuddy cannot work on, help with, create, nor make any updates to any specific translation files you may have, or may be working on, or want to work on. Our Awesome Volunteers do that and simply give us the final files for inclusion or consideration.
*8 : If you have corrections for any existing translation in form of final proper format translation files for an existing language, OR want to provide the final and proper translation files for a new language, please post a new thread in the appropriate product category in the [http://ithemes.com/forum/ PluginBuddy Support Forums] with the final translations files. If you have any support questions on how to create or make language specific translation files, or how translation files work, you can do so on the [http://wordpress.org/support/ WordPress forums], as such support questions are outside the scope of what PluginBuddy support guarantees with your iThemes membership.
*9 : Any final translation file provided by you (or any other Awesome Volunteer) on the support forums will then be saved and filed as a future enhancement request for the future updates of the plugin(s) in question. In your support forum thread, where you share the final complete translation files you inclusion, you can upload your files directly to the forums OR upload them somewhere and link to them in your support forum thread. We will then download and save such files. Remember please: we cannot guarantee looking inside such files or verifying that they are correct in any manner (because of so many languages in the world and so many possible language files everywhere).

Thank you SO MUCH for being interested in providing translation files for our PluginBuddy plugins. We hope you will become one of our Awesome Translator Volunteers, in addition to being our AWESOME CUSTOMER, and create/update any language-specific translation file package and provide it to us so that we can consider including it in future updates.

===Resources for understanding, creating, updating and submitting final translation files===
*Here are the 3 official resources again which you can use to create, update, start work on and finish translation on any of the translation-capable PluginBuddy plugins:
**1 : [http://codex.wordpress.org/WordPress_in_Your_Language WordPress in Your Language]
**2 : [http://codex.wordpress.org/Translating_WordPress Translating WordPress]
**3 : [http://codex.wordpress.org/I18n_for_WordPress_Developers What WordPress Localization in Plugins is mainly about]

=Extra Customizations=
While any extra customization of any PluginBuddy Plugin is beyond the scope of the official support, we do from time to time offer different tips and tutorials on editing the awesome PluginBuddy plugins to better fit your individual needs. All such edits are, however, beyond what is officially supported and provided in the actual plugin admin panel and officially stated features on the individual plugin pages. No official support is provided nor guaranteed in, before, during, after or related to anything resulting from any such edits/customizations.

No support is provided on any of these extra customizations. Any of the steps mentioned in any of these extra custom edits may change at any time depending on newer versions of the plugins being released. Any use or customization of anything, beyond what is provided by default inside the plugin admin menu, means you are proceeding at your own risk and that you accept 100% responsibility and liability for everything you change or modify in any manner in the plugin. Your purchase and use of any PluginBuddy plugin implies and shows that you are buying and using PluginBuddy plugin(s) the way it(they) came in their original unmodified form, with no exceptions.

*Remember:
**[http://pluginbuddy.com/purchase/backupbuddy/ Make a backup of your entire site with BackupBuddy] before making any edits!
** PluginBuddy only supports the official unedited, unmodified versions of all PluginBuddy plugins.
** Use a good text editor to make any file changes. Again, maintain backups!
** Any changes you make to files WILL MOST PROBABLY be lost when the plugin is upgraded to any newer version.
** You are 100% responsible and liable for anything resulting from any of these changes.
** No support is provided nor guaranteed on any of these extra changes in any form or shape, whatsoever, regardless of who suggested these custom edits or suggestions.
** Any extra customization info or suggestion is added voluntarily by PluginBuddy staff to help users as much as possible, even if such customization is outside the scope of any membership support.
** Whether a PluginBuddy staff or representative offered or suggested the edit/customization, another customer or anyone else, PluginBuddy does not officially support nor provide any official support on any such edits.
** We cannot guarantee providing any support on any edits or customization tips we provide.
** Absolutely no support is guaranteed in any manner on any of our free plugins, whether or not there is any customization/edit involved.

=External Plugins Compatibility=

PluginBuddy does not promise, guarantee or provide support for any compatibility with any external plugin. If any PluginBuddy Plugin works without any problems when used with any external plugin in question, that means the PluginBuddy Plugin is most probably working without any issues overall. PluginBuddy is not responsible for making PluginBuddy plugins work in any manner, whether custom, fully, fixed or other, with any external non-PluginBuddy plugins. PluginBuddy is also not responsible for providing any support whatsoever for any external plugin, whether or not such an external plugin is used along with any PluginBuddy plugin.

=Free Plugins=

Free plugins are provided as is. There is no guaranteed support that comes with them. Guaranteed support is limited only and mainly for our premium unmodified plugins.

=Bugs, Features and ETA on new updates=

With every new release of any plugin, there may be a new bug or two. You may also want to have new features added to specific plugins. All existing versions of all plugins can have bugs reported OR new features suggested. All of this is done via the [http://ithemes.com/forum official forums].

New updates are also usually released regularly and at the same time, at very different paces, depending on the current number of bugs, features, new plans and tasks at hand. Therefore it is the official policy that there is NO pre-defined ETA on any bug fix, feature imeplemention OR new update OR new plugin roll-out UNLESS otherwise specified specifically in writing somewhere by an official iThemes employee.

==Bugs, bug reports and bug fixes==

Bug reports are filed and noted as they are encountered (thanks for reporting them to us!). There is never any ETA on any bug fixes unless otherwise noted.

==Feature Requests==

Feature requests and feature suggestions are basically future suggested features that users can suggest, and/or future features PluginBuddy may consider adding to the future versions of the plugin(s) in question (again, thanks for suggesting new features!).

There is no guaranteed ETA on when such feature requests will be implemented, unless otherwise noted. All suggested features are just that: suggestions. They remain suggestions until they're confirmed as officially in the works and to be included. Even then, unless a feature is actually rolled out publicly, there is no guarantee any feature suggestion will be implemented. We do our best to try and accommodate as many feature suggestions as possible.

Also, there is no guarantee that any feature request suggested will be implemented, unless otherwise noted.

==ETA on new updates==

Just like bug fixes and new features, there is never a guaranteed date nor a guaranteed time frame on when new updates will roll out. We work every single day of the week, all the time, on our plugins and thus every day there is something new and improved happening in almost all our plugins daily. Whenever we are ready to release any new updates publicly, you'll find out by seeing the plugin update notice in your WordPress OR in your [http://ithemes.com/member/member.php Member's area].

=What does BETA mean?=

Some of PluginBuddy plugins may be in Beta status OR may have Beta features. BETA simply means that some feature or specific part of the plugin is currently still in testing mode, and can cause issues if not used properly. All BETA plugins/features are not yet 100% stable, and thus should NOT be relied on to be working properly OR working at all. Throughout the iThemes Codex, any time the word "Beta" is used in any form, it refers to Beta plugins, Beta features, Beta status and/or anything related to the Beta nature that is officially announced or mentioned as such by any iThemes staff or on any of the Plugin pages, or in this Codex.

Beta implies that any new features or plugins are very close to being released as 100% working very soon, and that there may still be some issues to fix or test more before removing the Beta status. Since no single software of any kind can be tested under every system and site configuration in the world, the Beta status enables the Beta features to be tested out by as many people on as many different websites and configurations as possible.

*Some points to keep in mind when using any BETA plugin/feature:
**1 : Make [http://pluginbuddy.com/purchase/backupbuddy/ FULL WordPress backups] before using ANY beta feature.
**2 : Beta means that the current software feature is NOT complete, and that you are NOT forced to use such a feature at all. You are advised to WAIT until the BETA status is removed.
**3 : Using any Beta feature of any kind, whether it is an entire plugin or something inside a plugin, means and shows that you are fully accepting any liability for any risks involved.
**4 : Using any Beta feature of any kind, whether it is an entire plugin or something inside a plugin, means and shows that you are fully aware that there are all different kinds of risks involved with such features.
**5 : If you are concerned about your important data or anything bad that might happen as a result of using any Beta feature, do NOT use such Beta features.
**6 : ALWAYS make full [http://pluginbuddy.com/purchase/backupbuddy/ BackupBuddy Backups of all your important data] before using any Beta software, whether that Beta software is from PluginBuddy or from any other place.
**7 : If any issues are found in Beta, they are usually added to the list of bug fixes to be released as a whole, or for the next big update, instead of being updated OR fixed individually on a case by case basis.
**8 : Beta features are recommended to test and play with on test sites/servers and configurations with any dummy data, as long as you have [http://pluginbuddy.com/purchase/backupbuddy/ full backups of all important data] still.
**9 : iThemes is not liable nor cannot be held accountable for any unwanted results resulting from the use of BETA features.
**10 : The very name and nature of BETA shows clearly, without any doubt, that there will most probably be issues and problems involved when such labeled features are used anywhere.
**11 : Support for Beta features may be very limited. We usually simply collect all reports related to Beta features and collect them all for one big update in the future.
**12 : If you lose any important data or settings anywhere, or encounter damaged data or settings anywhere, because of any Beta feature, we will not be able to help you and will simply tell you to revert to your previous [http://pluginbuddy.com/purchase/backupbuddy/ backups]. We will also tell you to always wait for BETA status to be removed before using any such features.

If you do not fully understand what Beta means, OR are not willing to fully accept and be fully liable for any risks involved because of using such Beta software, you should NOT use the Beta software in any manner. In such a case, you should simply wait until the Beta status is removed.

*[http://pluginbuddy.com/what-does-beta-mean/ Blog post announcing what BETA means]

=PluginBuddy Licenses=

==Licenses Issues due to Plugin Conflicts==

Some times, external plugins may cause issues in detaching, deleting, generating OR saving license keys. Such plugins may also cause issues when you want to manually or automatically upgrade plugins when you try to solve licensing issues.

Following is a list of currently known plugins which cause license detaching, deleting, generating OR saving issues. Please disable the following plugins, even temporarily, while you perform all the steps of manually OR automatically upgrading the PluginBuddy plugins in question, and detaching, deleting, generating and saving license keys for them. Keep such plugins disabled UNTIL all license key issues are gone OR at least while you perform these steps.

*Plugins causing PluginBuddy licensing issues
**'''W3 Total Cache or WP Super Cache :''' If you are using any caching plugin like '''W3 Total Cache''' or '''WP Super Cache''', please disable it temporarily and then carry out any required steps. You can re-enable the plugin in the end after everything works in terms of the licenses.
***Fix: Follow the above steps to fix this issue. [http://ithemes.com/forum/index.php?/topic/19436-backupbuddy-license-issue/#p92171 Steps also explained by BackupBuddy customer Laura (thanks!)]
**'''Any other CACHING or related plugin:''' Try disabling such plugins, performing the required steps, and then re-activating the Caching or related plugins in question.

*Related Links
**1 : [http://ithemes.com/forum/topic/24881-license-key-is-not-set-yet-or-invalid/page__view__findpost__p__116047 blm03 deactivated W3 Total Cache, which allowed the licenses to save correctly]
**2 : [http://ithemes.com/forum/topic/24737-backupbuddy-manage-licenses/page__view__findpost__p__115187 Karlos deactivated W3 Total Cache, and that fixed the licensing issues]
**3 : [http://ithemes.com/forum/topic/23481-license-issue-pluginbuddy-developer-to-backupbuddy-both-unlimited/page__view__findpost__p__110368 Disabling W3 Total Cache modules allowed Greg to license BackupBuddy without any issues]
**4 : [http://ithemes.com/forum/topic/23275-unable-to-get-license-to-stick/page__pid__109503#entry109503 W3 Total Cache causing licenses to be deleted after a while]
**5 : [http://ithemes.com/forum/topic/22964-cant-find-stylesheet-to-make-adjustments-to-slider/page__view__findpost__p__107933 W3 Total Cache not allowing licenses to be saved properly]
**6 : [http://ithemes.com/forum/topic/22859-bub-licenses-not-taking-effect/page__view__findpost__p__107476 W3 Total Cache not allowing licenses to be saved - easy solution!]
**7 : [http://ithemes.com/forum/index.php?/topic/19079-wont-let-me-set-a-license-key/#p91663 W3 Total Cache plugin conflict and solution]
**8 : [http://ithemes.com/forum/index.php?/topic/19436-backupbuddy-license-issue/#p92171 W3 Total Cache plugin conflict and solution]
**9 : [http://ithemes.com/forum/index.php?/topic/20228-key-does-not-work/#p95697 W3 Total Cache plugin conflict and solution]
**10 : [http://ithemes.com/forum/index.php?/topic/19041-license-problem-causes-loss-of-all-bb-settings-way-to-get-them-back/ WP Super Cache conflict and solution]

==Other Steps to Resolve Licensing Issues==

There are some reports that some users have issues with their license insides the Licenses area of different PluginBuddy plugins, including BackupBuddy.

Remember: All your PluginBuddy plugins, including BackupBuddy, will CONTINUE WORKING PERFECTLY even with these licensing issues. You can keep using the plugins exactly how you want them even during these licensing issues. Your plugins are NOT affected by this licensing situation in any manner.

Your membership is also completely fine and you have NOT lost any license(s). The issue is happening to some customers who simply need to upgrade manually to the latest version of their plugin, if the automatic upgrade does not work.

*Plugins with the update versions which remove this issue completely
**ALL PluginBuddy Products

*You can upgrade via one of the following:
**Automatically upgrade to the latest version
**Manually update by downloading the latest zip version of your PluginBuddy plugin from your Member's panel and then
***Overwrite your existing plugin directory via FTP with the new files.
***De-activate the existing plugin, delete it via your '''WordPress --> Plugins''' area and then upload the newly downloaded zip file. Then re-activate the plugin.
**That will remove the issue completely.
*DETACH the key and then RE-ATTACH the license key for the specific site in question IF licensing still shows issues AFTER manually upgrading to the latest version of the plugin in question (check your Member's area for the latest version download)
*Also make sure to DETACH the key, DELETE that same AND any other keys related to that specific site from the entire licenses area, and then GENERATE a new key for that site IF detaching and re-attaching the license key does not work AFTER manually upgrading (for example, manually upgrading to the latest BackupBuddy version - all plugins have their own latest version numbers - check your Member's area for the latest version download)

[http://ithemes.com/forum/index.php?/topic/6691-read-this-first-pluginbuddy-licensing-issues/page-2/#p85977 First reports]

PluginBuddy

2012-03-06T20:43:00Z

Bes: Enhanced name of the section to clarify its relation to the Licensing Issues /* Plugin Conflicts */

Welcome to the PluginBuddy Knowledge Base - Tutorials, Technical Information, Debugging Information, and more.

=Premium Plugins=
* [[Ajax-Edit-Comments]]
* [[BackupBuddy]]
* [[DisplayBuddy]]
** [[Accordion]]
** [[Billboard]]
** [[Carousel]]
** [[CopiousComments]]
** [[FeaturedPosts]]
** [[Rotating Images]]
** [[RotatingText]]
** [[Slides]]
** [[Slideshow]]
** [[Tipsy]]
** [[VideoShowcase]]
* [[EmailBuddy]]
* [[Frolic]]
* [[LoopBuddy]]
* [[Mobile]]
* [[TailoredLogin]]
* [[ThumbsUp]]
* [[VidEmbed]]

=Free Plugins (active)=
* [[Featured Text]]
* [[PB-Tweet]]
* [[ServerBuddy]]
* [[Tabber Widget]]
* [[ThemeMan]]
* [[S3 URLS]]
* [[YOURLS]]
* [[ContactBuddy]]

=Free Plugins (inactive)=
* [[WP Easy Uploader]]
* [[WP Developer Assistant]]
* [[Easy Theme and Plugin Updater]]
* [[Current Date & Time Widget]]

''[[:Category:PluginBuddy|View all PluginBuddy Wiki Pages]]''

=Misc. Documentation=
==Frequently Asked (Plugin) Questions==
*[[General Plugins FAQ]]

==License Manager Tutorial and Information==
*[[License Manager]]
==PHP Development & Advanced==
*[[.htaccess]]
*[[PHP]]
*[[Arrays]]

[[Category:PluginBuddy]]

=Translations (localization / internationalization)=

Many PluginBuddy plugins come with translation capability. That means such PluginBuddy plugins can be translated (aka localized) to other languages.

===How Translations Work===

PluginBuddy provides the capability to have a translation in such plugins. Anyone wanting to enhance PluginBuddy with specific language translations can do so voluntarily via Translation Files. Translation Files are simply language files created fully and solely by the volunteer community which use the already built in translation-capable features in many of the PluginBuddy plugins to allow such plugins to show text or outputs in different languages. Making PluginBuddy translation-capable is done by PluginBuddy. Creating, updating and sending in any language specific translation files to PluginBuddy is done by the volunteer community.

Anyone can create translation files, package them into the proper format and give PluginBuddy the final translated files that we will try to include in the next update for the plugin in question. We call such awesome people, who create or update the translation files and send us the full translation package files, '''Awesome Translator Volunteers''', and we are really thankful that they take the time to do such an awesome thing.

If you want to help us, you can translate any existing PluginBuddy plugin which supports internationalization (another way of saying localization or translation-capable) and then, once you're fully done, simply let us know in the forums the link to the final language files that we can directly save and simply try to include in any future updates for the plugin(s) in question.

===Tips on how to localize any PluginBuddy Plugin to any non-English language===

The following 9 tips can help you figure out how to approach translations, how to create translations, and how to send us the final translated file for any translation-capable PluginBuddy plugin:

*1 : Many of the PluginBuddy plugins are internationalized, meaning they have the capability to be translated, via actual external translation files, by any non-iThemes-staff Awesome Translator Volunteer who wishes such plugins to be translated to their language.
*2 : If a PluginBuddy plugin is currently not internationalized or you're not sure if it is, you can ask us in the [http://ithemes.com/forum Support Forums] and we'll let you know, or we'll have it included as a future translation feature request. After the translation capability is added to such a plugin, you can submit the actual translation file. Please remember though: we cannot help with creating, understanding or making any language translation files. Our Awesome Translator Volunteers do that voluntarily (you can too! keep on reading) and fully on their own.
*3 : There are MANY resources which teach you how to create and work with WordPress language files. Following are the official 3 directly by the WordPress community:
**1 : [http://codex.wordpress.org/WordPress_in_Your_Language WordPress in Your Language]
**2 : [http://codex.wordpress.org/Translating_WordPress Translating WordPress]
**3 : [http://codex.wordpress.org/I18n_for_WordPress_Developers What WordPress Localization in Plugins is mainly about]
*4 : Translations are sent in from volunteers from all over the world. As a courtesy, we sometimes package the actual language translation files (provided directly by the Awesome Translator Volunteers) in with the final product. If some translation is not included in the actual plugin even when the plugin has the capability to be translated, you can submit the final translation to us for consideration in the next update by posting on our forums OR you can include the translation in your own live or local WordPress install directly for your own use. More info on how to include your own language specific file for your own WordPress sites is in the resources listed in #3 above.
*5 : A translation included in with the final product does not guarantee the accuracy or quality of the translation. These files are from the Awesome Translator Volunteers, and correction of these files is also done by those Awesome Translator Volunteers.
*6 : If a translation is very inaccurate or incomplete, we can put out a request for a new translation from the volunteer community, or remove the translation from the packaged and final product. You can also let us know of any inaccuracies in any existing translation files by the Awesome Volunteers by providing us with the corrected final files. Please remember: we only accept final and full translation files that you yourself have already created or packaged properly. If you let us know only of the actual inaccuracies without providing the final correct files, we cannot make such changes ourselves to the translation files.
*7 : Unfortunately, PluginBuddy cannot work on, help with, create, nor make any updates to any specific translation files you may have, or may be working on, or want to work on. Our Awesome Volunteers do that and simply give us the final files for inclusion or consideration.
*8 : If you have corrections for any existing translation in form of final proper format translation files for an existing language, OR want to provide the final and proper translation files for a new language, please post a new thread in the appropriate product category in the [http://ithemes.com/forum/ PluginBuddy Support Forums] with the final translations files. If you have any support questions on how to create or make language specific translation files, or how translation files work, you can do so on the [http://wordpress.org/support/ WordPress forums], as such support questions are outside the scope of what PluginBuddy support guarantees with your iThemes membership.
*9 : Any final translation file provided by you (or any other Awesome Volunteer) on the support forums will then be saved and filed as a future enhancement request for the future updates of the plugin(s) in question. In your support forum thread, where you share the final complete translation files you inclusion, you can upload your files directly to the forums OR upload them somewhere and link to them in your support forum thread. We will then download and save such files. Remember please: we cannot guarantee looking inside such files or verifying that they are correct in any manner (because of so many languages in the world and so many possible language files everywhere).

Thank you SO MUCH for being interested in providing translation files for our PluginBuddy plugins. We hope you will become one of our Awesome Translator Volunteers, in addition to being our AWESOME CUSTOMER, and create/update any language-specific translation file package and provide it to us so that we can consider including it in future updates.

===Resources for understanding, creating, updating and submitting final translation files===
*Here are the 3 official resources again which you can use to create, update, start work on and finish translation on any of the translation-capable PluginBuddy plugins:
**1 : [http://codex.wordpress.org/WordPress_in_Your_Language WordPress in Your Language]
**2 : [http://codex.wordpress.org/Translating_WordPress Translating WordPress]
**3 : [http://codex.wordpress.org/I18n_for_WordPress_Developers What WordPress Localization in Plugins is mainly about]

=Extra Customizations=
While any extra customization of any PluginBuddy Plugin is beyond the scope of the official support, we do from time to time offer different tips and tutorials on editing the awesome PluginBuddy plugins to better fit your individual needs. All such edits are, however, beyond what is officially supported and provided in the actual plugin admin panel and officially stated features on the individual plugin pages. No official support is provided nor guaranteed in, before, during, after or related to anything resulting from any such edits/customizations.

No support is provided on any of these extra customizations. Any of the steps mentioned in any of these extra custom edits may change at any time depending on newer versions of the plugins being released. Any use or customization of anything, beyond what is provided by default inside the plugin admin menu, means you are proceeding at your own risk and that you accept 100% responsibility and liability for everything you change or modify in any manner in the plugin. Your purchase and use of any PluginBuddy plugin implies and shows that you are buying and using PluginBuddy plugin(s) the way it(they) came in their original unmodified form, with no exceptions.

*Remember:
**[http://pluginbuddy.com/purchase/backupbuddy/ Make a backup of your entire site with BackupBuddy] before making any edits!
** PluginBuddy only supports the official unedited, unmodified versions of all PluginBuddy plugins.
** Use a good text editor to make any file changes. Again, maintain backups!
** Any changes you make to files WILL MOST PROBABLY be lost when the plugin is upgraded to any newer version.
** You are 100% responsible and liable for anything resulting from any of these changes.
** No support is provided nor guaranteed on any of these extra changes in any form or shape, whatsoever, regardless of who suggested these custom edits or suggestions.
** Any extra customization info or suggestion is added voluntarily by PluginBuddy staff to help users as much as possible, even if such customization is outside the scope of any membership support.
** Whether a PluginBuddy staff or representative offered or suggested the edit/customization, another customer or anyone else, PluginBuddy does not officially support nor provide any official support on any such edits.
** We cannot guarantee providing any support on any edits or customization tips we provide.
** Absolutely no support is guaranteed in any manner on any of our free plugins, whether or not there is any customization/edit involved.

=External Plugins Compatibility=

PluginBuddy does not promise, guarantee or provide support for any compatibility with any external plugin. If any PluginBuddy Plugin works without any problems when used with any external plugin in question, that means the PluginBuddy Plugin is most probably working without any issues overall. PluginBuddy is not responsible for making PluginBuddy plugins work in any manner, whether custom, fully, fixed or other, with any external non-PluginBuddy plugins. PluginBuddy is also not responsible for providing any support whatsoever for any external plugin, whether or not such an external plugin is used along with any PluginBuddy plugin.

=Free Plugins=

Free plugins are provided as is. There is no guaranteed support that comes with them. Guaranteed support is limited only and mainly for our premium unmodified plugins.

=Bugs, Features and ETA on new updates=

With every new release of any plugin, there may be a new bug or two. You may also want to have new features added to specific plugins. All existing versions of all plugins can have bugs reported OR new features suggested. All of this is done via the [http://ithemes.com/forum official forums].

New updates are also usually released regularly and at the same time, at very different paces, depending on the current number of bugs, features, new plans and tasks at hand. Therefore it is the official policy that there is NO pre-defined ETA on any bug fix, feature imeplemention OR new update OR new plugin roll-out UNLESS otherwise specified specifically in writing somewhere by an official iThemes employee.

==Bugs, bug reports and bug fixes==

Bug reports are filed and noted as they are encountered (thanks for reporting them to us!). There is never any ETA on any bug fixes unless otherwise noted.

==Feature Requests==

Feature requests and feature suggestions are basically future suggested features that users can suggest, and/or future features PluginBuddy may consider adding to the future versions of the plugin(s) in question (again, thanks for suggesting new features!).

There is no guaranteed ETA on when such feature requests will be implemented, unless otherwise noted. All suggested features are just that: suggestions. They remain suggestions until they're confirmed as officially in the works and to be included. Even then, unless a feature is actually rolled out publicly, there is no guarantee any feature suggestion will be implemented. We do our best to try and accommodate as many feature suggestions as possible.

Also, there is no guarantee that any feature request suggested will be implemented, unless otherwise noted.

==ETA on new updates==

Just like bug fixes and new features, there is never a guaranteed date nor a guaranteed time frame on when new updates will roll out. We work every single day of the week, all the time, on our plugins and thus every day there is something new and improved happening in almost all our plugins daily. Whenever we are ready to release any new updates publicly, you'll find out by seeing the plugin update notice in your WordPress OR in your [http://ithemes.com/member/member.php Member's area].

=What does BETA mean?=

Some of PluginBuddy plugins may be in Beta status OR may have Beta features. BETA simply means that some feature or specific part of the plugin is currently still in testing mode, and can cause issues if not used properly. All BETA plugins/features are not yet 100% stable, and thus should NOT be relied on to be working properly OR working at all. Throughout the iThemes Codex, any time the word "Beta" is used in any form, it refers to Beta plugins, Beta features, Beta status and/or anything related to the Beta nature that is officially announced or mentioned as such by any iThemes staff or on any of the Plugin pages, or in this Codex.

Beta implies that any new features or plugins are very close to being released as 100% working very soon, and that there may still be some issues to fix or test more before removing the Beta status. Since no single software of any kind can be tested under every system and site configuration in the world, the Beta status enables the Beta features to be tested out by as many people on as many different websites and configurations as possible.

*Some points to keep in mind when using any BETA plugin/feature:
**1 : Make [http://pluginbuddy.com/purchase/backupbuddy/ FULL WordPress backups] before using ANY beta feature.
**2 : Beta means that the current software feature is NOT complete, and that you are NOT forced to use such a feature at all. You are advised to WAIT until the BETA status is removed.
**3 : Using any Beta feature of any kind, whether it is an entire plugin or something inside a plugin, means and shows that you are fully accepting any liability for any risks involved.
**4 : Using any Beta feature of any kind, whether it is an entire plugin or something inside a plugin, means and shows that you are fully aware that there are all different kinds of risks involved with such features.
**5 : If you are concerned about your important data or anything bad that might happen as a result of using any Beta feature, do NOT use such Beta features.
**6 : ALWAYS make full [http://pluginbuddy.com/purchase/backupbuddy/ BackupBuddy Backups of all your important data] before using any Beta software, whether that Beta software is from PluginBuddy or from any other place.
**7 : If any issues are found in Beta, they are usually added to the list of bug fixes to be released as a whole, or for the next big update, instead of being updated OR fixed individually on a case by case basis.
**8 : Beta features are recommended to test and play with on test sites/servers and configurations with any dummy data, as long as you have [http://pluginbuddy.com/purchase/backupbuddy/ full backups of all important data] still.
**9 : iThemes is not liable nor cannot be held accountable for any unwanted results resulting from the use of BETA features.
**10 : The very name and nature of BETA shows clearly, without any doubt, that there will most probably be issues and problems involved when such labeled features are used anywhere.
**11 : Support for Beta features may be very limited. We usually simply collect all reports related to Beta features and collect them all for one big update in the future.
**12 : If you lose any important data or settings anywhere, or encounter damaged data or settings anywhere, because of any Beta feature, we will not be able to help you and will simply tell you to revert to your previous [http://pluginbuddy.com/purchase/backupbuddy/ backups]. We will also tell you to always wait for BETA status to be removed before using any such features.

If you do not fully understand what Beta means, OR are not willing to fully accept and be fully liable for any risks involved because of using such Beta software, you should NOT use the Beta software in any manner. In such a case, you should simply wait until the Beta status is removed.

*[http://pluginbuddy.com/what-does-beta-mean/ Blog post announcing what BETA means]

=PluginBuddy Licenses=

==Licenses Issues due to Plugin Conflicts==

Some times, external plugins may cause issues in detaching, deleting, generating OR saving license keys. Such plugins may also cause issues when you want to manually or automatically upgrade plugins when you try to solve licensing issues.

Following is a list of currently known plugins which cause license detaching, deleting, generating OR saving issues. Please disable the following plugins, even temporarily, while you perform all the steps of manually OR automatically upgrading the PluginBuddy plugins in question, and detaching, deleting, generating and saving license keys for them. Keep such plugins disabled UNTIL all license key issues are gone OR at least while you perform these steps.

*Plugins causing PluginBuddy licensing issues
**'''W3 Total Cache or WP Super Cache :''' If you are using any caching plugin like '''W3 Total Cache''' or '''WP Super Cache''', please disable it temporarily and then carry out any required steps. You can re-enable the plugin in the end after everything works in terms of the licenses.
***Fix: Follow the above steps to fix this issue. [http://ithemes.com/forum/index.php?/topic/19436-backupbuddy-license-issue/#p92171 Steps also explained by BackupBuddy customer Laura (thanks!)]
**'''Any other CACHING or related plugin:''' Try disabling such plugins, performing the required steps, and then re-activating the Caching or related plugins in question.

*Related Links
**1 : [http://ithemes.com/forum/topic/24881-license-key-is-not-set-yet-or-invalid/page__view__findpost__p__116047 blm03 deactivated W3 Total Cache, which allowed the licenses to save correctly]
**2 : [http://ithemes.com/forum/topic/24737-backupbuddy-manage-licenses/page__view__findpost__p__115187 Karlos deactivated W3 Total Cache, and that fixed the licensing issues]
**3 : [http://ithemes.com/forum/topic/23481-license-issue-pluginbuddy-developer-to-backupbuddy-both-unlimited/page__view__findpost__p__110368 Disabling W3 Total Cache modules allowed Greg to license BackupBuddy without any issues]
**4 : [http://ithemes.com/forum/topic/23275-unable-to-get-license-to-stick/page__pid__109503#entry109503 W3 Total Cache causing licenses to be deleted after a while]
**5 : [http://ithemes.com/forum/topic/22964-cant-find-stylesheet-to-make-adjustments-to-slider/page__view__findpost__p__107933 W3 Total Cache not allowing licenses to be saved properly]
**6 : [http://ithemes.com/forum/topic/22859-bub-licenses-not-taking-effect/page__view__findpost__p__107476 W3 Total Cache not allowing licenses to be saved - easy solution!]
**7 : [http://ithemes.com/forum/index.php?/topic/19079-wont-let-me-set-a-license-key/#p91663 W3 Total Cache plugin conflict and solution]
**8 : [http://ithemes.com/forum/index.php?/topic/19436-backupbuddy-license-issue/#p92171 W3 Total Cache plugin conflict and solution]
**9 : [http://ithemes.com/forum/index.php?/topic/20228-key-does-not-work/#p95697 W3 Total Cache plugin conflict and solution]
**10 : [http://ithemes.com/forum/index.php?/topic/19041-license-problem-causes-loss-of-all-bb-settings-way-to-get-them-back/ WP Super Cache conflict and solution]

==Licensing Issues==

There are some reports that some users have issues with their license insides the Licenses area of different PluginBuddy plugins, including BackupBuddy.

Remember: All your PluginBuddy plugins, including BackupBuddy, will CONTINUE WORKING PERFECTLY even with these licensing issues. You can keep using the plugins exactly how you want them even during these licensing issues. Your plugins are NOT affected by this licensing situation in any manner.

Your membership is also completely fine and you have NOT lost any license(s). The issue is happening to some customers who simply need to upgrade manually to the latest version of their plugin, if the automatic upgrade does not work.

*Plugins with the update versions which remove this issue completely
**ALL PluginBuddy Products

*You can upgrade via one of the following:
**Automatically upgrade to the latest version
**Manually update by downloading the latest zip version of your PluginBuddy plugin from your Member's panel and then
***Overwrite your existing plugin directory via FTP with the new files.
***De-activate the existing plugin, delete it via your '''WordPress --> Plugins''' area and then upload the newly downloaded zip file. Then re-activate the plugin.
**That will remove the issue completely.
*DETACH the key and then RE-ATTACH the license key for the specific site in question IF licensing still shows issues AFTER manually upgrading to the latest version of the plugin in question (check your Member's area for the latest version download)
*Also make sure to DETACH the key, DELETE that same AND any other keys related to that specific site from the entire licenses area, and then GENERATE a new key for that site IF detaching and re-attaching the license key does not work AFTER manually upgrading (for example, manually upgrading to the latest BackupBuddy version - all plugins have their own latest version numbers - check your Member's area for the latest version download)

[http://ithemes.com/forum/index.php?/topic/6691-read-this-first-pluginbuddy-licensing-issues/page-2/#p85977 First reports]

PluginBuddy

2012-03-06T20:41:51Z

Bes: Added another W3 Total Cache issue confirmation thread http://ithemes.com/forum/topic/24881-license-key-is-not-set-yet-or-invalid/page__view__findpost__p__116047 /* Plugin Conflicts */

Welcome to the PluginBuddy Knowledge Base - Tutorials, Technical Information, Debugging Information, and more.

=Premium Plugins=
* [[Ajax-Edit-Comments]]
* [[BackupBuddy]]
* [[DisplayBuddy]]
** [[Accordion]]
** [[Billboard]]
** [[Carousel]]
** [[CopiousComments]]
** [[FeaturedPosts]]
** [[Rotating Images]]
** [[RotatingText]]
** [[Slides]]
** [[Slideshow]]
** [[Tipsy]]
** [[VideoShowcase]]
* [[EmailBuddy]]
* [[Frolic]]
* [[LoopBuddy]]
* [[Mobile]]
* [[TailoredLogin]]
* [[ThumbsUp]]
* [[VidEmbed]]

=Free Plugins (active)=
* [[Featured Text]]
* [[PB-Tweet]]
* [[ServerBuddy]]
* [[Tabber Widget]]
* [[ThemeMan]]
* [[S3 URLS]]
* [[YOURLS]]
* [[ContactBuddy]]

=Free Plugins (inactive)=
* [[WP Easy Uploader]]
* [[WP Developer Assistant]]
* [[Easy Theme and Plugin Updater]]
* [[Current Date & Time Widget]]

''[[:Category:PluginBuddy|View all PluginBuddy Wiki Pages]]''

=Misc. Documentation=
==Frequently Asked (Plugin) Questions==
*[[General Plugins FAQ]]

==License Manager Tutorial and Information==
*[[License Manager]]
==PHP Development & Advanced==
*[[.htaccess]]
*[[PHP]]
*[[Arrays]]

[[Category:PluginBuddy]]

=Translations (localization / internationalization)=

Many PluginBuddy plugins come with translation capability. That means such PluginBuddy plugins can be translated (aka localized) to other languages.

===How Translations Work===

PluginBuddy provides the capability to have a translation in such plugins. Anyone wanting to enhance PluginBuddy with specific language translations can do so voluntarily via Translation Files. Translation Files are simply language files created fully and solely by the volunteer community which use the already built in translation-capable features in many of the PluginBuddy plugins to allow such plugins to show text or outputs in different languages. Making PluginBuddy translation-capable is done by PluginBuddy. Creating, updating and sending in any language specific translation files to PluginBuddy is done by the volunteer community.

Anyone can create translation files, package them into the proper format and give PluginBuddy the final translated files that we will try to include in the next update for the plugin in question. We call such awesome people, who create or update the translation files and send us the full translation package files, '''Awesome Translator Volunteers''', and we are really thankful that they take the time to do such an awesome thing.

If you want to help us, you can translate any existing PluginBuddy plugin which supports internationalization (another way of saying localization or translation-capable) and then, once you're fully done, simply let us know in the forums the link to the final language files that we can directly save and simply try to include in any future updates for the plugin(s) in question.

===Tips on how to localize any PluginBuddy Plugin to any non-English language===

The following 9 tips can help you figure out how to approach translations, how to create translations, and how to send us the final translated file for any translation-capable PluginBuddy plugin:

*1 : Many of the PluginBuddy plugins are internationalized, meaning they have the capability to be translated, via actual external translation files, by any non-iThemes-staff Awesome Translator Volunteer who wishes such plugins to be translated to their language.
*2 : If a PluginBuddy plugin is currently not internationalized or you're not sure if it is, you can ask us in the [http://ithemes.com/forum Support Forums] and we'll let you know, or we'll have it included as a future translation feature request. After the translation capability is added to such a plugin, you can submit the actual translation file. Please remember though: we cannot help with creating, understanding or making any language translation files. Our Awesome Translator Volunteers do that voluntarily (you can too! keep on reading) and fully on their own.
*3 : There are MANY resources which teach you how to create and work with WordPress language files. Following are the official 3 directly by the WordPress community:
**1 : [http://codex.wordpress.org/WordPress_in_Your_Language WordPress in Your Language]
**2 : [http://codex.wordpress.org/Translating_WordPress Translating WordPress]
**3 : [http://codex.wordpress.org/I18n_for_WordPress_Developers What WordPress Localization in Plugins is mainly about]
*4 : Translations are sent in from volunteers from all over the world. As a courtesy, we sometimes package the actual language translation files (provided directly by the Awesome Translator Volunteers) in with the final product. If some translation is not included in the actual plugin even when the plugin has the capability to be translated, you can submit the final translation to us for consideration in the next update by posting on our forums OR you can include the translation in your own live or local WordPress install directly for your own use. More info on how to include your own language specific file for your own WordPress sites is in the resources listed in #3 above.
*5 : A translation included in with the final product does not guarantee the accuracy or quality of the translation. These files are from the Awesome Translator Volunteers, and correction of these files is also done by those Awesome Translator Volunteers.
*6 : If a translation is very inaccurate or incomplete, we can put out a request for a new translation from the volunteer community, or remove the translation from the packaged and final product. You can also let us know of any inaccuracies in any existing translation files by the Awesome Volunteers by providing us with the corrected final files. Please remember: we only accept final and full translation files that you yourself have already created or packaged properly. If you let us know only of the actual inaccuracies without providing the final correct files, we cannot make such changes ourselves to the translation files.
*7 : Unfortunately, PluginBuddy cannot work on, help with, create, nor make any updates to any specific translation files you may have, or may be working on, or want to work on. Our Awesome Volunteers do that and simply give us the final files for inclusion or consideration.
*8 : If you have corrections for any existing translation in form of final proper format translation files for an existing language, OR want to provide the final and proper translation files for a new language, please post a new thread in the appropriate product category in the [http://ithemes.com/forum/ PluginBuddy Support Forums] with the final translations files. If you have any support questions on how to create or make language specific translation files, or how translation files work, you can do so on the [http://wordpress.org/support/ WordPress forums], as such support questions are outside the scope of what PluginBuddy support guarantees with your iThemes membership.
*9 : Any final translation file provided by you (or any other Awesome Volunteer) on the support forums will then be saved and filed as a future enhancement request for the future updates of the plugin(s) in question. In your support forum thread, where you share the final complete translation files you inclusion, you can upload your files directly to the forums OR upload them somewhere and link to them in your support forum thread. We will then download and save such files. Remember please: we cannot guarantee looking inside such files or verifying that they are correct in any manner (because of so many languages in the world and so many possible language files everywhere).

Thank you SO MUCH for being interested in providing translation files for our PluginBuddy plugins. We hope you will become one of our Awesome Translator Volunteers, in addition to being our AWESOME CUSTOMER, and create/update any language-specific translation file package and provide it to us so that we can consider including it in future updates.

===Resources for understanding, creating, updating and submitting final translation files===
*Here are the 3 official resources again which you can use to create, update, start work on and finish translation on any of the translation-capable PluginBuddy plugins:
**1 : [http://codex.wordpress.org/WordPress_in_Your_Language WordPress in Your Language]
**2 : [http://codex.wordpress.org/Translating_WordPress Translating WordPress]
**3 : [http://codex.wordpress.org/I18n_for_WordPress_Developers What WordPress Localization in Plugins is mainly about]

=Extra Customizations=
While any extra customization of any PluginBuddy Plugin is beyond the scope of the official support, we do from time to time offer different tips and tutorials on editing the awesome PluginBuddy plugins to better fit your individual needs. All such edits are, however, beyond what is officially supported and provided in the actual plugin admin panel and officially stated features on the individual plugin pages. No official support is provided nor guaranteed in, before, during, after or related to anything resulting from any such edits/customizations.

No support is provided on any of these extra customizations. Any of the steps mentioned in any of these extra custom edits may change at any time depending on newer versions of the plugins being released. Any use or customization of anything, beyond what is provided by default inside the plugin admin menu, means you are proceeding at your own risk and that you accept 100% responsibility and liability for everything you change or modify in any manner in the plugin. Your purchase and use of any PluginBuddy plugin implies and shows that you are buying and using PluginBuddy plugin(s) the way it(they) came in their original unmodified form, with no exceptions.

*Remember:
**[http://pluginbuddy.com/purchase/backupbuddy/ Make a backup of your entire site with BackupBuddy] before making any edits!
** PluginBuddy only supports the official unedited, unmodified versions of all PluginBuddy plugins.
** Use a good text editor to make any file changes. Again, maintain backups!
** Any changes you make to files WILL MOST PROBABLY be lost when the plugin is upgraded to any newer version.
** You are 100% responsible and liable for anything resulting from any of these changes.
** No support is provided nor guaranteed on any of these extra changes in any form or shape, whatsoever, regardless of who suggested these custom edits or suggestions.
** Any extra customization info or suggestion is added voluntarily by PluginBuddy staff to help users as much as possible, even if such customization is outside the scope of any membership support.
** Whether a PluginBuddy staff or representative offered or suggested the edit/customization, another customer or anyone else, PluginBuddy does not officially support nor provide any official support on any such edits.
** We cannot guarantee providing any support on any edits or customization tips we provide.
** Absolutely no support is guaranteed in any manner on any of our free plugins, whether or not there is any customization/edit involved.

=External Plugins Compatibility=

PluginBuddy does not promise, guarantee or provide support for any compatibility with any external plugin. If any PluginBuddy Plugin works without any problems when used with any external plugin in question, that means the PluginBuddy Plugin is most probably working without any issues overall. PluginBuddy is not responsible for making PluginBuddy plugins work in any manner, whether custom, fully, fixed or other, with any external non-PluginBuddy plugins. PluginBuddy is also not responsible for providing any support whatsoever for any external plugin, whether or not such an external plugin is used along with any PluginBuddy plugin.

=Free Plugins=

Free plugins are provided as is. There is no guaranteed support that comes with them. Guaranteed support is limited only and mainly for our premium unmodified plugins.

=Bugs, Features and ETA on new updates=

With every new release of any plugin, there may be a new bug or two. You may also want to have new features added to specific plugins. All existing versions of all plugins can have bugs reported OR new features suggested. All of this is done via the [http://ithemes.com/forum official forums].

New updates are also usually released regularly and at the same time, at very different paces, depending on the current number of bugs, features, new plans and tasks at hand. Therefore it is the official policy that there is NO pre-defined ETA on any bug fix, feature imeplemention OR new update OR new plugin roll-out UNLESS otherwise specified specifically in writing somewhere by an official iThemes employee.

==Bugs, bug reports and bug fixes==

Bug reports are filed and noted as they are encountered (thanks for reporting them to us!). There is never any ETA on any bug fixes unless otherwise noted.

==Feature Requests==

Feature requests and feature suggestions are basically future suggested features that users can suggest, and/or future features PluginBuddy may consider adding to the future versions of the plugin(s) in question (again, thanks for suggesting new features!).

There is no guaranteed ETA on when such feature requests will be implemented, unless otherwise noted. All suggested features are just that: suggestions. They remain suggestions until they're confirmed as officially in the works and to be included. Even then, unless a feature is actually rolled out publicly, there is no guarantee any feature suggestion will be implemented. We do our best to try and accommodate as many feature suggestions as possible.

Also, there is no guarantee that any feature request suggested will be implemented, unless otherwise noted.

==ETA on new updates==

Just like bug fixes and new features, there is never a guaranteed date nor a guaranteed time frame on when new updates will roll out. We work every single day of the week, all the time, on our plugins and thus every day there is something new and improved happening in almost all our plugins daily. Whenever we are ready to release any new updates publicly, you'll find out by seeing the plugin update notice in your WordPress OR in your [http://ithemes.com/member/member.php Member's area].

=What does BETA mean?=

Some of PluginBuddy plugins may be in Beta status OR may have Beta features. BETA simply means that some feature or specific part of the plugin is currently still in testing mode, and can cause issues if not used properly. All BETA plugins/features are not yet 100% stable, and thus should NOT be relied on to be working properly OR working at all. Throughout the iThemes Codex, any time the word "Beta" is used in any form, it refers to Beta plugins, Beta features, Beta status and/or anything related to the Beta nature that is officially announced or mentioned as such by any iThemes staff or on any of the Plugin pages, or in this Codex.

Beta implies that any new features or plugins are very close to being released as 100% working very soon, and that there may still be some issues to fix or test more before removing the Beta status. Since no single software of any kind can be tested under every system and site configuration in the world, the Beta status enables the Beta features to be tested out by as many people on as many different websites and configurations as possible.

*Some points to keep in mind when using any BETA plugin/feature:
**1 : Make [http://pluginbuddy.com/purchase/backupbuddy/ FULL WordPress backups] before using ANY beta feature.
**2 : Beta means that the current software feature is NOT complete, and that you are NOT forced to use such a feature at all. You are advised to WAIT until the BETA status is removed.
**3 : Using any Beta feature of any kind, whether it is an entire plugin or something inside a plugin, means and shows that you are fully accepting any liability for any risks involved.
**4 : Using any Beta feature of any kind, whether it is an entire plugin or something inside a plugin, means and shows that you are fully aware that there are all different kinds of risks involved with such features.
**5 : If you are concerned about your important data or anything bad that might happen as a result of using any Beta feature, do NOT use such Beta features.
**6 : ALWAYS make full [http://pluginbuddy.com/purchase/backupbuddy/ BackupBuddy Backups of all your important data] before using any Beta software, whether that Beta software is from PluginBuddy or from any other place.
**7 : If any issues are found in Beta, they are usually added to the list of bug fixes to be released as a whole, or for the next big update, instead of being updated OR fixed individually on a case by case basis.
**8 : Beta features are recommended to test and play with on test sites/servers and configurations with any dummy data, as long as you have [http://pluginbuddy.com/purchase/backupbuddy/ full backups of all important data] still.
**9 : iThemes is not liable nor cannot be held accountable for any unwanted results resulting from the use of BETA features.
**10 : The very name and nature of BETA shows clearly, without any doubt, that there will most probably be issues and problems involved when such labeled features are used anywhere.
**11 : Support for Beta features may be very limited. We usually simply collect all reports related to Beta features and collect them all for one big update in the future.
**12 : If you lose any important data or settings anywhere, or encounter damaged data or settings anywhere, because of any Beta feature, we will not be able to help you and will simply tell you to revert to your previous [http://pluginbuddy.com/purchase/backupbuddy/ backups]. We will also tell you to always wait for BETA status to be removed before using any such features.

If you do not fully understand what Beta means, OR are not willing to fully accept and be fully liable for any risks involved because of using such Beta software, you should NOT use the Beta software in any manner. In such a case, you should simply wait until the Beta status is removed.

*[http://pluginbuddy.com/what-does-beta-mean/ Blog post announcing what BETA means]

=PluginBuddy Licenses=

==Plugin Conflicts==

Some times, external plugins may cause issues in detaching, deleting, generating OR saving license keys. Such plugins may also cause issues when you want to manually or automatically upgrade plugins when you try to solve licensing issues.

Following is a list of currently known plugins which cause license detaching, deleting, generating OR saving issues. Please disable the following plugins, even temporarily, while you perform all the steps of manually OR automatically upgrading the PluginBuddy plugins in question, and detaching, deleting, generating and saving license keys for them. Keep such plugins disabled UNTIL all license key issues are gone OR at least while you perform these steps.

*Plugins causing PluginBuddy licensing issues
**'''W3 Total Cache or WP Super Cache :''' If you are using any caching plugin like '''W3 Total Cache''' or '''WP Super Cache''', please disable it temporarily and then carry out any required steps. You can re-enable the plugin in the end after everything works in terms of the licenses.
***Fix: Follow the above steps to fix this issue. [http://ithemes.com/forum/index.php?/topic/19436-backupbuddy-license-issue/#p92171 Steps also explained by BackupBuddy customer Laura (thanks!)]
**'''Any other CACHING or related plugin:''' Try disabling such plugins, performing the required steps, and then re-activating the Caching or related plugins in question.

*Related Links
**1 : [http://ithemes.com/forum/topic/24881-license-key-is-not-set-yet-or-invalid/page__view__findpost__p__116047 blm03 deactivated W3 Total Cache, which allowed the licenses to save correctly]
**2 : [http://ithemes.com/forum/topic/24737-backupbuddy-manage-licenses/page__view__findpost__p__115187 Karlos deactivated W3 Total Cache, and that fixed the licensing issues]
**3 : [http://ithemes.com/forum/topic/23481-license-issue-pluginbuddy-developer-to-backupbuddy-both-unlimited/page__view__findpost__p__110368 Disabling W3 Total Cache modules allowed Greg to license BackupBuddy without any issues]
**4 : [http://ithemes.com/forum/topic/23275-unable-to-get-license-to-stick/page__pid__109503#entry109503 W3 Total Cache causing licenses to be deleted after a while]
**5 : [http://ithemes.com/forum/topic/22964-cant-find-stylesheet-to-make-adjustments-to-slider/page__view__findpost__p__107933 W3 Total Cache not allowing licenses to be saved properly]
**6 : [http://ithemes.com/forum/topic/22859-bub-licenses-not-taking-effect/page__view__findpost__p__107476 W3 Total Cache not allowing licenses to be saved - easy solution!]
**7 : [http://ithemes.com/forum/index.php?/topic/19079-wont-let-me-set-a-license-key/#p91663 W3 Total Cache plugin conflict and solution]
**8 : [http://ithemes.com/forum/index.php?/topic/19436-backupbuddy-license-issue/#p92171 W3 Total Cache plugin conflict and solution]
**9 : [http://ithemes.com/forum/index.php?/topic/20228-key-does-not-work/#p95697 W3 Total Cache plugin conflict and solution]
**10 : [http://ithemes.com/forum/index.php?/topic/19041-license-problem-causes-loss-of-all-bb-settings-way-to-get-them-back/ WP Super Cache conflict and solution]

==Licensing Issues==

There are some reports that some users have issues with their license insides the Licenses area of different PluginBuddy plugins, including BackupBuddy.

Remember: All your PluginBuddy plugins, including BackupBuddy, will CONTINUE WORKING PERFECTLY even with these licensing issues. You can keep using the plugins exactly how you want them even during these licensing issues. Your plugins are NOT affected by this licensing situation in any manner.

Your membership is also completely fine and you have NOT lost any license(s). The issue is happening to some customers who simply need to upgrade manually to the latest version of their plugin, if the automatic upgrade does not work.

*Plugins with the update versions which remove this issue completely
**ALL PluginBuddy Products

*You can upgrade via one of the following:
**Automatically upgrade to the latest version
**Manually update by downloading the latest zip version of your PluginBuddy plugin from your Member's panel and then
***Overwrite your existing plugin directory via FTP with the new files.
***De-activate the existing plugin, delete it via your '''WordPress --> Plugins''' area and then upload the newly downloaded zip file. Then re-activate the plugin.
**That will remove the issue completely.
*DETACH the key and then RE-ATTACH the license key for the specific site in question IF licensing still shows issues AFTER manually upgrading to the latest version of the plugin in question (check your Member's area for the latest version download)
*Also make sure to DETACH the key, DELETE that same AND any other keys related to that specific site from the entire licenses area, and then GENERATE a new key for that site IF detaching and re-attaching the license key does not work AFTER manually upgrading (for example, manually upgrading to the latest BackupBuddy version - all plugins have their own latest version numbers - check your Member's area for the latest version download)

[http://ithemes.com/forum/index.php?/topic/6691-read-this-first-pluginbuddy-licensing-issues/page-2/#p85977 First reports]

BackupBuddy: Frequent Support Issues

2012-03-02T17:44:54Z

Bes: Clarified Dropbox limitations a bit more, specially the server memory transfer relation and 300mb file size limits /* Dropbox Backups Not Arriving */

=Backing Up=

==HTTP Loopback Connections Disabled==
* Also known as '''Endless Ping'''.
* This usually happens before the second Scheduled Cron in your backup is run. You can see the number of times "Scheduled Cron" is mentioned in the Advanced Logs shown on the backup page to see if this is the case.
* If your Server Information page reports that HTTP Loopback Connections are disabled or the following occurs (see below), you need to either enable HTTP Loopback Connections or enter the WordPress Alternate Cron setting in your wp-config.php file. This is caused if your host is blocking loopback connections within their firewall. You will need to request that your host change this (this is very standard to have this available), enable the alternate cron method in your wp-config.php (as Solution below - often the '''only''' solution for those in a shared environment), or move to a new host.
** If your backup progress (as detailed in the Advanced Details area) consistently '''never''' progresses beyond this point except for the continuous "pings":

<pre>
Backing up with BackupBuddy v2.1.8...
20:35:15: Setting greedy script limits.
20:35:15: Set memory limit to 256M. Previous value < 256M.
20:35:15: Finished greedy script limits.
20:35:15: Full backup mode.
20:35:15: Performing pre-backup procedures.
20:35:15: Backup serial: pyisomo736
20:35:15: Creating import data file.
20:35:15: Finished creating import data file.
20:35:15: Finished pre-backup procedures.
20:35:15: Scheduling Cron for pyisomo736.
1307910918|ping
1307910922|ping
1307910926|ping
</pre>
* Solution:
** Add define('ALTERNATE_WP_CRON', true); to your wp-config.php
*** Open your wp-config.php in a text editor. This file is located in the root of your site.
*** Add the line somewhere between the first ( <?php ) and last line of the file (but before the line that says /* That's all, stop editing! Happy blogging. */)
*** <pre>define('ALTERNATE_WP_CRON', true);</pre>
** Deactivate all other plugins and see if it works then, if so then make sure you don't have a plugin that may apply a maintenance mode
*** This is because maintenance mode plugins rarely, if ever, take into account WordPress scheduling crons
* See also
**[http://ithemes.com/codex/page/BackupBuddy:_Frequent_Support_Issues#Endless_Ping_on_second_Scheduling_Cron Endless Ping on Second Scheduling Cron in BackupBuddy Codex]
**[http://codex.wordpress.org/Editing_wp-config.php#Alternative_Cron WordPress Codex / Alternative Cron on WordPress.org]

* Related threads with same/similar solutions:
** http://ithemes.com/forum/index.php?/topic/17385-backupbuddy-doesnt-backup-at-all-infinite-ping/
** http://ithemes.com/forum/backupbuddy/endless-pinging-v2-2-14

=== On Linux Systems ===
On Linux systems, be sure you have your /etc/hosts file correctly setup as problems here can cause loopback not to work.

==Compatibility Mode==
* If your server does not support command line Zip then BackupBuddy will fall back into a compatibility mode to help aid you in creating a backup. This mode is significantly slower and less reliable. It is not intended for persistent use and is provided to aid you in backing up in poor hosting environments, for instance to move to another host.
* Directory exclusion is not available in this mode. Even existing backups will be backed up, resulting in rapidly growing backup file sizes.
* If you are running on a Windows server you will need to install the [http://pluginbuddy.com/wp-content/uploads/2010/05/backupbuddy_windows_unzip.zip Windows zip.exe executable] (we do not provide support for setting this up, though the readme.txt in the file does help).
* Solutions:
** If you are running CentOS on a VPS or similar type of server then running the command <pre>yum install zip</pre> as root will install the zip package and any dependencies. This may also apply to other environments using rpm packages and the yum package manager front-end. The yum manager can also be used to query installed packages and update packages, etc. If you have any issues with this then please consult your host support for additional assistance.
** If you are operating a Media Temple DV server then please make sure you have the Developer Tools installed as this contains the package necessary to provide zip capability.
** If your server is configured to disable access to the PHP exec() function and if you have access to configure your server then remove any blocking of the PHP exec() function in php.ini and configure permissions to allow running the Linux command line function `zip`.
** If your server is operating in safe_mode then either turn safe_mode off (if you can) or make sure that the safe_mode_exec_dir configuration parameter includes the directory which contains the `zip` command (please consult your host support for this information)
** Ask your host to enable access to the Linux command line Zip command via PHP's exec() function.
*** Example message to send to your host:
<pre>
Dear Sir/Madam,

I am attempting to use the highly popular WordPress backup software, BackupBuddy by PluginBuddy.com.
BackupBuddy requires the ability to use the Linux command line Zip command via PHP's exec() function.
BackupBuddy is reporting that it is unable to access this functionality on my server hosting environment.
Please enable this functionality for me so that I may use this backup solution in combination with your hosting.
These are commonly available features of many popular hosting providers such as HostGator.com so it is
not unreasonable to request it nor is it a security risk IF it is properly configured.

Please verify access to the following features:
1) PHP's exec() function.
2) Permission to run Linux's `zip` command.
3) The directory containing the `zip` command is included in the PATH environment variable
available to the process executing the command passed to the exec() function

Thank you for your time and consideration.
</pre>
** Also possible that even though that zip via exec() is enable it still may not work if host does not have zip's path location currently as a part of PATH (or the path is not one of the "well known" locations that more recent versions of BackupBuddy with search). The below code is an example of how to add the directory of the zip executable to PATH after you ask your host where it is being kept and whether this is the correct way to do it on their servers or if not what is the preferred way (please note the colon that precedes the path being added):
*** <pre>putenv( "PATH=" . getenv( 'PATH' ) . ":directory zip exe is" );</pre>
*** The line has to be added anywhere in the wp-config.php file after the first line ( <?php ) but at least before the line that says /* That's all, stop editing! Happy Blogging */
** If all of the above are either impossible or unsuccessful and you absolutely must have the native zip command capability then you only option is to move your site to an alternative server or host that provides this capability.

==Warning: exec() has been disabled for security reasons in /www/wp-content/plugins/backupbuddy/lib/zip/zip.php on line ###==
* exec() is disabled somewhere in PHP configuration. Ask the host to correct this or use cPanel to edit PHP settings to enable it if possible. See 'Fallback to Compatibility Mode' above.

==Warning: mysql_query() [function.mysql-query]: Unable to save result set in /www/wp-content/plugins/backupbuddy/backupbuddy.php on line 1673==
* See [http://ithemes.com/codex/page/BackupBuddy:_Error_Codes#9001 BackupBuddy Error Code 9001]

==Godaddy Related==
* The bottom tier of Godaddy hosting services are known for not being able to complete backups within the maximum PHP runtime configured on their servers (usually 30 seconds), causing backups to fail.
* Solutions:
** Choose another quality hosting provider such as Hostgator.com (recommended)
** Upgrade to a higher tier of Godaddy hosting (not recommended as even better Godaddy servers are poor performers)

==.htaccess 404 / Addhandler Warning==
* Some hosts use a line at the top of the .htaccess file in the root of the site to configure some server settings such as enabling PHP support for that site. When used on a host that does not need this it can break PHP or other functionality. When migrating to a new site this can break the migration process. This often causes URLs to give 404 Not Found errors after migrating/restoring.
* Solution:
** Remove the Addhandler line from the .htaccess file before backup or open the backup ZIP archive and remove the line within the file within the ZIP.

==Backup marked as bad==
* Backups are verified by verifying the following criteria:
** The ZIP file is not corrupt and is openable.
** The database (.sql) file exists.
** The wp-config.php file.
** The backupbuddy_dat.php file.
* Potential causes:
** The backup timed out and did not complete within the PHP maximum runtime (usually 30 seconds)
*** Solution: Reduce the backup size by deleting files or excluding one or more directories. You may use the `Server Information` page's Directory Size browser to find large directories/files.
** Your hosting account does not have enough free space available.
** You may have the backupbuddy_temp directory excluded.

==Database backup succeeds, full fails==
* This is almost exclusively due any single step of the backup process not completing within the maximum PHP runtime (usually 30 seconds).
* If you are in compatibility mode then backups are significantly slower and less likely to complete in time.
* Solution:
** Ask your host to enable command line ZIP via exec() if you are in compatibility mode.
** Reduce the size of your backups by deleting files or excluding large directories.

==Directories not being excluded==
* Directories are not excluded if BackupBuddy is being forced to fall into compatibility mode. This is expected behaviour. This happens if command line Zip is unavailable via the PHP exec() function.
* Solutions:
** Contact your host and ask them if they can enable command line ZIP via exec() if using Linux. For Windows servers a zip.exe file is available by downloading it from the `Getting Started` page of BackupBuddy when running on a Windows host.
** Continue using compatibility mode. If you do this you will not be able to exclude directories, including the backups directory. Because of this even backups will be backed up. We recommend not storing any backups locally in this case as your backup file sizes will increase exponentially.

==Tempory files in directories/root==
* BackupBuddy creates several temporary files within the directory `/wp-content/uploads/backupbuddy_temp/` while generating a backup. Some of these may remain temporarily after backups complete though most are cleaned up immeditately. BackupBuddy will automatically clean up any remaining temporary files within 12 hours. This is an automated process.
* While in compatibility mode large sites can create temporary .gz files in the site root. Sometimes these may be left behind and require manual cleanup at this time. This is uncommon and is a result of not having command line ZIP via exec() available. Ask your host to enable this.
* Solution:
** Wait ~12 hours or delete the file(s) manually.

==Backups Time Out / Marked as Bad==
* Backup file size is too large so it takes too many resources or too much time to finish so the process is killed.
* The maximum PHP runtime is typically 30 seconds so backups must finish within this time period.
* Try reducing backup size, excluding directories, disabling compression to speed up zip file generation, or getting host to enable native zip compression if not already enabled.
* Backup completed but backup ZIP is incomplete / bad: exec() shares the maximum allowed memory usage with PHP. If this memory limit is met the exec() / proc() will be killed and return to PHP. The symptoms of this are a bad / incomplete ZIP file despite the backup fully completing successfully. Try increasing `memory_limit` to a larger size.
** <table border="1"><tr><td> </td><td>exec()</td><td>proc()</td></tr><tr><td>Maximum PHP Runtime Timeout</td><td>Zip file size stops increasing.</td><td>Zip file size stops increasing</td></tr><tr><td>Memory Limit Hit</td><td>Zip creation completed but ZIP file<br>incomplete & marked as bad</td><td>Zip file size stops increasing.</td></tr></table>

==Zip File Creation Dies at 2GB==
* The limit of some file systems on a 32bit server can create a file is 2GB.
** Ask host to user a better file system that allows for the creation and handling of files bigger than 2GB.
*** Large File Systems (LFS) don't technically have limits on how big they can support, they are designed to expand.

==Zip File Creation Dies at ~4GB==
* On a 32bit server the limit for Zip Archive is about 4GB.
** Ask host to upgrade to 64bit.
** Host may be able to use better configurations or software for the server to up this while staying on 32bit though I am unsure on the details

==Remote Transfers Fail==
* Login credentials are wrong. Test them to be sure that they have not changed. This is exceedingly common.
* The path entered is incorrect or the directory has not been created. BackupBuddy requires the path/bucket to already exist in some cases.
* Some hosts block outgoing connections. Try another remote destination if possible. Most remote destinations transfer over the HTTP port 80.
** Amazon S3: port 80
** Dropbox: port 80
** Rackspace Cloud: port 80
** FTP: port 21 (unless overridden)
** Email: port 25 (if using external mail server)

==Scheduled Events Fail to Trigger==
* The scheduled date is wrong and has not passed.
* Not enough visitors are visiting to trigger the schedule. Someone must visit any page on the WordPress site on or after the scheduled time for the event to occur. If no one visits during the time-frame then the event may be missed or occur at an unscheduled time.
** Can force a cron job to run in Cpanel by adding this line of code to a cron job if really need to: <pre> wget -q -O - http://DOMAIN/wp-cron.php 2&>1 /dev/null </pre>
*** Source: http://www.siteground.com/tutorials/cpanel/cron_jobs.htm
* The backup is failing. Test manual backups.

==Files not being sent remotely==
* Files may fail remote sending for two possible reasons:
** Files are too large to be transferred during the alotted PHP maximum runtime (usually 30 seconds). This is defined by your host.
** Your host's firewall is blocking outgoing HTTP connections / transfers.
** The backup itself isn't completing - verify that they work manually.
* Solutions:
** Reduce backup file size by deleting files or excluding directories.
** Contact your host to increase PHP's maximum allowed runtime.
** Contact your host to unblock their firewall to allow outgoing HTTP connections.

==Error 3382==
Check out [http://ithemes.com/codex/page/BackupBuddy:_Error_Codes#3382 Error 3382 Details]

==Backup failure running function `` in email==
* Usually due to sending remote backups/databases failed due to permissions/path if ftp.
** If sending the files by email, then files are probably too large for email(typically up to 10mb by email allowed by most places)

==Endless Ping on second Scheduling Cron==
* Database may be too large, lot of times this would be the wp_posts table.
** See if can lower size of database. The database size may be too big for your site/host/server to handle properly.
** Use Server Info inside BackupBuddy ( '''BackupBuddy --> Server Info.''' ) to check where the most disk space is being used.
** Increase available runtime. Your server may be timing out too quickly or having other issues related to not being allowed enough time to run scripts or specific commands.
** What revision retention policy do you operate on the posts? It may be that you have a lot of revisions stored in the database that you could safely remove. The WordPress Codex gives some information on controlling revisions (http://codex.wordpress.org/Editing_wp-config.php#Post_Revisions) but I don't think this acts retrospectively so you might need to find a method to prune any revisions you currently have.
** Many plugins tend to leave a lot of data behind even after they have been de-activated and deleted in WordPress. This can result in very large BackupBuddy backups.
***Example: A famous example of this is Statpress, which has been publicly known to leave massive amounts of data behind in the WordPress database tables even after the plugin was deactivated and deleted.
***Solutions:
**** Use Server Info inside BackupBuddy ( '''BackupBuddy --> Server Info.''' ) to check where the most disk space is being used in different WordPress database tables.
**** Another way to see if such plugins may be affecting and causing your Backup to fail is to look through the database and see where the most db space is being used. If any table with a lot of data exists and is related to a plugin you no longer use, you can drop or empty that table with something like phpMyAdmin.
****Also, if you have a "maintenance mode" plugin active, this can cause endless pinging as well. Deactivating this plugin solved the problem for some users.
***Make full Database backup with BackupBuddy before making any Database changes. :D
*Related links:
**[http://ithemes.com/forum/index.php?/topic/18066-backup-not-working-keepings-pinging/#p85085 Database size causing endless pings on second scheduling cron]

==Fatal Error: Call to undefined function home_url()==
* Full error will be Fatal Error: Call to undefined function home_url() in /wp-content/plugins/backupbuddy/classes/backup.php on line x
** BackupBuddy requires at least WordPress version 3.0, make sure you don't have an older version of WordPress.

==Parse Error, unexpected T_VARIABLE in .../backupbuddy.php on line xxx==
* Usually will come up during activation of BackupBuddy
** Make sure you are using PHP5 and not PHP4.
** If you are installing by downloading BackupBuddy, unzipping, and then using FTP the directory in the site plugins directory sometimes the configuration of the FTP transfer mode can cause issues. You can try deleting the existing plugin files with the plugin admin and then install through WordPress admin by going through Plugins -> Add New -> Upload -> and use the backupbuddy.zip file. Be sure to do this with a copy of backupbuddy.zip that has not been unzipped.

==Backed up files link shows 404 error==

* This error is shown when you click on the generated backed up files. There is no error shown on the Backup page or in the logs, yet clicking the backup links show a 404 error or result in you not being able to download them because the files don't exist. This could be caused by several things. Mainly, this has been known to be caused by the following:
** There is an Archive limit set on the BackupBuddy --> Settings page. If this is being exceeded, the extra archives will be deleted. Try setting this to something higher.
** Set the total size limit ( max file size ) to a higher setting.
** See if any other plugin may be causing the issue. Disable other plugins and try starting the backup process again.
** Make sure you have the necessary permissions to the downloads folder where the file is being saved.
** Make sure the Advanced Log file in BackupBuddy is not showing any errors. If it is, post on the [http://ithemes.com/forum/backupbuddy/ forums] so that the error can be looked at.

* Other threads with solutions listed above:
** http://ithemes.com/forum/index.php?/topic/17196-full-backup-completes-but-does-not-go-to-backup-archives/
** http://ithemes.com/forum/index.php?/topic/17624-backupbuddy-full-backup-is-deleting-backup-file-after-creating-it/
** http://ithemes.com/forum/index.php?/topic/15013-download-error-message/

==Change backups folder/file permissions or verify it is writable==
BackupBuddy needs the backups folder in your '''wp-content/uploads''' directory on your site to be writable so that BackupBuddy can easily create and modify backup and related files in that directory. If those permissions are not setup properly, either automatically or manually, you'll run into the "'''Unable to create backup storage directory'''" or similar errors.
*To verify and change any file or folder permissions:
**Easily and quickly learn what permissions are and how to change them in the official [http://codex.wordpress.org/Changing_File_Permissions WordPress File Permissions page]
**Ask your host to verify or do it for you.
**Make sure your backups folder directory in '''wp-content/uploads''' is set to 755 (permission).
**Make sure your '''wp-content/uploads''' folder and everything under/in it is set to 755 also (called recursive permissions OR changing permissions recursively).
*Support thread with detailed info
** http://ithemes.com/forum/index.php?/topic/5270-backupbuddy-setting-permissions-and-security-implications/#p24242

==Big backup files with both "Force Compatibility Mode" and PHP exec() function enabled==
*If PHP exec() function is enabled on your server AND you have "Force Compatibility Mode" setting enabled, you may run into backup file size issues. The compatibility mode does NOT support folder exclusions, and thus your backups may be very big.
*Solution:
**If your server has '''PHP exec() enabled''', go into '''BackupBuddy --> Settings''' and '''disable "Force Compatibility Mode"''' option.
*Related links with solution:
**http://ithemes.com/forum/index.php?/topic/18007-utterly-botched-wordpress-migration/

==Dropbox Backups Not Arriving==
Sometimes, backups sent to Dropbox never arrive (meaning they never show up) in Dropbox.
*'''Possible reasons:'''
**Due to the Dropbox API limits, each backup file has to be loaded into your server's memory and then sent to Dropbox. Dropbox requires PHP oAuth. Because of that, your server may run out of the required memory to do other things at the same time. When your server does not have enough memory to do multiple things at once, it may take longer than usual to complete each task, and the Dropbox process may take longer than the allowed time in PHP maximum_execution_time. This will simply result in the Dropbox process to time out and cancel. Since the limitation is because Dropbox requires PHP oAuth, there is no current workaround other than more memory.
**BackupBuddy can only transfer full backup files that can easily or be fully loaded into your server's memory. So if your backup file size is 200mb BUT your server memory size is only 128mb, your server will not be able to handle such a backup transfer to Dropbox, even if Dropbox allows such a transfer. If a Dropbox transfer exceeds your server memory limits, the backup will definitely not be transferred properly or at all. This is a server limitation, usually on less powerful servers, that we're trying to find a fix for.
**Your server or site has file transfer or PHP script processing limits which is resulting in the transfer not finishing.
**Your Dropbox connection settings are wrong.
**Your server may not have enough memory to perform this transfer.
**Your backup is around or larger than 300mb. Dropbox has a 300mb file size limitation when uploading files online via a file. Dropbox has a limitation of 300mb per file size upload limit when done via anything other than the Desktop dropbox client. This limitation is thus imposed on BackupBuddy also by Dropbox.
*'''Solutions to try:'''
**Make sure your Dropbox connection settings are right.
**Delete your current Dropbox connection and then re-create the Dropbox connection. See if that works.
**Most important and basic thing to try: wait 10 to 15 minutes for the backup to arrive before giving up. Dropbox uploads can be slow due to Dropbox itself. Dropbox has been known to show files even 30 minutes after a backup file was sent.
**Ask your host to increase the PHP maximum_execution_time. This is usually 30 seconds. Try increasing it to something much higher temporarily to see if that makes any difference.
**Ask your host if your server can get more allotted memory.
**Ask your host to enable PHP error logging to a file that you can access.
***What this does is create an entry, in a txt file on your server that your host can tell you the location of, every time there is a PHP related error or warning. When DropBox times out, this file can most probably give you an exact error message that you can tell your host to address or fix.
**Try sending a smaller backup file OR simply a database backup file to Dropbox. You can also use the Exclude option to exclude folders and files you do not need or to test things. See if such smaller files arrive. If they do, your issue is definitely with the larger file sizes.
**Try excluding certain folders from the backups via '''BackupBuddy --> Settings''' and then see if the smaller-than-before backup files get to Dropbox. Dropbox has a limit of 300mb per file size upload when uploading any file through any channel other than the desktop client. Therefore, this 300mb max size per each file limit is imposed by Dropbox on BackupBuddy also. Excluding unwanted folders can help reduce your backup file sizes.
*'''Related links:'''
**http://ithemes.com/forum/index.php?/topic/18099-dropbox-not-working/#p85173
**http://ithemes.com/forum/index.php?/topic/17812-no-downloads-to-dropbox/#p83619

==Database SQL (MySql) file inside full backups==
In full backups, the actual database is backed up also. To find this file, look for the following folder in your backup file after you have extracted/unzipped the backup zip file:

wp-content/uploads/backupbuddy_temp/'''NAMEOFBACKUP'''

The '''NAMEOFBACKUP''' part in the above link will be the exact same as the last set of characters, after the date, in your backup file name.

For example, if your backup file name is:

'''backup-domain_com-2012_05_29-''ukitenaifg'''''

then the folder inside a full backup where your database file is saved is

wp-content/uploads/backupbuddy_temp/'''ukitenaifg'''

==BackupBuddy Tab Missing in WordPress==
*If the BackupBuddy Tab is missing in your WordPress Admin area, there could be a few reasons for it:
**'''MULTISITES:''' If you are activating BackupBuddy on a single site inside a Multisite instead of using the NETWORK ACTIVATE option, BackupBuddy options will be hidden on purpose for security reasons. You must use [http://ithemes.com/codex/page/Installing_BackupBuddy#Multisite Network NETWORK ACTIVATE] instead.
**Try disabling other plugins which may be causing a conflict OR not allowing BackupBuddy tab to show up in WordPress admin area, even if direct links to such areas work.

*Related links
**[http://ithemes.com/codex/page/Installing_BackupBuddy#Multisite Network Active BackupBuddy on Multisites]
**[http://ithemes.com/forum/index.php?/topic/18395-backupbuddy-installed-and-working-but-missing-from-wordpress-left-panel/ Plugin conflicts causing BackupBuddy to disappear in WordPress Admin panel]

=Restoring/Migrating=

==Importbuddy asking for an authentication password when it didn't used to==
Importbuddy did not used to have a mandatory password to be ran or downloaded. However, it does now as of version 2.2.33 of BackupBuddy.

If using an older file that you never set a password for that is now asking for a password then:
* Set a password for importbuddy in BackupBuddy's Settings page. Then download and use this new importbuddy.

==Step 3 in import results in importbuddy.php file being downloaded when "Next Step" is clicked==
This problem happens because the .htaccess file being imported conflicts with the way your new host/server/site, where you are importing to, runs and processes php files.

* To fix it, try any of the following (keep going through the steps till you solve the problem - the Second step below should solve the problem completely)
** First, make sure you have the latest version of BackupBuddy's importbuddy.php (gotten from the download link available on the BackupBuddy main Backup page.)
** Second, read this exact issue explained in detail on PluginBuddy http://pluginbuddy.com/site-migration-heaven-one/ That has detailed steps on how to solve this.
** Third, AFTER you encounter the problem, since the importbuddy.php file already has extracted the files:
*** Rename the .htaccess file in the newly extracted folder/area to anything like .htaccess_backup
*** Restart the import process again.
*** This time, in the Advanced Tab, select the option to "Skip File Unzip", since the files have already been extracted.
*** After the site has been restored, go into your Settings --> Permalinks area to simply save that page, without making any changes. That will recreate the necessary .htaccess file again for the newly imported file.
** Make sure all file, folder and any other permissions are set properly before and after the backup and restore.
* This is probably the SAME as the other issue of [http://ithemes.com/codex/page/BackupBuddy:_Frequent_Support_Issues#Importbuddy.php_shows_ACTUAL_file_contents_instead_of_the_next_step Importbuddy showing actual file contents instead of the next step]

You should now be able to pass Step 3 without any issues.

* Similar pages/threads with solutions:
** http://pluginbuddy.com/site-migration-heaven-one/
** http://ithemes.com/forum/index.php?/topic/17933-backupbuddy-after-step-3-downloads-importbuddyphp/
** http://ithemes.com/forum/index.php?/topic/13350-step-3-click-next-step-downloads-a-file-does-not-go-to-step-4/
** http://ithemes.com/forum/index.php?/topic/15420-impurtbuddy-step-3-problem/
** http://ithemes.com/forum/index.php?/topic/16443-cant-get-past-step-3-asks-to-download-importbuddyphp-over-and-over/
** http://ithemes.com/forum/index.php?/topic/13375-rackspace-server-cant-migrate-to-it-using-importbuddy/
** http://ithemes.com/forum/index.php?/topic/13660-help-with-migration/
** http://ithemes.com/forum/index.php?/topic/14350-cannot-move-past-step-3-in-migration/
** [http://ithemes.com/codex/page/BackupBuddy:_Frequent_Support_Issues#Importbuddy.php_shows_ACTUAL_file_contents_instead_of_the_next_step Importbuddy showing actual file contents instead of the next step]

=='''Parse error''': syntax error, unexpected T_STRING, expecting T_OLD_FUNCTION or T_FUNCTION or T_VAR or '}' in /.../importbuddy.php on line 7974 (or any line)==
This error usually means that your site/server, where you are importing to, is running PHP4. BackupBuddy and importbuddy.php require at least PHP5 to function properly.
*It's usually easily fixable:
** Make sure you are using PHP5 and not PHP4.
** Change your PHP settings yourself to run PHP5.
** Ask your host to make sure you're running PHP5.
*Related customer thread with solution
**http://ithemes.com/forum/index.php?/topic/18009-parse-error/

==Extraction of zip files (unzipping) does not work==

Sometimes your host or site setup may prevent importbuddy.php from extracting (unzipping) the backup file.

Here are 2 manual solutions, one via FTP and one via cPanel, on unzipping the files manually and then continuing the importbuddy.php process. Try either of the following:

* http://pluginbuddy.com/restoring-an-unzipped-backup-with-backupbuddy/
* http://pluginbuddy.com/tutorials/unzip-backup-zip-file-in-cpanel/

IMPORTANT: Make sure you choose "Skip zip file extraction", under the "Advanced Configuration Options" tab on Step 1, to tell importbuddy.php to SKIP the extraction process. The import should work fine then while skipping the extraction process.

==Old importbuddy overwriting on unzip==
* Possible Symptoms:
** importbuddy behaves differently or stops functioning properly after the extraction step.
** Weird errors are seen after the extraction step.
** The importbuddy version at the bottom of importbuddy changes after the extraction step.
** Error: "Error! The unzip process reported success but the backup data file, backupbuddy_dat.php was not found in the extracted files. The unzip process either failed (most likely) or the zip file is not a proper BackupBuddy backup."
** Error 9003.
* Possible Solutions:
** Open the backup ZIP and delete the importbuddy.php file within it.
** Replace the importbuddy.php on your server after the extraction step but before moving forward further.

==After import: The source site is now redirecting to the destination site (or vice versa):==
* This occurs if the new database settings were not entered during Step 4 of importbuddy.php. Because of this, both sites are now sharing the same database so one of them (usually source) is redirecting to the other (usually destination). importbuddy.php needs to be re-run inputting the source URL on Step 4 and using the source database settings. This will reconfigure the source database to use its proper URL. Next importbuddy.php needs to be run again inputting the destination URL on Step 4 with the NEW database settings for the new database. This way both sites will have their own database for their respective URLs.
* importbuddy no longer overwrites existing WordPress databases by default so this issue is not as common as it used to be.

==After import: WordPress Error: `You do not have sufficient permissions to access this page`==
One or more of your database table prefixes did not get changed during migration. A fix is available here: http://www.tech-evangelist.com/2010/02/06/wordpress-error-sufficient-permissions/

==Cannot Log-in and Keep Getting Redirected Back to Log-In Page==
The migration completed successfully and the site is browse-able but when you try to log in you keep getting redirected back to the log-in page and the URL looks something like this:
<pre>http://wptest.local/wp-login.php?redirect_to=http%3A%2F%2Fwptest.local%2Fwp-admin%2F&reauth=1</pre>

This is a common WordPress related issue and not a result of BackupBuddy backup or restore/import. It is easily fixable, though, and happens mainly because of some plugin or custom edit somewhere in WordPress causing WordPress to keep redirecting to a specific url for admin login.

* Solutions (try any of these to see if they work - make a backup of everything Or keep you BackupBuddy backup in case something goes wrong or you want to undo some changes you make below):
** Edit W3 Total Cache settings to fix this, if you are using or have used W3 Total Cache. Please check in your wp-config.php for a line such as this:<pre>define('COOKIE_DOMAIN', 'www.domain.com'); // Added by W3 Total Cache</pre> In order to be able to log-in please either delete the line; or comment out the line; or change the string 'www.domain.com' to false - note that false is not enclosed by quotes, e.g.,: <pre>define('COOKIE_DOMAIN', false); // Added by W3 Total Cache</pre> You will now be able to log-in and can then attend to updating this definition as required by your new site configuration. To read more about COOKIE_DOMAIN please visit: [http://codex.wordpress.org/Editing_wp-config.php#Set_Cookie_Domain WordPress Codex - Cooke Domain]
** Make sure your wp-config.php files does NOT have any hard-coded SITE or WordPress URI that may be causing this issue.
** Make sure there is no duplicate .htaccess file.
** Make sure the existing .htaccess file does not contain anything related to the Site or WordPress URL that is causing the redirect.
** Make sure the wp_options table does not have any OLD url's which were NOT updated prior to the move.
** Make sure you use the latest versions of BackupBuddy and importbuddy.php (even try importbuddy.php beta to see if that makes a difference)
** Disable conflicting/all plugins by renaming the folder names of the individual plugins to something different.

* Some good posts with good/alternate solutions/info on this:
** http://ithemes.com/forum/index.php?/topic/14324-getting-redirected-when-trying-to-login/
** http://ithemes.com/forum/index.php?/topic/14102-new-site-wp-admin-redirect-back-to-original-sites-wp-admin/
** http://ithemes.com/forum/index.php?/topic/13581-access-admin-backend/
** http://ithemes.com/forum/index.php?/topic/17383-wp-content-files-on-subdomain-redirect-to-root/
** http://codex.wordpress.org/Login_Trouble
** http://wordpress.org/support/topic/keeps-redirecting-when-logging-in
** http://codex.wordpress.org/Editing_wp-config.php#Set_Cookie_Domain
** [http://wordpress.org/support/topic/domain-redirection-keeps-forwarding-to-signup-page Multisite Redirects]

==Blank OR strange homepage/frontpage BUT admin area works perfectly==
This usually happens when there is an existing and unwanted index.html, default.html or some other server default file already in the root of WordPress directory of your new restore/migrated site.
*Solution:
**Make sure your .htaccess file is not causing the issue.
**Make sure you delete any extra index.html, default.html or any other server default file that is already in the root of the WordPress directory of your newly restored/migrated site.
**Make sure your WordPress's index.php file is correct. If not, you can always download the latest version from WordPress.org and use the index.php file from that download (with any changes you may have made to the existing index.php file) to replace the index.php already present in your site.
**Make sure your theme's index.php and other theme files contents and permissions are correct.
**Make sure your theme settings in the WordPress admin section are correct.
** Make sure the home URL got updated in the database.
*** Can also use RepairBuddy to verify home URL.
*Related customer thread with easy solution:
**http://ithemes.com/forum/index.php?/topic/17989-update-in-progress-after-migrate/

==Where can I get the latest BETA of importbuddy.php?==
Starting with version 2.2.14, BackupBuddy now also includes a way to download the latest BETA version of importbuddy.php which will have the latest bleeding edge features. The link is in your BackupBuddy admin area.
* To download the latest BETA version of importbuddy.php
** Click the BackupBuddy tab OR the downward arrow in front of it to expand it.
** Click the Backup & Restore link under that tab.
** Look at the 3 images on that page, specifically the right most image called "Restore/Migrate."
** Right under it will be a link text "'''''Try the latest <ins>beta version here</ins>'''''" - that is your download link.
** Click that link to download the latest BETA version of importbuddy.php to your computer.
** Upload and use that file anywhere you want to restore/migrate your BackupBuddy backups.
* Here is the image of your '''BackupBuddy --> Backup & Restore''' area, where the latest BETA importbuddy.php download link is:
**[[File:Backupbuddy-importbuddy-beta.jpg|Image of where the latest BETA importbuddy.php download link is]]

==Links (permalinks) return 404 errors==
====Most Common====
* The [[.htaccess]] file was not configured properly or was not writable so importbuddy didn't update it.
** Solution: Log in to the admin dashboard and navigate to: Settings -> Permalinks and click 'Save Changes'. This regenerates your .htaccess entries correcting most problems.
* To manually fix, edit the [[.htaccess]] file in a text editor following the format on the [[.htaccess]] page.
* If getting this after a migration in which it redirected you to home page during the migration's step 5
** Cause: .htaccess file is causing redirections.
** Solution:
*** 1) Redo import and pause after Step 2 (file extraction).
*** 2) After step 2 (but before continuing to step 3) delete the .htaccess file in the root of the site.
*** 3) Continue the import to completion
*** 4) Regenerate the .htaccess file in WordPress by going to Settings -> Permalinks -> and clicking to "Save Changes"
* [http://codex.wordpress.org/Using_Permalinks#Fixing_Permalink_Problems See WordPress' official page on Fixing Permalinks for more solutions.]

====Users of XAMPP (Windows)====
Some versions of XAMPP do not enable mod_rewrite by default (though it is compiled in Apache). To enable it — and thus enable WordPress to write the .htaccess file needed to create pretty permalinks — you must open apache/conf/httpd.conf and uncomment the line LoadModule rewrite_module modules/mod_rewrite.so (i.e., delete the hash/pound sign at the front of the line).
====Users of WAMP (Windows)====
Some versions of WAMP (all versions?) do not enable mod_rewrite or permit following SymLinks by default. To enable the required functionality navigate to the apache/conf/httpd.conf file, open with a text editor and uncomment the line LoadModule rewrite_module modules/mod_rewrite.so (i.e., delete the hash/pound sign at the front of the line). Then further down in the same file there is a section that starts with the line "Options FollowSymlinks". Change the second line in that section from "AllowOverride none" to AllowOverride all. Save edited httpd.conf and restart all WAMP modules. Your permalinks should now work.
====Users of Ubuntu + Apache====
The packaged version of Apache that came down with apt-get lamp-server^ doesn't enable mod_rewrite by default. [http://serverfault.com/questions/139791/how-can-i-enable-mod-rewrite-in-apache-on-ubuntu This link is a step in the right direction], although you also might have to set the AllowOverride rules to "all" in /etc/apache2/sites-enabled/000-default. Also, after making those changes make sure to restart Apache. -- In summary, the steps that helped me fix this problem were: 1) Enable mod_rewrite on Apache, 2) Restart Apache, 3) Rename .htaccess to .htaccess.bak (move it out of the way), 4) Regenerate the .htaccess file (as above) --> login to your admin dashboard and go to Settings -> Permalinks -> and click the "Save Changes" button.

====500 Server Errors====
* [[.htaccess]] (click for details) file is causing URLs to be redirected improperly or is malformed. Sometimes the front end simply won't load.
** Regnerating the .htaccess file can solve. To do this login to your admin dashboard and go to Settings -> Permalinks -> and click the "Save Changes" button.
*** Note: You don't have to actually make any changes on the page to regenerate the .htaccess in this manner by clicking to "Save Changes".
* PHP is not functioning or enabled for the site. Check with basic [[phpinfo()]].
* A 404 error is occurring but the server is not set up correctly to return a 404. Do sanity check with .htm file.
* Manually edit the [[.htaccess]] file in a text editor following the format on the [[.htaccess]] page.
* Delete or manually remove your OLD .htaccess file from the extracted folders after it passes the step of extracting files, from the backup file (and then zip it again) OR before you do a backup.
* Edit your OLD .htaccess file to be basic without any extra comments that may be interfering on the new server.
* Make sure your new OR old .htaccess does NOT have any directive that is resulting in any website file, including the index, to be blocked.
* See `.htaccess being overwritten on unzip` below if it happens on Step 2 of import.
* Ask your host to look at the .htaccess file and to fix any errors with it, OR to delete the EXISTING AND/OR GENERATED .htaccess file OR to generate a new .htaccess file for you.

*Related links:
** http://ithemes.com/forum/index.php?/topic/18089-migration-failure-with-500-internal-server-error/
** [http://ithemes.com/forum/index.php?/topic/18445-restored-site-now-wont-load-and-cant-log-in/#p86642 Remove extra .htaccess lines which may be preventing the site from loading]
** [http://ithemes.com/forum/index.php?/topic/18607-internal-server-error-hostgator-rocks/ How HostGator helped a customer fix this error by simply fixing the bad .htaccess file]

==.htaccess being overwritten on unzip==
* Symptoms:
** PHP stops properly functions in importbuddy.php after the extraction step.
** Weird errors are seen after the extraction step.
* Solution:
** Open the backup ZIP and delete the .htaccess file within it, can be done before migrating.
*** Can also delete the .htaccess file in directory after step 2

==The backup zip file is not found==
* The zip file has been renamed to a non-BackupBuddy format.
* The zip file permissions are wrong. Ex: Not readable.
* The zip file is not in the same directory as importbuddy.php.
* The zip file has not finished uploading or was interrupted in transit. If BackupBuddy was used to send it try manually uploading.

==backupbuddy_dat.php OR db_1.sql was not found after extraction==
* You may be using an older version of importbuddy.php not compatible with your backup version. Try upgrading your importbuddy.php to the version in the latest BackupBuddy.
* You may have renamed your backup ZIP file. BackupBuddy depends on the naming format to determine where some data in the backup ZIP is stored. Rename your backup back to its original name.
* Your backup may be corrupt. Try manually unzipping to verify it extracts properly.

==SQL error near WH==
* It is because the table does not have a mysql primary key or unique index
** If you have Gravity Forms and the problem is in _rg_form_meta then upgrade Gravity Forms to version 1.6+

==Restoring database times out==
* You can try reducing the size of that database.
** Checking for extra large tables you don't need (such as deleted plugins leaving data behind).
** What revision retention policy do you operate on the posts? It may be that you have a lot of revisions stored in the database that you could safely remove. The WordPress Codex gives some information on controlling revisions (http://codex.wordpress.org/Editing_wp-config.php#Post_Revisions) but I don't think this acts retrospectively so you might need to find a method to prune any revisions you currently have.
* Seeing if host will increase memory limit and runtime can help as well.

==Extracting ZIP times out / hangs==
* Unzipping was not able to complete due to the unzipping process taking longer than the maximum PHP allowed runtime (usually 30 seconds).
* Solutions:
** Manual Unzip Process:
*** Manually extract the ZIP file on your computer then upload the files to the server.
*** Restart the importbuddy.php Import process, selecting `Skip Zip Extraction` from the advanced options slide-down.
** Or ask your host to increase the maximum PHP runtime beyond its current limit.

==Defined URL in wp-config.php==
* Symptoms:
** URL does not appear to update after migration.
** Links 404 after migration and you verified that you entered the correct URL to migrate to.
** Links can also redirect to old site at the defined URL, though usually they 404
** Cannot update url's in the admin area. Such fields are usually disabled, as WordPress disallows their editing if the home URL is in the wp-config.php file

==URLs redirecting to old site after migration==
* Symptoms: Home page is up and looks fine but links in the site all keep going to the old/source site.
* Solution:
** Re-run importbuddy.php entering the correct URLs and watching for any errors.
** Also make sure import is finishing correctly, may be timing out without realizing it.
*** Can check the importbuddy.txt log to see if it caught something, will be located in same place you uploaded the importbuddy file.
** Check for any hardcoded/defined URLs in the site's wp-config.php and HTML files.
*** If site URL is hardcoded in theme HTML files can wrap them in home_url( '/directory/' ) to fix.

==URL needs manually updated==
* Note that this does not update serialized data. In short, some plugins, such as PluginBuddy plugins may not have internal URLs updated. This is more of a last-choice solution.
* SQL to update URL in posts manually:
<pre class="brush:html">update wp_posts set post_content = replace(post_content, 'http://OLD_URL', 'http://NEW_URL');</pre>
* Command line zip test to check if exec is enabled and zip can create a file. Download: [[Media:Zip_test.zip]]

==The unzip process reported success but the backup data file...==
"Error! The unzip process reported success but the backup data file,
backupbuddy_dat.php was not found in the extracted files. The unzip
process either failed (most likely) or the zip file is not a proper
BackupBuddy backup."
* Most common cause: See [http://ithemes.com/codex/page/BackupBuddy:_Frequent_Support_Issues#Old_importbuddy_overwriting_on_unzip]
* The backup did not finish extracting (timed out).
* Verify the backup is not damaged.

==Importbuddy.php shows ACTUAL file contents instead of the next step==
There is one report that on Step 4, importbuddy.php started showing the actual importbuddy.php file contents. The reason for this was that the EXTRACTED .htaccess file from the OLD server/site was causing the issue.

This is VERY similar OR the same as [http://ithemes.com/codex/page/BackupBuddy:_Frequent_Support_Issues#Step_3_in_import_results_in_importbuddy.php_file_being_downloaded_when_.22Next_Step.22_is_clicked Step 3 downloading importbuddy.php file issue] which also contains possible reasons and solutions.

*Solutions
**Check your .htaccess file on the OLD server/site and fix any issues with it. THEN do the backup.
**After Step 3 has finished, and BEFORE proceeding to Step 4 (or any such step where this problem happens), open a new window OR your FTP program, go and find the EXTRACTED .htaccess file, EDIT it to remove any UNWANTED directives, and then switch back to the importbuddy.php window to continue onto the next step.
**On the OLD site, ALSO try saving your Permalinks again in WordPress --> Permalinks . Simply click "Save" on that page and then do a backup and retry the import/restore/migration.
**Thanks to our customer Chris Malone for finding the issue and finding a solution right away too.
**As mentioned above, this is VERY similar OR the same as [http://ithemes.com/codex/page/BackupBuddy:_Frequent_Support_Issues#Step_3_in_import_results_in_importbuddy.php_file_being_downloaded_when_.22Next_Step.22_is_clicked Step 3 downloading importbuddy.php file issue] which also contains possible reasons and solutions.

*Related link
**[http://ithemes.com/forum/index.php?/topic/18621-wont-continue-past-step-3-when-running-importbuddy/ User reporting the issue and the solution]
**[http://ithemes.com/codex/page/BackupBuddy:_Frequent_Support_Issues#Step_3_in_import_results_in_importbuddy.php_file_being_downloaded_when_.22Next_Step.22_is_clicked Step 3 downloading importbuddy.php file issue]

=BackupBuddy Classic=
BackupBuddy Classic is available to download in case you have an older system OR older system specs like older PHP, MySql and other things. BackupBuddy Classic does not have any of the new features of BackupBuddy.

If your system or host forces you to use BackupBuddy Classic, you should start considering switching to another host or server ( we recommend [http://ithemes.com/hostgator HostGator] ) which is not old or not updated regularly.

BackupBuddy Classic can be found in your Member's area and is labeled "'''BackupBuddy Classic'''."

*Related Link
** http://ithemes.com/forum/index.php?/topic/18448-download-legacy-versions-of-backupbuddy/#p86657

=Additional Resources=
# [http://pluginbuddy.com/purchase/backupbuddy/ Purchase BackupBuddy]
# [http://pluginbuddy.com/tutorials/ PluginBuddy Tutorials]
# [http://pluginbuddy.com/ PluginBuddy.com]
# [http://pluginbuddy.com/support/ Support Forums]

[[Category:PluginBuddy]]

BackupBuddy Multisite

2012-03-02T17:23:54Z

Bes: Removed BETA label. Updated with real webinar http://pluginbuddy.com/intro-to-backupbuddy-multisite-feb-8th-2012-webinar/ /* Running Backup, Migrating OR Restoring with BackupBuddy Multisite BETA */

BackupBuddy Multisite is the '''NEW BETA''' feature of the latest BackupBuddy which allows you to backup, migrate, restore OR copy your Multisite from one location to another, or back to the same location. '''BETA''' means that at this time, any new error or problem may occur including, but not limited to, the restore not importing image links properly, sub-domains OR sub-directory paths giving permalink errors, helping your cat escape from your home, and more.

This page is updated regularly every week, since we are working with all our Multisite customers DAILY in getting more features, fixes and enhancements into BackupBuddy Beta updates as fast as we can. Soon, the BETA status will be removed to signify the official fully supported and fully tested '''BackupBuddy Multisite''' release. [http://ithemes.com/codex/index.php?title=BackupBuddy_Multisite&action=submit#Support_Questions Please let us know of any suggestions or questions in the forums]!

As of version 2.2.14, the single BackupBuddy product contains BOTH the standard BackupBuddy AND the new BackupBuddy Multisite Beta. Your single BackupBuddy does it all!

=Getting BackupBuddy Multisite=

====BackupBuddy Backup Plugin====
BackupBuddy Multisite BETA is now an integral part of BackupBuddy itself. You simply [http://pluginbuddy.com/purchase/backupbuddy/ Get BackupBuddy] and then download it from your [http://ithemes.com/member/member.php Member's Area].

====BackupBuddy's IMPORTBUDDY.PHP File====
The importbuddy.php file, which is the awesome file that helps you MIGRATE/RESTORE your BackupBuddy backups, now has a BETA version also that is used when you want to migrate or restore your BackupBuddy Multisite backups. You must use the BETA importbuddy.php to restore/migrate any BackupBuddy Multisite backup file.

* Here is an image of your '''BackupBuddy --> Backup & Restore''' area, where the latest BETA importbuddy.php download link is:
**[[File:Backupbuddy-importbuddy-beta.jpg|Image of where the latest BETA importbuddy.php download link is]]

=Installing BackupBuddy Multisite=

Since BackupBuddy Multisite BETA is now part of BackupBuddy, the Installation steps are now integrated and the differences explained in the [http://ithemes.com/codex/page/Installing_BackupBuddy standard BackupBuddy Installation] section.

=Running Backup, Migrating OR Restoring with BackupBuddy Multisite BETA=

Here is an actual video, from one of our many webinars (we have many regular webinars planned), with details on how to migrate or restore with BackupBuddy:

{{#ev:youtube|WYhLIK3KfK4|600|BackupBuddy Multisite}}

=Frequently Asked Questions=

====WordPress Multisite Domain Mapping and BackupBuddy Multisite====

BackupBuddy Multisite works perfectly with WordPress Multisite Domain Mapping. Here is a detailed video of what is possible and how it's exactly done (better to see something in addition to reading about it too ;) ):

{{#ev:youtube|oDM5v2Ymk1M|600|BackupBuddy Multisite}}

====Limitations of Multisite====

There are 2 limitations (and for good reasons) in WordPress Multisite itself which BackupBuddy of course goes through automatically:
* 1 : If your multisite install is sub-domain based, you cannot migrate or restore to a sub-directory within your web root.
* 2 : You can not change from sub-domains to sub-directories using BackupBuddy Multisite. You can not use BackupBuddy to migrate from a sub-domain based install to sub-directories or vice-versa.

====Known Issues====

The following are known issues of BackupBuddy Multisite:

* 1 : You can not currently migrate a Multiste installation to a sub-directory, or migrate a Multisite installation based in a sub-directory back to the root of the domain. We are currently working on enabling this feature.
* 2: You can not duplicate a mapped domain. We are currently working on enabling this feature.

====Support Questions====

All BackupBuddy Multisite support questions can be asked in the official [http://ithemes.com/forum/backupbuddy-ms/ BackupBuddy Multisite Forums].

All non-Multisite related BackupBuddy support questions can be asked in the official [http://ithemes.com/forum/backupbuddy/ BackupBuddy Forums].

All BackupBuddy Pre-Sales questions, for Multisite OR non-Multisite backups and restores/migrations, can be asked on the [http://ithemes.com/forum/pre-sales-and-other-inquiries/ Pre-Sales Forums], via the Live Chat (the Panda icon on top of [http://pluginbuddy.com/purchase/backupbuddy/ Get BackupBuddy Multisite] page), or by emailing sales@ithemes.com

=Additional Resources=
====Official Pages====
*[http://pluginbuddy.com/purchase/backupbuddy/ Get BackupBuddy]
*[http://ithemes.com/codex/page/BackupBuddy BackupBuddy Codex - Self-Hosted and Multisite combined]
====Blog Posts====
*[http://pluginbuddy.com/5-reasons-to-love-backupbuddy-with-new-wordpress-multisite-support/ 5 Reasons to Love BackupBuddy with Multisite Support - Blog Article]
*[http://pluginbuddy.com/backupbuddy-multisite-migration-expanded-features-in-beta-coming-soon/ BackupBuddy Multisite Migration - Expanded Features in Beta - Announcement]
*[http://pluginbuddy.com/backupbuddy-ms-released-as-a-beta/ BackupBuddy Multisite Released as Beta - Announcement]
*[http://pluginbuddy.com/how-backupbuddy-changed-my-business-model/ How BackupBuddy changed one of our customer's entire business model!]

BackupBuddy Multisite

2012-03-02T17:21:30Z

Bes: Comment that was here is in View History for everyone to see - check out http://ithemes.com/forum/topic/24746-how-do-i-restoreimport-from-a-multisite-bub-export/ * Installing BackupBuddy Multisite */

BackupBuddy Multisite is the '''NEW BETA''' feature of the latest BackupBuddy which allows you to backup, migrate, restore OR copy your Multisite from one location to another, or back to the same location. '''BETA''' means that at this time, any new error or problem may occur including, but not limited to, the restore not importing image links properly, sub-domains OR sub-directory paths giving permalink errors, helping your cat escape from your home, and more.

This page is updated regularly every week, since we are working with all our Multisite customers DAILY in getting more features, fixes and enhancements into BackupBuddy Beta updates as fast as we can. Soon, the BETA status will be removed to signify the official fully supported and fully tested '''BackupBuddy Multisite''' release. [http://ithemes.com/codex/index.php?title=BackupBuddy_Multisite&action=submit#Support_Questions Please let us know of any suggestions or questions in the forums]!

As of version 2.2.14, the single BackupBuddy product contains BOTH the standard BackupBuddy AND the new BackupBuddy Multisite Beta. Your single BackupBuddy does it all!

=Getting BackupBuddy Multisite=

====BackupBuddy Backup Plugin====
BackupBuddy Multisite BETA is now an integral part of BackupBuddy itself. You simply [http://pluginbuddy.com/purchase/backupbuddy/ Get BackupBuddy] and then download it from your [http://ithemes.com/member/member.php Member's Area].

====BackupBuddy's IMPORTBUDDY.PHP File====
The importbuddy.php file, which is the awesome file that helps you MIGRATE/RESTORE your BackupBuddy backups, now has a BETA version also that is used when you want to migrate or restore your BackupBuddy Multisite backups. You must use the BETA importbuddy.php to restore/migrate any BackupBuddy Multisite backup file.

* Here is an image of your '''BackupBuddy --> Backup & Restore''' area, where the latest BETA importbuddy.php download link is:
**[[File:Backupbuddy-importbuddy-beta.jpg|Image of where the latest BETA importbuddy.php download link is]]

=Installing BackupBuddy Multisite=

Since BackupBuddy Multisite BETA is now part of BackupBuddy, the Installation steps are now integrated and the differences explained in the [http://ithemes.com/codex/page/Installing_BackupBuddy standard BackupBuddy Installation] section.

=Running Backup, Migrating OR Restoring with BackupBuddy Multisite BETA=

Here is an actual video, from one of our many webinars (we have many regular webinars planned), with details on how to migrate or restore with BackupBuddy Beta:

{{#ev:vimeo|29432403|600|BackupBuddy Multisite}}

=Frequently Asked Questions=

====WordPress Multisite Domain Mapping and BackupBuddy Multisite====

BackupBuddy Multisite works perfectly with WordPress Multisite Domain Mapping. Here is a detailed video of what is possible and how it's exactly done (better to see something in addition to reading about it too ;) ):

{{#ev:youtube|oDM5v2Ymk1M|600|BackupBuddy Multisite}}

====Limitations of Multisite====

There are 2 limitations (and for good reasons) in WordPress Multisite itself which BackupBuddy of course goes through automatically:
* 1 : If your multisite install is sub-domain based, you cannot migrate or restore to a sub-directory within your web root.
* 2 : You can not change from sub-domains to sub-directories using BackupBuddy Multisite. You can not use BackupBuddy to migrate from a sub-domain based install to sub-directories or vice-versa.

====Known Issues====

The following are known issues of BackupBuddy Multisite:

* 1 : You can not currently migrate a Multiste installation to a sub-directory, or migrate a Multisite installation based in a sub-directory back to the root of the domain. We are currently working on enabling this feature.
* 2: You can not duplicate a mapped domain. We are currently working on enabling this feature.

====Support Questions====

All BackupBuddy Multisite support questions can be asked in the official [http://ithemes.com/forum/backupbuddy-ms/ BackupBuddy Multisite Forums].

All non-Multisite related BackupBuddy support questions can be asked in the official [http://ithemes.com/forum/backupbuddy/ BackupBuddy Forums].

All BackupBuddy Pre-Sales questions, for Multisite OR non-Multisite backups and restores/migrations, can be asked on the [http://ithemes.com/forum/pre-sales-and-other-inquiries/ Pre-Sales Forums], via the Live Chat (the Panda icon on top of [http://pluginbuddy.com/purchase/backupbuddy/ Get BackupBuddy Multisite] page), or by emailing sales@ithemes.com

=Additional Resources=
====Official Pages====
*[http://pluginbuddy.com/purchase/backupbuddy/ Get BackupBuddy]
*[http://ithemes.com/codex/page/BackupBuddy BackupBuddy Codex - Self-Hosted and Multisite combined]
====Blog Posts====
*[http://pluginbuddy.com/5-reasons-to-love-backupbuddy-with-new-wordpress-multisite-support/ 5 Reasons to Love BackupBuddy with Multisite Support - Blog Article]
*[http://pluginbuddy.com/backupbuddy-multisite-migration-expanded-features-in-beta-coming-soon/ BackupBuddy Multisite Migration - Expanded Features in Beta - Announcement]
*[http://pluginbuddy.com/backupbuddy-ms-released-as-a-beta/ BackupBuddy Multisite Released as Beta - Announcement]
*[http://pluginbuddy.com/how-backupbuddy-changed-my-business-model/ How BackupBuddy changed one of our customer's entire business model!]

PluginBuddy

2012-03-01T17:58:28Z

Bes: Added http://ithemes.com/forum/topic/24737-backupbuddy-manage-licenses/page__view__findpost__p__115187 example for W3 Total Cache issues /* Plugin Conflicts */

Welcome to the PluginBuddy Knowledge Base - Tutorials, Technical Information, Debugging Information, and more.

=Premium Plugins=
* [[Ajax-Edit-Comments]]
* [[BackupBuddy]]
* [[DisplayBuddy]]
** [[Accordion]]
** [[Billboard]]
** [[Carousel]]
** [[CopiousComments]]
** [[FeaturedPosts]]
** [[Rotating Images]]
** [[RotatingText]]
** [[Slides]]
** [[Slideshow]]
** [[Tipsy]]
** [[VideoShowcase]]
* [[EmailBuddy]]
* [[Frolic]]
* [[LoopBuddy]]
* [[Mobile]]
* [[TailoredLogin]]
* [[ThumbsUp]]
* [[VidEmbed]]

=Free Plugins (active)=
* [[Featured Text]]
* [[PB-Tweet]]
* [[ServerBuddy]]
* [[Tabber Widget]]
* [[ThemeMan]]
* [[S3 URLS]]
* [[YOURLS]]
* [[ContactBuddy]]

=Free Plugins (inactive)=
* [[WP Easy Uploader]]
* [[WP Developer Assistant]]
* [[Easy Theme and Plugin Updater]]
* [[Current Date & Time Widget]]

''[[:Category:PluginBuddy|View all PluginBuddy Wiki Pages]]''

=Misc. Documentation=
==Frequently Asked (Plugin) Questions==
*[[General Plugins FAQ]]

==License Manager Tutorial and Information==
*[[License Manager]]
==PHP Development & Advanced==
*[[.htaccess]]
*[[PHP]]
*[[Arrays]]

[[Category:PluginBuddy]]

=Translations (localization / internationalization)=

Many PluginBuddy plugins come with translation capability. That means such PluginBuddy plugins can be translated (aka localized) to other languages.

===How Translations Work===

PluginBuddy provides the capability to have a translation in such plugins. Anyone wanting to enhance PluginBuddy with specific language translations can do so voluntarily via Translation Files. Translation Files are simply language files created fully and solely by the volunteer community which use the already built in translation-capable features in many of the PluginBuddy plugins to allow such plugins to show text or outputs in different languages. Making PluginBuddy translation-capable is done by PluginBuddy. Creating, updating and sending in any language specific translation files to PluginBuddy is done by the volunteer community.

Anyone can create translation files, package them into the proper format and give PluginBuddy the final translated files that we will try to include in the next update for the plugin in question. We call such awesome people, who create or update the translation files and send us the full translation package files, '''Awesome Translator Volunteers''', and we are really thankful that they take the time to do such an awesome thing.

If you want to help us, you can translate any existing PluginBuddy plugin which supports internationalization (another way of saying localization or translation-capable) and then, once you're fully done, simply let us know in the forums the link to the final language files that we can directly save and simply try to include in any future updates for the plugin(s) in question.

===Tips on how to localize any PluginBuddy Plugin to any non-English language===

The following 9 tips can help you figure out how to approach translations, how to create translations, and how to send us the final translated file for any translation-capable PluginBuddy plugin:

*1 : Many of the PluginBuddy plugins are internationalized, meaning they have the capability to be translated, via actual external translation files, by any non-iThemes-staff Awesome Translator Volunteer who wishes such plugins to be translated to their language.
*2 : If a PluginBuddy plugin is currently not internationalized or you're not sure if it is, you can ask us in the [http://ithemes.com/forum Support Forums] and we'll let you know, or we'll have it included as a future translation feature request. After the translation capability is added to such a plugin, you can submit the actual translation file. Please remember though: we cannot help with creating, understanding or making any language translation files. Our Awesome Translator Volunteers do that voluntarily (you can too! keep on reading) and fully on their own.
*3 : There are MANY resources which teach you how to create and work with WordPress language files. Following are the official 3 directly by the WordPress community:
**1 : [http://codex.wordpress.org/WordPress_in_Your_Language WordPress in Your Language]
**2 : [http://codex.wordpress.org/Translating_WordPress Translating WordPress]
**3 : [http://codex.wordpress.org/I18n_for_WordPress_Developers What WordPress Localization in Plugins is mainly about]
*4 : Translations are sent in from volunteers from all over the world. As a courtesy, we sometimes package the actual language translation files (provided directly by the Awesome Translator Volunteers) in with the final product. If some translation is not included in the actual plugin even when the plugin has the capability to be translated, you can submit the final translation to us for consideration in the next update by posting on our forums OR you can include the translation in your own live or local WordPress install directly for your own use. More info on how to include your own language specific file for your own WordPress sites is in the resources listed in #3 above.
*5 : A translation included in with the final product does not guarantee the accuracy or quality of the translation. These files are from the Awesome Translator Volunteers, and correction of these files is also done by those Awesome Translator Volunteers.
*6 : If a translation is very inaccurate or incomplete, we can put out a request for a new translation from the volunteer community, or remove the translation from the packaged and final product. You can also let us know of any inaccuracies in any existing translation files by the Awesome Volunteers by providing us with the corrected final files. Please remember: we only accept final and full translation files that you yourself have already created or packaged properly. If you let us know only of the actual inaccuracies without providing the final correct files, we cannot make such changes ourselves to the translation files.
*7 : Unfortunately, PluginBuddy cannot work on, help with, create, nor make any updates to any specific translation files you may have, or may be working on, or want to work on. Our Awesome Volunteers do that and simply give us the final files for inclusion or consideration.
*8 : If you have corrections for any existing translation in form of final proper format translation files for an existing language, OR want to provide the final and proper translation files for a new language, please post a new thread in the appropriate product category in the [http://ithemes.com/forum/ PluginBuddy Support Forums] with the final translations files. If you have any support questions on how to create or make language specific translation files, or how translation files work, you can do so on the [http://wordpress.org/support/ WordPress forums], as such support questions are outside the scope of what PluginBuddy support guarantees with your iThemes membership.
*9 : Any final translation file provided by you (or any other Awesome Volunteer) on the support forums will then be saved and filed as a future enhancement request for the future updates of the plugin(s) in question. In your support forum thread, where you share the final complete translation files you inclusion, you can upload your files directly to the forums OR upload them somewhere and link to them in your support forum thread. We will then download and save such files. Remember please: we cannot guarantee looking inside such files or verifying that they are correct in any manner (because of so many languages in the world and so many possible language files everywhere).

Thank you SO MUCH for being interested in providing translation files for our PluginBuddy plugins. We hope you will become one of our Awesome Translator Volunteers, in addition to being our AWESOME CUSTOMER, and create/update any language-specific translation file package and provide it to us so that we can consider including it in future updates.

===Resources for understanding, creating, updating and submitting final translation files===
*Here are the 3 official resources again which you can use to create, update, start work on and finish translation on any of the translation-capable PluginBuddy plugins:
**1 : [http://codex.wordpress.org/WordPress_in_Your_Language WordPress in Your Language]
**2 : [http://codex.wordpress.org/Translating_WordPress Translating WordPress]
**3 : [http://codex.wordpress.org/I18n_for_WordPress_Developers What WordPress Localization in Plugins is mainly about]

=Extra Customizations=
While any extra customization of any PluginBuddy Plugin is beyond the scope of the official support, we do from time to time offer different tips and tutorials on editing the awesome PluginBuddy plugins to better fit your individual needs. All such edits are, however, beyond what is officially supported and provided in the actual plugin admin panel and officially stated features on the individual plugin pages. No official support is provided nor guaranteed in, before, during, after or related to anything resulting from any such edits/customizations.

No support is provided on any of these extra customizations. Any of the steps mentioned in any of these extra custom edits may change at any time depending on newer versions of the plugins being released. Any use or customization of anything, beyond what is provided by default inside the plugin admin menu, means you are proceeding at your own risk and that you accept 100% responsibility and liability for everything you change or modify in any manner in the plugin. Your purchase and use of any PluginBuddy plugin implies and shows that you are buying and using PluginBuddy plugin(s) the way it(they) came in their original unmodified form, with no exceptions.

*Remember:
**[http://pluginbuddy.com/purchase/backupbuddy/ Make a backup of your entire site with BackupBuddy] before making any edits!
** PluginBuddy only supports the official unedited, unmodified versions of all PluginBuddy plugins.
** Use a good text editor to make any file changes. Again, maintain backups!
** Any changes you make to files WILL MOST PROBABLY be lost when the plugin is upgraded to any newer version.
** You are 100% responsible and liable for anything resulting from any of these changes.
** No support is provided nor guaranteed on any of these extra changes in any form or shape, whatsoever, regardless of who suggested these custom edits or suggestions.
** Any extra customization info or suggestion is added voluntarily by PluginBuddy staff to help users as much as possible, even if such customization is outside the scope of any membership support.
** Whether a PluginBuddy staff or representative offered or suggested the edit/customization, another customer or anyone else, PluginBuddy does not officially support nor provide any official support on any such edits.
** We cannot guarantee providing any support on any edits or customization tips we provide.
** Absolutely no support is guaranteed in any manner on any of our free plugins, whether or not there is any customization/edit involved.

=External Plugins Compatibility=

PluginBuddy does not promise, guarantee or provide support for any compatibility with any external plugin. If any PluginBuddy Plugin works without any problems when used with any external plugin in question, that means the PluginBuddy Plugin is most probably working without any issues overall. PluginBuddy is not responsible for making PluginBuddy plugins work in any manner, whether custom, fully, fixed or other, with any external non-PluginBuddy plugins. PluginBuddy is also not responsible for providing any support whatsoever for any external plugin, whether or not such an external plugin is used along with any PluginBuddy plugin.

=Free Plugins=

Free plugins are provided as is. There is no guaranteed support that comes with them. Guaranteed support is limited only and mainly for our premium unmodified plugins.

=Bugs, Features and ETA on new updates=

With every new release of any plugin, there may be a new bug or two. You may also want to have new features added to specific plugins. All existing versions of all plugins can have bugs reported OR new features suggested. All of this is done via the [http://ithemes.com/forum official forums].

New updates are also usually released regularly and at the same time, at very different paces, depending on the current number of bugs, features, new plans and tasks at hand. Therefore it is the official policy that there is NO pre-defined ETA on any bug fix, feature imeplemention OR new update OR new plugin roll-out UNLESS otherwise specified specifically in writing somewhere by an official iThemes employee.

==Bugs, bug reports and bug fixes==

Bug reports are filed and noted as they are encountered (thanks for reporting them to us!). There is never any ETA on any bug fixes unless otherwise noted.

==Feature Requests==

Feature requests and feature suggestions are basically future suggested features that users can suggest, and/or future features PluginBuddy may consider adding to the future versions of the plugin(s) in question (again, thanks for suggesting new features!).

There is no guaranteed ETA on when such feature requests will be implemented, unless otherwise noted. All suggested features are just that: suggestions. They remain suggestions until they're confirmed as officially in the works and to be included. Even then, unless a feature is actually rolled out publicly, there is no guarantee any feature suggestion will be implemented. We do our best to try and accommodate as many feature suggestions as possible.

Also, there is no guarantee that any feature request suggested will be implemented, unless otherwise noted.

==ETA on new updates==

Just like bug fixes and new features, there is never a guaranteed date nor a guaranteed time frame on when new updates will roll out. We work every single day of the week, all the time, on our plugins and thus every day there is something new and improved happening in almost all our plugins daily. Whenever we are ready to release any new updates publicly, you'll find out by seeing the plugin update notice in your WordPress OR in your [http://ithemes.com/member/member.php Member's area].

=What does BETA mean?=

Some of PluginBuddy plugins may be in Beta status OR may have Beta features. BETA simply means that some feature or specific part of the plugin is currently still in testing mode, and can cause issues if not used properly. All BETA plugins/features are not yet 100% stable, and thus should NOT be relied on to be working properly OR working at all. Throughout the iThemes Codex, any time the word "Beta" is used in any form, it refers to Beta plugins, Beta features, Beta status and/or anything related to the Beta nature that is officially announced or mentioned as such by any iThemes staff or on any of the Plugin pages, or in this Codex.

Beta implies that any new features or plugins are very close to being released as 100% working very soon, and that there may still be some issues to fix or test more before removing the Beta status. Since no single software of any kind can be tested under every system and site configuration in the world, the Beta status enables the Beta features to be tested out by as many people on as many different websites and configurations as possible.

*Some points to keep in mind when using any BETA plugin/feature:
**1 : Make [http://pluginbuddy.com/purchase/backupbuddy/ FULL WordPress backups] before using ANY beta feature.
**2 : Beta means that the current software feature is NOT complete, and that you are NOT forced to use such a feature at all. You are advised to WAIT until the BETA status is removed.
**3 : Using any Beta feature of any kind, whether it is an entire plugin or something inside a plugin, means and shows that you are fully accepting any liability for any risks involved.
**4 : Using any Beta feature of any kind, whether it is an entire plugin or something inside a plugin, means and shows that you are fully aware that there are all different kinds of risks involved with such features.
**5 : If you are concerned about your important data or anything bad that might happen as a result of using any Beta feature, do NOT use such Beta features.
**6 : ALWAYS make full [http://pluginbuddy.com/purchase/backupbuddy/ BackupBuddy Backups of all your important data] before using any Beta software, whether that Beta software is from PluginBuddy or from any other place.
**7 : If any issues are found in Beta, they are usually added to the list of bug fixes to be released as a whole, or for the next big update, instead of being updated OR fixed individually on a case by case basis.
**8 : Beta features are recommended to test and play with on test sites/servers and configurations with any dummy data, as long as you have [http://pluginbuddy.com/purchase/backupbuddy/ full backups of all important data] still.
**9 : iThemes is not liable nor cannot be held accountable for any unwanted results resulting from the use of BETA features.
**10 : The very name and nature of BETA shows clearly, without any doubt, that there will most probably be issues and problems involved when such labeled features are used anywhere.
**11 : Support for Beta features may be very limited. We usually simply collect all reports related to Beta features and collect them all for one big update in the future.
**12 : If you lose any important data or settings anywhere, or encounter damaged data or settings anywhere, because of any Beta feature, we will not be able to help you and will simply tell you to revert to your previous [http://pluginbuddy.com/purchase/backupbuddy/ backups]. We will also tell you to always wait for BETA status to be removed before using any such features.

If you do not fully understand what Beta means, OR are not willing to fully accept and be fully liable for any risks involved because of using such Beta software, you should NOT use the Beta software in any manner. In such a case, you should simply wait until the Beta status is removed.

*[http://pluginbuddy.com/what-does-beta-mean/ Blog post announcing what BETA means]

=PluginBuddy Licenses=

==Plugin Conflicts==

Some times, external plugins may cause issues in detaching, deleting, generating OR saving license keys. Such plugins may also cause issues when you want to manually or automatically upgrade plugins when you try to solve licensing issues.

Following is a list of currently known plugins which cause license detaching, deleting, generating OR saving issues. Please disable the following plugins, even temporarily, while you perform all the steps of manually OR automatically upgrading the PluginBuddy plugins in question, and detaching, deleting, generating and saving license keys for them. Keep such plugins disabled UNTIL all license key issues are gone OR at least while you perform these steps.

*Plugins causing PluginBuddy licensing issues
**'''W3 Total Cache or WP Super Cache :''' If you are using any caching plugin like '''W3 Total Cache''' or '''WP Super Cache''', please disable it temporarily and then carry out any required steps. You can re-enable the plugin in the end after everything works in terms of the licenses.
***Fix: Follow the above steps to fix this issue. [http://ithemes.com/forum/index.php?/topic/19436-backupbuddy-license-issue/#p92171 Steps also explained by BackupBuddy customer Laura (thanks!)]
**'''Any other CACHING or related plugin:''' Try disabling such plugins, performing the required steps, and then re-activating the Caching or related plugins in question.

*Related Links
**1 : [http://ithemes.com/forum/topic/24737-backupbuddy-manage-licenses/page__view__findpost__p__115187 Karlos deactivated W3 Total Cache, and that fixed the licensing issues]
**2 : [http://ithemes.com/forum/topic/23481-license-issue-pluginbuddy-developer-to-backupbuddy-both-unlimited/page__view__findpost__p__110368 Disabling W3 Total Cache modules allowed Greg to license BackupBuddy without any issues]
**3 : [http://ithemes.com/forum/topic/23275-unable-to-get-license-to-stick/page__pid__109503#entry109503 W3 Total Cache causing licenses to be deleted after a while]
**4 : [http://ithemes.com/forum/topic/22964-cant-find-stylesheet-to-make-adjustments-to-slider/page__view__findpost__p__107933 W3 Total Cache not allowing licenses to be saved properly]
**5 : [http://ithemes.com/forum/topic/22859-bub-licenses-not-taking-effect/page__view__findpost__p__107476 W3 Total Cache not allowing licenses to be saved - easy solution!]
**6 : [http://ithemes.com/forum/index.php?/topic/19079-wont-let-me-set-a-license-key/#p91663 W3 Total Cache plugin conflict and solution]
**7 : [http://ithemes.com/forum/index.php?/topic/19436-backupbuddy-license-issue/#p92171 W3 Total Cache plugin conflict and solution]
**8 : [http://ithemes.com/forum/index.php?/topic/20228-key-does-not-work/#p95697 W3 Total Cache plugin conflict and solution]
**9 : [http://ithemes.com/forum/index.php?/topic/19041-license-problem-causes-loss-of-all-bb-settings-way-to-get-them-back/ WP Super Cache conflict and solution]

==Licensing Issues==

There are some reports that some users have issues with their license insides the Licenses area of different PluginBuddy plugins, including BackupBuddy.

Remember: All your PluginBuddy plugins, including BackupBuddy, will CONTINUE WORKING PERFECTLY even with these licensing issues. You can keep using the plugins exactly how you want them even during these licensing issues. Your plugins are NOT affected by this licensing situation in any manner.

Your membership is also completely fine and you have NOT lost any license(s). The issue is happening to some customers who simply need to upgrade manually to the latest version of their plugin, if the automatic upgrade does not work.

*Plugins with the update versions which remove this issue completely
**ALL PluginBuddy Products

*You can upgrade via one of the following:
**Automatically upgrade to the latest version
**Manually update by downloading the latest zip version of your PluginBuddy plugin from your Member's panel and then
***Overwrite your existing plugin directory via FTP with the new files.
***De-activate the existing plugin, delete it via your '''WordPress --> Plugins''' area and then upload the newly downloaded zip file. Then re-activate the plugin.
**That will remove the issue completely.
*DETACH the key and then RE-ATTACH the license key for the specific site in question IF licensing still shows issues AFTER manually upgrading to the latest version of the plugin in question (check your Member's area for the latest version download)
*Also make sure to DETACH the key, DELETE that same AND any other keys related to that specific site from the entire licenses area, and then GENERATE a new key for that site IF detaching and re-attaching the license key does not work AFTER manually upgrading (for example, manually upgrading to the latest BackupBuddy version - all plugins have their own latest version numbers - check your Member's area for the latest version download)

[http://ithemes.com/forum/index.php?/topic/6691-read-this-first-pluginbuddy-licensing-issues/page-2/#p85977 First reports]

Frolic

2012-02-27T19:34:47Z

Bes: Added link to http://ithemes.com/forum/topic/24334-styling-of-short-codes/page__gopid__114391#entry114391 to show styling example /* Built in Styling Helpers */

{{#ev:youtube|AAKFR4Vzl88|400|right}}

Frolic is available as a [http://pluginbuddy.com/purchase/frolick/ stand-alone plugin].

==Description==
The Frolic plugin adds the ability to integrate various social media features into your site. With support for Twitter, Facebook, and Google+, you integrate useful social media feature such as `Like` buttons, sharing, feeds, and more via shortcodes and widgets. Each social object may be customized and you can have multiple customized instances of each object.

==Accounts==
The first step in adding Frolic social media features to your site is to add your account in the Frolic settings. Frolic allows you to create multiple accounts with unique settings. Each account has multiple different social media objects you can insert into your site.

==Feature Overview==

===Shortcode & Widget Objects===

'''Twitter'''
* Display the latest tweets from user(s).
* Tweet button.
* Follow button.
* Hashtag button.
* Mention button.

'''Facebook'''
* Like button.
* Comments Block
* Activity Feed
* Send Button
* Recommendations

'''Google+'''
* +1 button
* Google+ badge

===WordPress Admin===
* View Twitter activity from Dashboard
* View Facebook Activity and Comment Feeds from Dashboard

All PluginBuddy plugins also support automatic upgrades and support.

===Built in Styling Helpers===
* Each object now has a div in the style of -- div class="pb-frolic pb-frolic-{account type} pb-frolic-{object type} pb-frolic-object-{id number}"
* Account types will be facebook, google, or twitter. Object type will be something like 'like-button', and id number is a number generated using the account and object id.
* [http://ithemes.com/forum/topic/24334-styling-of-short-codes/page__gopid__114391#entry114391 Example of how to use styling and move all Frolic objects into one line easily with real example code]

==Additional Resources==
# [http://pluginbuddy.com/free-wordpress-plugins/ Free Plugins by PluginBuddy]
# [http://pluginbuddy.com/tutorials/ PluginBuddy Tutorials]
# [http://pluginbuddy.com/ PluginBuddy.com]
# [http://ithemes.com/forum/tipsy/ Tipsy Support Forums]

[[Category:PluginBuddy]]

Slides

2012-02-11T05:14:03Z

Bes: Updated Slides forum and main page links

Slides is available as part of the [http://pluginbuddy.com/purchase/displaybuddy/ DisplayBuddy Series].

==Description==
The Slides plugin adds the ability to easily integrate sliding presentations, consisting of slides, into your website. Your Slides presentation optionally displays a numbered or bulleted list of slides for easy navigation and the ability to manually or auto-advance. Slides supports multiple groups of slide presentations. Each slide presentation may contain unlimited slides. Slides are made by selecting a slide layout, selecting an image to use in the layout, then adding content in the WYSIWYG editor. The WYSIWYG editor is provided when adding/editing each individual slide so you may easily customize the look and feel of the slide even with little to no HTML knowledge, just like a normal WordPress post or page is created.

Slides is great for creating presentations of information such as telling a story, presenting news, or giving tutorial walkthroughs. Any information you'd like to quickly split up and display with or without an associated image can be displayed well with this tool.

==Feature Overview==

* Unlimited slide groups with unlimited slides within.
* Six standard slide layouts (assign per slide):
** Image Left (image on the left; content on the right)
** Image Right (image on the right; content to the left)
** Image Top (image on the top; content below)
** Image Bottom (image on the bottom; content above)
** Image as Background (slide content goes over image which is set as background)
** No Image (content / text only)
* Widget support.
* Shortcode support.
* WYSIWYG editor.
* Drag & drop re-ordering of slides.

All PluginBuddy plugins also support automatic upgrades and support.

==Options per Slides group==
* Display next/previous buttons
* Display pagination (numbered tabs for jumping ahead)?
* Fade speed.
* Slide speed.
* Slide effect.
* Cross fade?
* Randomize slides?
* Auto play?
* Pause on manual advancement?
* Pause on hover?
* Auto adjust height?
* Auto height adjust animation speed.
* Make whole slides link to the next?

==Future==
* Preload images?

==Usage==

# Create a Slides group.
# Add one or more slide(s) into your Slides group.
## Hover over your group you would like to add slides to and click to Add Slides.
## Select the layout format you would like to use for this slide.
## Select an image for use in the Slide (if applicable).
## Enter your content in the WYSIWYG editor.
## Save the slide; add more slides if desired.
# Add as a widget or shortcode.

==Additional Resources==
# [http://ithemes.com/forum/forum/170-slides/ Slides forum]
# [http://pluginbuddy.com/purchase/displaybuddy/ Get Slides as part of DisplayBuddy]

[[Category:PluginBuddy]]

PluginBuddy

2012-02-08T20:24:02Z

Bes: Added http://ithemes.com/forum/topic/23481-license-issue-pluginbuddy-developer-to-backupbuddy-both-unlimited/page__view__findpost__p__110368 /* Plugin Conflicts */

Welcome to the PluginBuddy Knowledge Base - Tutorials, Technical Information, Debugging Information, and more.

=Premium Plugins=
* [[Ajax-Edit-Comments]]
* [[BackupBuddy]]
* DisplayBuddy
** [[Accordion]]
** [[Billboard]]
** [[Carousel]]
** [[CopiousComments]]
** [[FeaturedPosts]]
** [[Rotating Images]]
** [[RotatingText]]
** [[Slideshow]]
** [[Tipsy]]
** [[VideoShowcase]]
* [[EmailBuddy]]
* [[Frolick]]
* [[LoopBuddy]]
* [[Mobile]]
* [[TailoredLogin]]
* [[ThumbsUp]]
* [[VidEmbed]]

=Free Plugins (active)=
* [[Featured Text]]
* [[PB-Tweet]]
* [[ServerBuddy]]
* [[Tabber Widget]]
* [[ThemeMan]]
* [[S3 URLS]]
* [[YOURLS]]
* [[ContactBuddy]]

=Free Plugins (inactive)=
* [[WP Easy Uploader]]
* [[WP Developer Assistant]]
* [[Easy Theme and Plugin Updater]]
* [[Current Date & Time Widget]]

''[[:Category:PluginBuddy|View all PluginBuddy Wiki Pages]]''

=Misc. Documentation=
==Frequently Asked (Plugin) Questions==
*[[General Plugins FAQ]]

==License Manager Tutorial and Information==
*[[License Manager]]
==PHP Development & Advanced==
*[[.htaccess]]
*[[PHP]]
*[[Arrays]]

[[Category:PluginBuddy]]

=Translations (localization / internationalization)=

Many PluginBuddy plugins come with translation capability. That means such PluginBuddy plugins can be translated (aka localized) to other languages.

===How Translations Work===

PluginBuddy provides the capability to have a translation in such plugins. Anyone wanting to enhance PluginBuddy with specific language translations can do so voluntarily via Translation Files. Translation Files are simply language files created fully and solely by the volunteer community which use the already built in translation-capable features in many of the PluginBuddy plugins to allow such plugins to show text or outputs in different languages. Making PluginBuddy translation-capable is done by PluginBuddy. Creating, updating and sending in any language specific translation files to PluginBuddy is done by the volunteer community.

Anyone can create translation files, package them into the proper format and give PluginBuddy the final translated files that we will try to include in the next update for the plugin in question. We call such awesome people, who create or update the translation files and send us the full translation package files, '''Awesome Translator Volunteers''', and we are really thankful that they take the time to do such an awesome thing.

If you want to help us, you can translate any existing PluginBuddy plugin which supports internationalization (another way of saying localization or translation-capable) and then, once you're fully done, simply let us know in the forums the link to the final language files that we can directly save and simply try to include in any future updates for the plugin(s) in question.

===Tips on how to localize any PluginBuddy Plugin to any non-English language===

The following 9 tips can help you figure out how to approach translations, how to create translations, and how to send us the final translated file for any translation-capable PluginBuddy plugin:

*1 : Many of the PluginBuddy plugins are internationalized, meaning they have the capability to be translated, via actual external translation files, by any non-iThemes-staff Awesome Translator Volunteer who wishes such plugins to be translated to their language.
*2 : If a PluginBuddy plugin is currently not internationalized or you're not sure if it is, you can ask us in the [http://ithemes.com/forum Support Forums] and we'll let you know, or we'll have it included as a future translation feature request. After the translation capability is added to such a plugin, you can submit the actual translation file. Please remember though: we cannot help with creating, understanding or making any language translation files. Our Awesome Translator Volunteers do that voluntarily (you can too! keep on reading) and fully on their own.
*3 : There are MANY resources which teach you how to create and work with WordPress language files. Following are the official 3 directly by the WordPress community:
**1 : [http://codex.wordpress.org/WordPress_in_Your_Language WordPress in Your Language]
**2 : [http://codex.wordpress.org/Translating_WordPress Translating WordPress]
**3 : [http://codex.wordpress.org/I18n_for_WordPress_Developers What WordPress Localization in Plugins is mainly about]
*4 : Translations are sent in from volunteers from all over the world. As a courtesy, we sometimes package the actual language translation files (provided directly by the Awesome Translator Volunteers) in with the final product. If some translation is not included in the actual plugin even when the plugin has the capability to be translated, you can submit the final translation to us for consideration in the next update by posting on our forums OR you can include the translation in your own live or local WordPress install directly for your own use. More info on how to include your own language specific file for your own WordPress sites is in the resources listed in #3 above.
*5 : A translation included in with the final product does not guarantee the accuracy or quality of the translation. These files are from the Awesome Translator Volunteers, and correction of these files is also done by those Awesome Translator Volunteers.
*6 : If a translation is very inaccurate or incomplete, we can put out a request for a new translation from the volunteer community, or remove the translation from the packaged and final product. You can also let us know of any inaccuracies in any existing translation files by the Awesome Volunteers by providing us with the corrected final files. Please remember: we only accept final and full translation files that you yourself have already created or packaged properly. If you let us know only of the actual inaccuracies without providing the final correct files, we cannot make such changes ourselves to the translation files.
*7 : Unfortunately, PluginBuddy cannot work on, help with, create, nor make any updates to any specific translation files you may have, or may be working on, or want to work on. Our Awesome Volunteers do that and simply give us the final files for inclusion or consideration.
*8 : If you have corrections for any existing translation in form of final proper format translation files for an existing language, OR want to provide the final and proper translation files for a new language, please post a new thread in the appropriate product category in the [http://ithemes.com/forum/ PluginBuddy Support Forums] with the final translations files. If you have any support questions on how to create or make language specific translation files, or how translation files work, you can do so on the [http://wordpress.org/support/ WordPress forums], as such support questions are outside the scope of what PluginBuddy support guarantees with your iThemes membership.
*9 : Any final translation file provided by you (or any other Awesome Volunteer) on the support forums will then be saved and filed as a future enhancement request for the future updates of the plugin(s) in question. In your support forum thread, where you share the final complete translation files you inclusion, you can upload your files directly to the forums OR upload them somewhere and link to them in your support forum thread. We will then download and save such files. Remember please: we cannot guarantee looking inside such files or verifying that they are correct in any manner (because of so many languages in the world and so many possible language files everywhere).

Thank you SO MUCH for being interested in providing translation files for our PluginBuddy plugins. We hope you will become one of our Awesome Translator Volunteers, in addition to being our AWESOME CUSTOMER, and create/update any language-specific translation file package and provide it to us so that we can consider including it in future updates.

===Resources for understanding, creating, updating and submitting final translation files===
*Here are the 3 official resources again which you can use to create, update, start work on and finish translation on any of the translation-capable PluginBuddy plugins:
**1 : [http://codex.wordpress.org/WordPress_in_Your_Language WordPress in Your Language]
**2 : [http://codex.wordpress.org/Translating_WordPress Translating WordPress]
**3 : [http://codex.wordpress.org/I18n_for_WordPress_Developers What WordPress Localization in Plugins is mainly about]

=Extra Customizations=
While any extra customization of any PluginBuddy Plugin is beyond the scope of the official support, we do from time to time offer different tips and tutorials on editing the awesome PluginBuddy plugins to better fit your individual needs. All such edits are, however, beyond what is officially supported and provided in the actual plugin admin panel and officially stated features on the individual plugin pages. No official support is provided nor guaranteed in, before, during, after or related to anything resulting from any such edits/customizations.

No support is provided on any of these extra customizations. Any of the steps mentioned in any of these extra custom edits may change at any time depending on newer versions of the plugins being released. Any use or customization of anything, beyond what is provided by default inside the plugin admin menu, means you are proceeding at your own risk and that you accept 100% responsibility and liability for everything you change or modify in any manner in the plugin. Your purchase and use of any PluginBuddy plugin implies and shows that you are buying and using PluginBuddy plugin(s) the way it(they) came in their original unmodified form, with no exceptions.

*Remember:
**[http://pluginbuddy.com/purchase/backupbuddy/ Make a backup of your entire site with BackupBuddy] before making any edits!
** PluginBuddy only supports the official unedited, unmodified versions of all PluginBuddy plugins.
** Use a good text editor to make any file changes. Again, maintain backups!
** Any changes you make to files WILL MOST PROBABLY be lost when the plugin is upgraded to any newer version.
** You are 100% responsible and liable for anything resulting from any of these changes.
** No support is provided nor guaranteed on any of these extra changes in any form or shape, whatsoever, regardless of who suggested these custom edits or suggestions.
** Any extra customization info or suggestion is added voluntarily by PluginBuddy staff to help users as much as possible, even if such customization is outside the scope of any membership support.
** Whether a PluginBuddy staff or representative offered or suggested the edit/customization, another customer or anyone else, PluginBuddy does not officially support nor provide any official support on any such edits.
** We cannot guarantee providing any support on any edits or customization tips we provide.
** Absolutely no support is guaranteed in any manner on any of our free plugins, whether or not there is any customization/edit involved.

=External Plugins Compatibility=

PluginBuddy does not promise, guarantee or provide support for any compatibility with any external plugin. If any PluginBuddy Plugin works without any problems when used with any external plugin in question, that means the PluginBuddy Plugin is most probably working without any issues overall. PluginBuddy is not responsible for making PluginBuddy plugins work in any manner, whether custom, fully, fixed or other, with any external non-PluginBuddy plugins. PluginBuddy is also not responsible for providing any support whatsoever for any external plugin, whether or not such an external plugin is used along with any PluginBuddy plugin.

=Free Plugins=

Free plugins are provided as is. There is no guaranteed support that comes with them. Guaranteed support is limited only and mainly for our premium unmodified plugins.

=Bugs, Features and ETA on new updates=

With every new release of any plugin, there may be a new bug or two. You may also want to have new features added to specific plugins. All existing versions of all plugins can have bugs reported OR new features suggested. All of this is done via the [http://ithemes.com/forum official forums].

New updates are also usually released regularly and at the same time, at very different paces, depending on the current number of bugs, features, new plans and tasks at hand. Therefore it is the official policy that there is NO pre-defined ETA on any bug fix, feature imeplemention OR new update OR new plugin roll-out UNLESS otherwise specified specifically in writing somewhere by an official iThemes employee.

==Bugs, bug reports and bug fixes==

Bug reports are filed and noted as they are encountered (thanks for reporting them to us!). There is never any ETA on any bug fixes unless otherwise noted.

==Feature Requests==

Feature requests and feature suggestions are basically future suggested features that users can suggest, and/or future features PluginBuddy may consider adding to the future versions of the plugin(s) in question (again, thanks for suggesting new features!).

There is no guaranteed ETA on when such feature requests will be implemented, unless otherwise noted. All suggested features are just that: suggestions. They remain suggestions until they're confirmed as officially in the works and to be included. Even then, unless a feature is actually rolled out publicly, there is no guarantee any feature suggestion will be implemented. We do our best to try and accommodate as many feature suggestions as possible.

Also, there is no guarantee that any feature request suggested will be implemented, unless otherwise noted.

==ETA on new updates==

Just like bug fixes and new features, there is never a guaranteed date nor a guaranteed time frame on when new updates will roll out. We work every single day of the week, all the time, on our plugins and thus every day there is something new and improved happening in almost all our plugins daily. Whenever we are ready to release any new updates publicly, you'll find out by seeing the plugin update notice in your WordPress OR in your [http://ithemes.com/member/member.php Member's area].

=What does BETA mean?=

Some of PluginBuddy plugins may be in Beta status OR may have Beta features. BETA simply means that some feature or specific part of the plugin is currently still in testing mode, and can cause issues if not used properly. All BETA plugins/features are not yet 100% stable, and thus should NOT be relied on to be working properly OR working at all. Throughout the iThemes Codex, any time the word "Beta" is used in any form, it refers to Beta plugins, Beta features, Beta status and/or anything related to the Beta nature that is officially announced or mentioned as such by any iThemes staff or on any of the Plugin pages, or in this Codex.

Beta implies that any new features or plugins are very close to being released as 100% working very soon, and that there may still be some issues to fix or test more before removing the Beta status. Since no single software of any kind can be tested under every system and site configuration in the world, the Beta status enables the Beta features to be tested out by as many people on as many different websites and configurations as possible.

*Some points to keep in mind when using any BETA plugin/feature:
**1 : Make [http://pluginbuddy.com/purchase/backupbuddy/ FULL WordPress backups] before using ANY beta feature.
**2 : Beta means that the current software feature is NOT complete, and that you are NOT forced to use such a feature at all. You are advised to WAIT until the BETA status is removed.
**3 : Using any Beta feature of any kind, whether it is an entire plugin or something inside a plugin, means and shows that you are fully accepting any liability for any risks involved.
**4 : Using any Beta feature of any kind, whether it is an entire plugin or something inside a plugin, means and shows that you are fully aware that there are all different kinds of risks involved with such features.
**5 : If you are concerned about your important data or anything bad that might happen as a result of using any Beta feature, do NOT use such Beta features.
**6 : ALWAYS make full [http://pluginbuddy.com/purchase/backupbuddy/ BackupBuddy Backups of all your important data] before using any Beta software, whether that Beta software is from PluginBuddy or from any other place.
**7 : If any issues are found in Beta, they are usually added to the list of bug fixes to be released as a whole, or for the next big update, instead of being updated OR fixed individually on a case by case basis.
**8 : Beta features are recommended to test and play with on test sites/servers and configurations with any dummy data, as long as you have [http://pluginbuddy.com/purchase/backupbuddy/ full backups of all important data] still.
**9 : iThemes is not liable nor cannot be held accountable for any unwanted results resulting from the use of BETA features.
**10 : The very name and nature of BETA shows clearly, without any doubt, that there will most probably be issues and problems involved when such labeled features are used anywhere.
**11 : Support for Beta features may be very limited. We usually simply collect all reports related to Beta features and collect them all for one big update in the future.
**12 : If you lose any important data or settings anywhere, or encounter damaged data or settings anywhere, because of any Beta feature, we will not be able to help you and will simply tell you to revert to your previous [http://pluginbuddy.com/purchase/backupbuddy/ backups]. We will also tell you to always wait for BETA status to be removed before using any such features.

If you do not fully understand what Beta means, OR are not willing to fully accept and be fully liable for any risks involved because of using such Beta software, you should NOT use the Beta software in any manner. In such a case, you should simply wait until the Beta status is removed.

*[http://pluginbuddy.com/what-does-beta-mean/ Blog post announcing what BETA means]

=PluginBuddy Licenses=

==Plugin Conflicts==

Some times, external plugins may cause issues in detaching, deleting, generating OR saving license keys. Such plugins may also cause issues when you want to manually or automatically upgrade plugins when you try to solve licensing issues.

Following is a list of currently known plugins which cause license detaching, deleting, generating OR saving issues. Please disable the following plugins, even temporarily, while you perform all the steps of manually OR automatically upgrading the PluginBuddy plugins in question, and detaching, deleting, generating and saving license keys for them. Keep such plugins disabled UNTIL all license key issues are gone OR at least while you perform these steps.

*Plugins causing PluginBuddy licensing issues
**'''W3 Total Cache or WP Super Cache :''' If you are using any caching plugin like '''W3 Total Cache''' or '''WP Super Cache''', please disable it temporarily and then carry out any required steps. You can re-enable the plugin in the end after everything works in terms of the licenses.
***Fix: Follow the above steps to fix this issue. [http://ithemes.com/forum/index.php?/topic/19436-backupbuddy-license-issue/#p92171 Steps also explained by BackupBuddy customer Laura (thanks!)]
**'''Any other CACHING or related plugin:''' Try disabling such plugins, performing the required steps, and then re-activating the Caching or related plugins in question.

*Related Links
**1 : [http://ithemes.com/forum/topic/23481-license-issue-pluginbuddy-developer-to-backupbuddy-both-unlimited/page__view__findpost__p__110368 Disabling W3 Total Cache modules allowed Greg to license BackupBuddy without any issues]
**2 : [http://ithemes.com/forum/topic/23275-unable-to-get-license-to-stick/page__pid__109503#entry109503 W3 Total Cache causing licenses to be deleted after a while]
**3 : [http://ithemes.com/forum/topic/22964-cant-find-stylesheet-to-make-adjustments-to-slider/page__view__findpost__p__107933 W3 Total Cache not allowing licenses to be saved properly]
**4 : [http://ithemes.com/forum/topic/22859-bub-licenses-not-taking-effect/page__view__findpost__p__107476 W3 Total Cache not allowing licenses to be saved - easy solution!]
**5 : [http://ithemes.com/forum/index.php?/topic/19079-wont-let-me-set-a-license-key/#p91663 W3 Total Cache plugin conflict and solution]
**6 : [http://ithemes.com/forum/index.php?/topic/19436-backupbuddy-license-issue/#p92171 W3 Total Cache plugin conflict and solution]
**7 : [http://ithemes.com/forum/index.php?/topic/20228-key-does-not-work/#p95697 W3 Total Cache plugin conflict and solution]
**8 : [http://ithemes.com/forum/index.php?/topic/19041-license-problem-causes-loss-of-all-bb-settings-way-to-get-them-back/ WP Super Cache conflict and solution]

==Licensing Issues==

There are some reports that some users have issues with their license insides the Licenses area of different PluginBuddy plugins, including BackupBuddy.

Remember: All your PluginBuddy plugins, including BackupBuddy, will CONTINUE WORKING PERFECTLY even with these licensing issues. You can keep using the plugins exactly how you want them even during these licensing issues. Your plugins are NOT affected by this licensing situation in any manner.

Your membership is also completely fine and you have NOT lost any license(s). The issue is happening to some customers who simply need to upgrade manually to the latest version of their plugin, if the automatic upgrade does not work.

*Plugins with the update versions which remove this issue completely
**ALL PluginBuddy Products

*You can upgrade via one of the following:
**Automatically upgrade to the latest version
**Manually update by downloading the latest zip version of your PluginBuddy plugin from your Member's panel and then
***Overwrite your existing plugin directory via FTP with the new files.
***De-activate the existing plugin, delete it via your '''WordPress --> Plugins''' area and then upload the newly downloaded zip file. Then re-activate the plugin.
**That will remove the issue completely.
*DETACH the key and then RE-ATTACH the license key for the specific site in question IF licensing still shows issues AFTER manually upgrading to the latest version of the plugin in question (check your Member's area for the latest version download)
*Also make sure to DETACH the key, DELETE that same AND any other keys related to that specific site from the entire licenses area, and then GENERATE a new key for that site IF detaching and re-attaching the license key does not work AFTER manually upgrading (for example, manually upgrading to the latest BackupBuddy version - all plugins have their own latest version numbers - check your Member's area for the latest version download)

[http://ithemes.com/forum/index.php?/topic/6691-read-this-first-pluginbuddy-licensing-issues/page-2/#p85977 First reports]

PluginBuddy

2012-02-06T20:45:29Z

Bes: Added http://ithemes.com/forum/topic/23275-unable-to-get-license-to-stick/page__pid__109503#entry109503 example /* Plugin Conflicts */

Welcome to the PluginBuddy Knowledge Base - Tutorials, Technical Information, Debugging Information, and more.

=Premium Plugins=
* [[Ajax-Edit-Comments]]
* [[BackupBuddy]]
* DisplayBuddy
** [[Accordion]]
** [[Billboard]]
** [[Carousel]]
** [[CopiousComments]]
** [[FeaturedPosts]]
** [[Rotating Images]]
** [[RotatingText]]
** [[Slideshow]]
** [[Tipsy]]
** [[VideoShowcase]]
* [[EmailBuddy]]
* [[Frolick]]
* [[LoopBuddy]]
* [[Mobile]]
* [[TailoredLogin]]
* [[ThumbsUp]]
* [[VidEmbed]]

=Free Plugins (active)=
* [[Featured Text]]
* [[PB-Tweet]]
* [[ServerBuddy]]
* [[Tabber Widget]]
* [[ThemeMan]]
* [[S3 URLS]]
* [[YOURLS]]
* [[ContactBuddy]]

=Free Plugins (inactive)=
* [[WP Easy Uploader]]
* [[WP Developer Assistant]]
* [[Easy Theme and Plugin Updater]]
* [[Current Date & Time Widget]]

''[[:Category:PluginBuddy|View all PluginBuddy Wiki Pages]]''

=Misc. Documentation=
==Frequently Asked (Plugin) Questions==
*[[General Plugins FAQ]]

==License Manager Tutorial and Information==
*[[License Manager]]
==PHP Development & Advanced==
*[[.htaccess]]
*[[PHP]]
*[[Arrays]]

[[Category:PluginBuddy]]

=Translations (localization / internationalization)=

Many PluginBuddy plugins come with translation capability. That means such PluginBuddy plugins can be translated (aka localized) to other languages.

===How Translations Work===

PluginBuddy provides the capability to have a translation in such plugins. Anyone wanting to enhance PluginBuddy with specific language translations can do so voluntarily via Translation Files. Translation Files are simply language files created fully and solely by the volunteer community which use the already built in translation-capable features in many of the PluginBuddy plugins to allow such plugins to show text or outputs in different languages. Making PluginBuddy translation-capable is done by PluginBuddy. Creating, updating and sending in any language specific translation files to PluginBuddy is done by the volunteer community.

Anyone can create translation files, package them into the proper format and give PluginBuddy the final translated files that we will try to include in the next update for the plugin in question. We call such awesome people, who create or update the translation files and send us the full translation package files, '''Awesome Translator Volunteers''', and we are really thankful that they take the time to do such an awesome thing.

If you want to help us, you can translate any existing PluginBuddy plugin which supports internationalization (another way of saying localization or translation-capable) and then, once you're fully done, simply let us know in the forums the link to the final language files that we can directly save and simply try to include in any future updates for the plugin(s) in question.

===Tips on how to localize any PluginBuddy Plugin to any non-English language===

The following 9 tips can help you figure out how to approach translations, how to create translations, and how to send us the final translated file for any translation-capable PluginBuddy plugin:

*1 : Many of the PluginBuddy plugins are internationalized, meaning they have the capability to be translated, via actual external translation files, by any non-iThemes-staff Awesome Translator Volunteer who wishes such plugins to be translated to their language.
*2 : If a PluginBuddy plugin is currently not internationalized or you're not sure if it is, you can ask us in the [http://ithemes.com/forum Support Forums] and we'll let you know, or we'll have it included as a future translation feature request. After the translation capability is added to such a plugin, you can submit the actual translation file. Please remember though: we cannot help with creating, understanding or making any language translation files. Our Awesome Translator Volunteers do that voluntarily (you can too! keep on reading) and fully on their own.
*3 : There are MANY resources which teach you how to create and work with WordPress language files. Following are the official 3 directly by the WordPress community:
**1 : [http://codex.wordpress.org/WordPress_in_Your_Language WordPress in Your Language]
**2 : [http://codex.wordpress.org/Translating_WordPress Translating WordPress]
**3 : [http://codex.wordpress.org/I18n_for_WordPress_Developers What WordPress Localization in Plugins is mainly about]
*4 : Translations are sent in from volunteers from all over the world. As a courtesy, we sometimes package the actual language translation files (provided directly by the Awesome Translator Volunteers) in with the final product. If some translation is not included in the actual plugin even when the plugin has the capability to be translated, you can submit the final translation to us for consideration in the next update by posting on our forums OR you can include the translation in your own live or local WordPress install directly for your own use. More info on how to include your own language specific file for your own WordPress sites is in the resources listed in #3 above.
*5 : A translation included in with the final product does not guarantee the accuracy or quality of the translation. These files are from the Awesome Translator Volunteers, and correction of these files is also done by those Awesome Translator Volunteers.
*6 : If a translation is very inaccurate or incomplete, we can put out a request for a new translation from the volunteer community, or remove the translation from the packaged and final product. You can also let us know of any inaccuracies in any existing translation files by the Awesome Volunteers by providing us with the corrected final files. Please remember: we only accept final and full translation files that you yourself have already created or packaged properly. If you let us know only of the actual inaccuracies without providing the final correct files, we cannot make such changes ourselves to the translation files.
*7 : Unfortunately, PluginBuddy cannot work on, help with, create, nor make any updates to any specific translation files you may have, or may be working on, or want to work on. Our Awesome Volunteers do that and simply give us the final files for inclusion or consideration.
*8 : If you have corrections for any existing translation in form of final proper format translation files for an existing language, OR want to provide the final and proper translation files for a new language, please post a new thread in the appropriate product category in the [http://ithemes.com/forum/ PluginBuddy Support Forums] with the final translations files. If you have any support questions on how to create or make language specific translation files, or how translation files work, you can do so on the [http://wordpress.org/support/ WordPress forums], as such support questions are outside the scope of what PluginBuddy support guarantees with your iThemes membership.
*9 : Any final translation file provided by you (or any other Awesome Volunteer) on the support forums will then be saved and filed as a future enhancement request for the future updates of the plugin(s) in question. In your support forum thread, where you share the final complete translation files you inclusion, you can upload your files directly to the forums OR upload them somewhere and link to them in your support forum thread. We will then download and save such files. Remember please: we cannot guarantee looking inside such files or verifying that they are correct in any manner (because of so many languages in the world and so many possible language files everywhere).

Thank you SO MUCH for being interested in providing translation files for our PluginBuddy plugins. We hope you will become one of our Awesome Translator Volunteers, in addition to being our AWESOME CUSTOMER, and create/update any language-specific translation file package and provide it to us so that we can consider including it in future updates.

===Resources for understanding, creating, updating and submitting final translation files===
*Here are the 3 official resources again which you can use to create, update, start work on and finish translation on any of the translation-capable PluginBuddy plugins:
**1 : [http://codex.wordpress.org/WordPress_in_Your_Language WordPress in Your Language]
**2 : [http://codex.wordpress.org/Translating_WordPress Translating WordPress]
**3 : [http://codex.wordpress.org/I18n_for_WordPress_Developers What WordPress Localization in Plugins is mainly about]

=Extra Customizations=
While any extra customization of any PluginBuddy Plugin is beyond the scope of the official support, we do from time to time offer different tips and tutorials on editing the awesome PluginBuddy plugins to better fit your individual needs. All such edits are, however, beyond what is officially supported and provided in the actual plugin admin panel and officially stated features on the individual plugin pages. No official support is provided nor guaranteed in, before, during, after or related to anything resulting from any such edits/customizations.

No support is provided on any of these extra customizations. Any of the steps mentioned in any of these extra custom edits may change at any time depending on newer versions of the plugins being released. Any use or customization of anything, beyond what is provided by default inside the plugin admin menu, means you are proceeding at your own risk and that you accept 100% responsibility and liability for everything you change or modify in any manner in the plugin. Your purchase and use of any PluginBuddy plugin implies and shows that you are buying and using PluginBuddy plugin(s) the way it(they) came in their original unmodified form, with no exceptions.

*Remember:
**[http://pluginbuddy.com/purchase/backupbuddy/ Make a backup of your entire site with BackupBuddy] before making any edits!
** PluginBuddy only supports the official unedited, unmodified versions of all PluginBuddy plugins.
** Use a good text editor to make any file changes. Again, maintain backups!
** Any changes you make to files WILL MOST PROBABLY be lost when the plugin is upgraded to any newer version.
** You are 100% responsible and liable for anything resulting from any of these changes.
** No support is provided nor guaranteed on any of these extra changes in any form or shape, whatsoever, regardless of who suggested these custom edits or suggestions.
** Any extra customization info or suggestion is added voluntarily by PluginBuddy staff to help users as much as possible, even if such customization is outside the scope of any membership support.
** Whether a PluginBuddy staff or representative offered or suggested the edit/customization, another customer or anyone else, PluginBuddy does not officially support nor provide any official support on any such edits.
** We cannot guarantee providing any support on any edits or customization tips we provide.
** Absolutely no support is guaranteed in any manner on any of our free plugins, whether or not there is any customization/edit involved.

=External Plugins Compatibility=

PluginBuddy does not promise, guarantee or provide support for any compatibility with any external plugin. If any PluginBuddy Plugin works without any problems when used with any external plugin in question, that means the PluginBuddy Plugin is most probably working without any issues overall. PluginBuddy is not responsible for making PluginBuddy plugins work in any manner, whether custom, fully, fixed or other, with any external non-PluginBuddy plugins. PluginBuddy is also not responsible for providing any support whatsoever for any external plugin, whether or not such an external plugin is used along with any PluginBuddy plugin.

=Free Plugins=

Free plugins are provided as is. There is no guaranteed support that comes with them. Guaranteed support is limited only and mainly for our premium unmodified plugins.

=Bugs, Features and ETA on new updates=

With every new release of any plugin, there may be a new bug or two. You may also want to have new features added to specific plugins. All existing versions of all plugins can have bugs reported OR new features suggested. All of this is done via the [http://ithemes.com/forum official forums].

New updates are also usually released regularly and at the same time, at very different paces, depending on the current number of bugs, features, new plans and tasks at hand. Therefore it is the official policy that there is NO pre-defined ETA on any bug fix, feature imeplemention OR new update OR new plugin roll-out UNLESS otherwise specified specifically in writing somewhere by an official iThemes employee.

==Bugs, bug reports and bug fixes==

Bug reports are filed and noted as they are encountered (thanks for reporting them to us!). There is never any ETA on any bug fixes unless otherwise noted.

==Feature Requests==

Feature requests and feature suggestions are basically future suggested features that users can suggest, and/or future features PluginBuddy may consider adding to the future versions of the plugin(s) in question (again, thanks for suggesting new features!).

There is no guaranteed ETA on when such feature requests will be implemented, unless otherwise noted. All suggested features are just that: suggestions. They remain suggestions until they're confirmed as officially in the works and to be included. Even then, unless a feature is actually rolled out publicly, there is no guarantee any feature suggestion will be implemented. We do our best to try and accommodate as many feature suggestions as possible.

Also, there is no guarantee that any feature request suggested will be implemented, unless otherwise noted.

==ETA on new updates==

Just like bug fixes and new features, there is never a guaranteed date nor a guaranteed time frame on when new updates will roll out. We work every single day of the week, all the time, on our plugins and thus every day there is something new and improved happening in almost all our plugins daily. Whenever we are ready to release any new updates publicly, you'll find out by seeing the plugin update notice in your WordPress OR in your [http://ithemes.com/member/member.php Member's area].

=What does BETA mean?=

Some of PluginBuddy plugins may be in Beta status OR may have Beta features. BETA simply means that some feature or specific part of the plugin is currently still in testing mode, and can cause issues if not used properly. All BETA plugins/features are not yet 100% stable, and thus should NOT be relied on to be working properly OR working at all. Throughout the iThemes Codex, any time the word "Beta" is used in any form, it refers to Beta plugins, Beta features, Beta status and/or anything related to the Beta nature that is officially announced or mentioned as such by any iThemes staff or on any of the Plugin pages, or in this Codex.

Beta implies that any new features or plugins are very close to being released as 100% working very soon, and that there may still be some issues to fix or test more before removing the Beta status. Since no single software of any kind can be tested under every system and site configuration in the world, the Beta status enables the Beta features to be tested out by as many people on as many different websites and configurations as possible.

*Some points to keep in mind when using any BETA plugin/feature:
**1 : Make [http://pluginbuddy.com/purchase/backupbuddy/ FULL WordPress backups] before using ANY beta feature.
**2 : Beta means that the current software feature is NOT complete, and that you are NOT forced to use such a feature at all. You are advised to WAIT until the BETA status is removed.
**3 : Using any Beta feature of any kind, whether it is an entire plugin or something inside a plugin, means and shows that you are fully accepting any liability for any risks involved.
**4 : Using any Beta feature of any kind, whether it is an entire plugin or something inside a plugin, means and shows that you are fully aware that there are all different kinds of risks involved with such features.
**5 : If you are concerned about your important data or anything bad that might happen as a result of using any Beta feature, do NOT use such Beta features.
**6 : ALWAYS make full [http://pluginbuddy.com/purchase/backupbuddy/ BackupBuddy Backups of all your important data] before using any Beta software, whether that Beta software is from PluginBuddy or from any other place.
**7 : If any issues are found in Beta, they are usually added to the list of bug fixes to be released as a whole, or for the next big update, instead of being updated OR fixed individually on a case by case basis.
**8 : Beta features are recommended to test and play with on test sites/servers and configurations with any dummy data, as long as you have [http://pluginbuddy.com/purchase/backupbuddy/ full backups of all important data] still.
**9 : iThemes is not liable nor cannot be held accountable for any unwanted results resulting from the use of BETA features.
**10 : The very name and nature of BETA shows clearly, without any doubt, that there will most probably be issues and problems involved when such labeled features are used anywhere.
**11 : Support for Beta features may be very limited. We usually simply collect all reports related to Beta features and collect them all for one big update in the future.
**12 : If you lose any important data or settings anywhere, or encounter damaged data or settings anywhere, because of any Beta feature, we will not be able to help you and will simply tell you to revert to your previous [http://pluginbuddy.com/purchase/backupbuddy/ backups]. We will also tell you to always wait for BETA status to be removed before using any such features.

If you do not fully understand what Beta means, OR are not willing to fully accept and be fully liable for any risks involved because of using such Beta software, you should NOT use the Beta software in any manner. In such a case, you should simply wait until the Beta status is removed.

*[http://pluginbuddy.com/what-does-beta-mean/ Blog post announcing what BETA means]

=PluginBuddy Licenses=

==Plugin Conflicts==

Some times, external plugins may cause issues in detaching, deleting, generating OR saving license keys. Such plugins may also cause issues when you want to manually or automatically upgrade plugins when you try to solve licensing issues.

Following is a list of currently known plugins which cause license detaching, deleting, generating OR saving issues. Please disable the following plugins, even temporarily, while you perform all the steps of manually OR automatically upgrading the PluginBuddy plugins in question, and detaching, deleting, generating and saving license keys for them. Keep such plugins disabled UNTIL all license key issues are gone OR at least while you perform these steps.

*Plugins causing PluginBuddy licensing issues
**'''W3 Total Cache or WP Super Cache :''' If you are using any caching plugin like '''W3 Total Cache''' or '''WP Super Cache''', please disable it temporarily and then carry out any required steps. You can re-enable the plugin in the end after everything works in terms of the licenses.
***Fix: Follow the above steps to fix this issue. [http://ithemes.com/forum/index.php?/topic/19436-backupbuddy-license-issue/#p92171 Steps also explained by BackupBuddy customer Laura (thanks!)]
**'''Any other CACHING or related plugin:''' Try disabling such plugins, performing the required steps, and then re-activating the Caching or related plugins in question.

*Related Links
**1 : [http://ithemes.com/forum/topic/23275-unable-to-get-license-to-stick/page__pid__109503#entry109503 W3 Total Cache causing licenses to be deleted after a while]
**2 : [http://ithemes.com/forum/topic/22964-cant-find-stylesheet-to-make-adjustments-to-slider/page__view__findpost__p__107933 W3 Total Cache not allowing licenses to be saved properly]
**3 : [http://ithemes.com/forum/topic/22859-bub-licenses-not-taking-effect/page__view__findpost__p__107476 W3 Total Cache not allowing licenses to be saved - easy solution!]
**4 : [http://ithemes.com/forum/index.php?/topic/19079-wont-let-me-set-a-license-key/#p91663 W3 Total Cache plugin conflict and solution]
**5 : [http://ithemes.com/forum/index.php?/topic/19436-backupbuddy-license-issue/#p92171 W3 Total Cache plugin conflict and solution]
**6 : [http://ithemes.com/forum/index.php?/topic/20228-key-does-not-work/#p95697 W3 Total Cache plugin conflict and solution]
**7 : [http://ithemes.com/forum/index.php?/topic/19041-license-problem-causes-loss-of-all-bb-settings-way-to-get-them-back/ WP Super Cache conflict and solution]

==Licensing Issues==

There are some reports that some users have issues with their license insides the Licenses area of different PluginBuddy plugins, including BackupBuddy.

Remember: All your PluginBuddy plugins, including BackupBuddy, will CONTINUE WORKING PERFECTLY even with these licensing issues. You can keep using the plugins exactly how you want them even during these licensing issues. Your plugins are NOT affected by this licensing situation in any manner.

Your membership is also completely fine and you have NOT lost any license(s). The issue is happening to some customers who simply need to upgrade manually to the latest version of their plugin, if the automatic upgrade does not work.

*Plugins with the update versions which remove this issue completely
**ALL PluginBuddy Products

*You can upgrade via one of the following:
**Automatically upgrade to the latest version
**Manually update by downloading the latest zip version of your PluginBuddy plugin from your Member's panel and then
***Overwrite your existing plugin directory via FTP with the new files.
***De-activate the existing plugin, delete it via your '''WordPress --> Plugins''' area and then upload the newly downloaded zip file. Then re-activate the plugin.
**That will remove the issue completely.
*DETACH the key and then RE-ATTACH the license key for the specific site in question IF licensing still shows issues AFTER manually upgrading to the latest version of the plugin in question (check your Member's area for the latest version download)
*Also make sure to DETACH the key, DELETE that same AND any other keys related to that specific site from the entire licenses area, and then GENERATE a new key for that site IF detaching and re-attaching the license key does not work AFTER manually upgrading (for example, manually upgrading to the latest BackupBuddy version - all plugins have their own latest version numbers - check your Member's area for the latest version download)

[http://ithemes.com/forum/index.php?/topic/6691-read-this-first-pluginbuddy-licensing-issues/page-2/#p85977 First reports]

Installing BackupBuddy

2012-02-06T17:57:59Z

Bes: Simplified the installation info of BackupBuddy on Multisite /* Multisite */

BackupBuddy can be uploaded, activated and used just like any other plugin. While BackupBuddy can back up both Standalone sites and Multisite installations, it is normally activated differently (<strong>strong recommended!</strong>) on a Multisite network.

*<strong> Remember:</strong>
**'''STANDALONE SITES''' are individual WordPress installations that are not part of a Multisite Network.
**'''MULTISITE NETWORKS''' refers to the entire Multisite Network installation. Within a Network there are both individual site admin panels as well as a Network Admin panel which controls the overall network and allows you manage global settings.
**'''MULTISITE SITES (or subsites)''' refer to INDIVIDUAL SITES inside a MULTISITE. This includes the main base site of a network.
**The term MULTISITE is used loosely by WordPress to refer to EITHER Multisite Networks OR Multisite Sites OR both. We will try to be as specific as possible for any explanations.
*[http://codex.wordpress.org/Tools_Network_SubPanel Detailed info on what Multisite is]

=Standalone Sites=

Standalone Sites are any WordPress sites where Multisite is NOT activated nor used in any manner.

===Upload BackupBuddy on Standalone Site===
*You can upload BackupBuddy on any Standalone (non-Multisite) site just like any other plugin.
**You can use cPanel to upload the plugin to wp-content/plugins directory and then extract it.
**You can extract the BackupBuddy zip file on your computer and then uplaod the BackupBuddy folder via FTP to your wp-content/plugins directory.
**You can use the '''WordPress --> Plugins --> Add New --> Upload''' feature to upload the zip file.

===Activate BackupBuddy on Standalone Site===
*You can activate BackupBuddy like any other plugin.
**Visit your '''WordPress --> Plugins''' area.
**Activate BackupBuddy.

BackupBuddy is now installed and ready to use on your Standalone site. Congratulations!

=Multisite=

Installing BackupBuddy on Multisite is different than installing BackupBuddy on Standalone (non-Multisite) sites.

*[http://ithemes.com/forum/index.php?/topic/18346-backup-buddy-ms-installation/#p86151 MORE INFO ON WHETHER TO GO WITH SINGLE SITE ACTIVATE OR NETWORK ACTIVATE ON MULTISITES]

===Upload BackupBuddy on Multisite===
*When it comes to Multisite, you upload BackupBuddy as if it were any other plugin being uploaded to Multisite.
**You can use cPanel to upload the plugin to wp-content/plugins directory and then extract it.
**You can extract the BackupBuddy zip file on your computer and then uplaod the BackupBuddy folder via FTP to your wp-content/plugins directory.
**You can use the '''WordPress --> Plugins --> Add New --> Upload''' feature to upload the zip file. '''This will ONLY work when you're logged in as the Network Administrator on the top Network site.'''

===Activating BackupBuddy on Multisite===
*Activating BackupBuddy on Multisite is different than activating BackupBuddy on Standalone Sites.
*There is only one official way to install BackupBuddy on a Multisite, which is the <strong>NETWORK ACTIVATE method.</strong>
**<strong>NETWORK ACTIVATE Method:</strong>
***Log into the '''main site's Network Admin''' login area '''as a Network Administrator'''.
***Go to '''WordPress --> Plugins''' area.
***Click the "'''Network Activate'''" link under BackupBuddy on the Plugins page.
****This will enable BackupBuddy for all sites in the Network.
****This will allow ONLY the TOP NETWORK ADMIN to be able to backup all sites in the Network.
****Each site admin (the user level below NETWORK ADMIN) can still export and backup their own single sites (if enabled).

Your BackupBuddy is now installed and ready to use. Congratulations!

PluginBuddy

2012-01-27T19:54:41Z

Bes: Added another W3 Total Cache example http://ithemes.com/forum/topic/22964-cant-find-stylesheet-to-make-adjustments-to-slider/page__view__findpost__p__107933 /* Plugin Conflicts */

Welcome to the PluginBuddy Knowledge Base - Tutorials, Technical Information, Debugging Information, and more.

=Premium Plugins=
* [[Ajax-Edit-Comments]]
* [[BackupBuddy]]
* DisplayBuddy
** [[Accordion]]
** [[Billboard]]
** [[Carousel]]
** [[CopiousComments]]
** [[FeaturedPosts]]
** [[Rotating Images]]
** [[RotatingText]]
** [[Slideshow]]
** [[Tipsy]]
** [[VideoShowcase]]
* [[EmailBuddy]]
* [[LoopBuddy]]
* [[Mobile]]
* [[TailoredLogin]]
* [[ThumbsUp]]
* [[VidEmbed]]

=Free Plugins (active)=
* [[Featured Text]]
* [[PB-Tweet]]
* [[ServerBuddy]]
* [[Tabber Widget]]
* [[ThemeMan]]
* [[S3 URLS]]
* [[YOURLS]]
* [[ContactBuddy]]

=Free Plugins (inactive)=
* [[WP Easy Uploader]]
* [[WP Developer Assistant]]
* [[Easy Theme and Plugin Updater]]
* [[Current Date & Time Widget]]

''[[:Category:PluginBuddy|View all PluginBuddy Wiki Pages]]''

=Misc. Documentation=
==Frequently Asked (Plugin) Questions==
*[[General Plugins FAQ]]

==License Manager Tutorial and Information==
*[[License Manager]]
==PHP Development & Advanced==
*[[.htaccess]]
*[[PHP]]
*[[Arrays]]

[[Category:PluginBuddy]]

=Translations (localization / internationalization)=

Many PluginBuddy plugins come with translation capability. That means such PluginBuddy plugins can be translated (aka localized) to other languages.

===How Translations Work===

PluginBuddy provides the capability to have a translation in such plugins. Anyone wanting to enhance PluginBuddy with specific language translations can do so voluntarily via Translation Files. Translation Files are simply language files created fully and solely by the volunteer community which use the already built in translation-capable features in many of the PluginBuddy plugins to allow such plugins to show text or outputs in different languages. Making PluginBuddy translation-capable is done by PluginBuddy. Creating, updating and sending in any language specific translation files to PluginBuddy is done by the volunteer community.

Anyone can create translation files, package them into the proper format and give PluginBuddy the final translated files that we will try to include in the next update for the plugin in question. We call such awesome people, who create or update the translation files and send us the full translation package files, '''Awesome Translator Volunteers''', and we are really thankful that they take the time to do such an awesome thing.

If you want to help us, you can translate any existing PluginBuddy plugin which supports internationalization (another way of saying localization or translation-capable) and then, once you're fully done, simply let us know in the forums the link to the final language files that we can directly save and simply try to include in any future updates for the plugin(s) in question.

===Tips on how to localize any PluginBuddy Plugin to any non-English language===

The following 9 tips can help you figure out how to approach translations, how to create translations, and how to send us the final translated file for any translation-capable PluginBuddy plugin:

*1 : Many of the PluginBuddy plugins are internationalized, meaning they have the capability to be translated, via actual external translation files, by any non-iThemes-staff Awesome Translator Volunteer who wishes such plugins to be translated to their language.
*2 : If a PluginBuddy plugin is currently not internationalized or you're not sure if it is, you can ask us in the [http://ithemes.com/forum Support Forums] and we'll let you know, or we'll have it included as a future translation feature request. After the translation capability is added to such a plugin, you can submit the actual translation file. Please remember though: we cannot help with creating, understanding or making any language translation files. Our Awesome Translator Volunteers do that voluntarily (you can too! keep on reading) and fully on their own.
*3 : There are MANY resources which teach you how to create and work with WordPress language files. Following are the official 3 directly by the WordPress community:
**1 : [http://codex.wordpress.org/WordPress_in_Your_Language WordPress in Your Language]
**2 : [http://codex.wordpress.org/Translating_WordPress Translating WordPress]
**3 : [http://codex.wordpress.org/I18n_for_WordPress_Developers What WordPress Localization in Plugins is mainly about]
*4 : Translations are sent in from volunteers from all over the world. As a courtesy, we sometimes package the actual language translation files (provided directly by the Awesome Translator Volunteers) in with the final product. If some translation is not included in the actual plugin even when the plugin has the capability to be translated, you can submit the final translation to us for consideration in the next update by posting on our forums OR you can include the translation in your own live or local WordPress install directly for your own use. More info on how to include your own language specific file for your own WordPress sites is in the resources listed in #3 above.
*5 : A translation included in with the final product does not guarantee the accuracy or quality of the translation. These files are from the Awesome Translator Volunteers, and correction of these files is also done by those Awesome Translator Volunteers.
*6 : If a translation is very inaccurate or incomplete, we can put out a request for a new translation from the volunteer community, or remove the translation from the packaged and final product. You can also let us know of any inaccuracies in any existing translation files by the Awesome Volunteers by providing us with the corrected final files. Please remember: we only accept final and full translation files that you yourself have already created or packaged properly. If you let us know only of the actual inaccuracies without providing the final correct files, we cannot make such changes ourselves to the translation files.
*7 : Unfortunately, PluginBuddy cannot work on, help with, create, nor make any updates to any specific translation files you may have, or may be working on, or want to work on. Our Awesome Volunteers do that and simply give us the final files for inclusion or consideration.
*8 : If you have corrections for any existing translation in form of final proper format translation files for an existing language, OR want to provide the final and proper translation files for a new language, please post a new thread in the appropriate product category in the [http://ithemes.com/forum/ PluginBuddy Support Forums] with the final translations files. If you have any support questions on how to create or make language specific translation files, or how translation files work, you can do so on the [http://wordpress.org/support/ WordPress forums], as such support questions are outside the scope of what PluginBuddy support guarantees with your iThemes membership.
*9 : Any final translation file provided by you (or any other Awesome Volunteer) on the support forums will then be saved and filed as a future enhancement request for the future updates of the plugin(s) in question. In your support forum thread, where you share the final complete translation files you inclusion, you can upload your files directly to the forums OR upload them somewhere and link to them in your support forum thread. We will then download and save such files. Remember please: we cannot guarantee looking inside such files or verifying that they are correct in any manner (because of so many languages in the world and so many possible language files everywhere).

Thank you SO MUCH for being interested in providing translation files for our PluginBuddy plugins. We hope you will become one of our Awesome Translator Volunteers, in addition to being our AWESOME CUSTOMER, and create/update any language-specific translation file package and provide it to us so that we can consider including it in future updates.

===Resources for understanding, creating, updating and submitting final translation files===
*Here are the 3 official resources again which you can use to create, update, start work on and finish translation on any of the translation-capable PluginBuddy plugins:
**1 : [http://codex.wordpress.org/WordPress_in_Your_Language WordPress in Your Language]
**2 : [http://codex.wordpress.org/Translating_WordPress Translating WordPress]
**3 : [http://codex.wordpress.org/I18n_for_WordPress_Developers What WordPress Localization in Plugins is mainly about]

=Extra Customizations=
While any extra customization of any PluginBuddy Plugin is beyond the scope of the official support, we do from time to time offer different tips and tutorials on editing the awesome PluginBuddy plugins to better fit your individual needs. All such edits are, however, beyond what is officially supported and provided in the actual plugin admin panel and officially stated features on the individual plugin pages. No official support is provided nor guaranteed in, before, during, after or related to anything resulting from any such edits/customizations.

No support is provided on any of these extra customizations. Any of the steps mentioned in any of these extra custom edits may change at any time depending on newer versions of the plugins being released. Any use or customization of anything, beyond what is provided by default inside the plugin admin menu, means you are proceeding at your own risk and that you accept 100% responsibility and liability for everything you change or modify in any manner in the plugin. Your purchase and use of any PluginBuddy plugin implies and shows that you are buying and using PluginBuddy plugin(s) the way it(they) came in their original unmodified form, with no exceptions.

*Remember:
**[http://pluginbuddy.com/purchase/backupbuddy/ Make a backup of your entire site with BackupBuddy] before making any edits!
** PluginBuddy only supports the official unedited, unmodified versions of all PluginBuddy plugins.
** Use a good text editor to make any file changes. Again, maintain backups!
** Any changes you make to files WILL MOST PROBABLY be lost when the plugin is upgraded to any newer version.
** You are 100% responsible and liable for anything resulting from any of these changes.
** No support is provided nor guaranteed on any of these extra changes in any form or shape, whatsoever, regardless of who suggested these custom edits or suggestions.
** Any extra customization info or suggestion is added voluntarily by PluginBuddy staff to help users as much as possible, even if such customization is outside the scope of any membership support.
** Whether a PluginBuddy staff or representative offered or suggested the edit/customization, another customer or anyone else, PluginBuddy does not officially support nor provide any official support on any such edits.
** We cannot guarantee providing any support on any edits or customization tips we provide.
** Absolutely no support is guaranteed in any manner on any of our free plugins, whether or not there is any customization/edit involved.

=External Plugins Compatibility=

PluginBuddy does not promise, guarantee or provide support for any compatibility with any external plugin. If any PluginBuddy Plugin works without any problems when used with any external plugin in question, that means the PluginBuddy Plugin is most probably working without any issues overall. PluginBuddy is not responsible for making PluginBuddy plugins work in any manner, whether custom, fully, fixed or other, with any external non-PluginBuddy plugins. PluginBuddy is also not responsible for providing any support whatsoever for any external plugin, whether or not such an external plugin is used along with any PluginBuddy plugin.

=Free Plugins=

Free plugins are provided as is. There is no guaranteed support that comes with them. Guaranteed support is limited only and mainly for our premium unmodified plugins.

=Bugs, Features and ETA on new updates=

With every new release of any plugin, there may be a new bug or two. You may also want to have new features added to specific plugins. All existing versions of all plugins can have bugs reported OR new features suggested. All of this is done via the [http://ithemes.com/forum official forums].

New updates are also usually released regularly and at the same time, at very different paces, depending on the current number of bugs, features, new plans and tasks at hand. Therefore it is the official policy that there is NO pre-defined ETA on any bug fix, feature imeplemention OR new update OR new plugin roll-out UNLESS otherwise specified specifically in writing somewhere by an official iThemes employee.

==Bugs, bug reports and bug fixes==

Bug reports are filed and noted as they are encountered (thanks for reporting them to us!). There is never any ETA on any bug fixes unless otherwise noted.

==Feature Requests==

Feature requests and feature suggestions are basically future suggested features that users can suggest, and/or future features PluginBuddy may consider adding to the future versions of the plugin(s) in question (again, thanks for suggesting new features!).

There is no guaranteed ETA on when such feature requests will be implemented, unless otherwise noted. All suggested features are just that: suggestions. They remain suggestions until they're confirmed as officially in the works and to be included. Even then, unless a feature is actually rolled out publicly, there is no guarantee any feature suggestion will be implemented. We do our best to try and accommodate as many feature suggestions as possible.

Also, there is no guarantee that any feature request suggested will be implemented, unless otherwise noted.

==ETA on new updates==

Just like bug fixes and new features, there is never a guaranteed date nor a guaranteed time frame on when new updates will roll out. We work every single day of the week, all the time, on our plugins and thus every day there is something new and improved happening in almost all our plugins daily. Whenever we are ready to release any new updates publicly, you'll find out by seeing the plugin update notice in your WordPress OR in your [http://ithemes.com/member/member.php Member's area].

=What does BETA mean?=

Some of PluginBuddy plugins may be in Beta status OR may have Beta features. BETA simply means that some feature or specific part of the plugin is currently still in testing mode, and can cause issues if not used properly. All BETA plugins/features are not yet 100% stable, and thus should NOT be relied on to be working properly OR working at all. Throughout the iThemes Codex, any time the word "Beta" is used in any form, it refers to Beta plugins, Beta features, Beta status and/or anything related to the Beta nature that is officially announced or mentioned as such by any iThemes staff or on any of the Plugin pages, or in this Codex.

Beta implies that any new features or plugins are very close to being released as 100% working very soon, and that there may still be some issues to fix or test more before removing the Beta status. Since no single software of any kind can be tested under every system and site configuration in the world, the Beta status enables the Beta features to be tested out by as many people on as many different websites and configurations as possible.

*Some points to keep in mind when using any BETA plugin/feature:
**1 : Make [http://pluginbuddy.com/purchase/backupbuddy/ FULL WordPress backups] before using ANY beta feature.
**2 : Beta means that the current software feature is NOT complete, and that you are NOT forced to use such a feature at all. You are advised to WAIT until the BETA status is removed.
**3 : Using any Beta feature of any kind, whether it is an entire plugin or something inside a plugin, means and shows that you are fully accepting any liability for any risks involved.
**4 : Using any Beta feature of any kind, whether it is an entire plugin or something inside a plugin, means and shows that you are fully aware that there are all different kinds of risks involved with such features.
**5 : If you are concerned about your important data or anything bad that might happen as a result of using any Beta feature, do NOT use such Beta features.
**6 : ALWAYS make full [http://pluginbuddy.com/purchase/backupbuddy/ BackupBuddy Backups of all your important data] before using any Beta software, whether that Beta software is from PluginBuddy or from any other place.
**7 : If any issues are found in Beta, they are usually added to the list of bug fixes to be released as a whole, or for the next big update, instead of being updated OR fixed individually on a case by case basis.
**8 : Beta features are recommended to test and play with on test sites/servers and configurations with any dummy data, as long as you have [http://pluginbuddy.com/purchase/backupbuddy/ full backups of all important data] still.
**9 : iThemes is not liable nor cannot be held accountable for any unwanted results resulting from the use of BETA features.
**10 : The very name and nature of BETA shows clearly, without any doubt, that there will most probably be issues and problems involved when such labeled features are used anywhere.
**11 : Support for Beta features may be very limited. We usually simply collect all reports related to Beta features and collect them all for one big update in the future.
**12 : If you lose any important data or settings anywhere, or encounter damaged data or settings anywhere, because of any Beta feature, we will not be able to help you and will simply tell you to revert to your previous [http://pluginbuddy.com/purchase/backupbuddy/ backups]. We will also tell you to always wait for BETA status to be removed before using any such features.

If you do not fully understand what Beta means, OR are not willing to fully accept and be fully liable for any risks involved because of using such Beta software, you should NOT use the Beta software in any manner. In such a case, you should simply wait until the Beta status is removed.

*[http://pluginbuddy.com/what-does-beta-mean/ Blog post announcing what BETA means]

=PluginBuddy Licenses=

==Plugin Conflicts==

Some times, external plugins may cause issues in detaching, deleting, generating OR saving license keys. Such plugins may also cause issues when you want to manually or automatically upgrade plugins when you try to solve licensing issues.

Following is a list of currently known plugins which cause license detaching, deleting, generating OR saving issues. Please disable the following plugins, even temporarily, while you perform all the steps of manually OR automatically upgrading the PluginBuddy plugins in question, and detaching, deleting, generating and saving license keys for them. Keep such plugins disabled UNTIL all license key issues are gone OR at least while you perform these steps.

*Plugins causing PluginBuddy licensing issues
**'''W3 Total Cache or WP Super Cache :''' If you are using any caching plugin like '''W3 Total Cache''' or '''WP Super Cache''', please disable it temporarily and then carry out any required steps. You can re-enable the plugin in the end after everything works in terms of the licenses.
***Fix: Follow the above steps to fix this issue. [http://ithemes.com/forum/index.php?/topic/19436-backupbuddy-license-issue/#p92171 Steps also explained by BackupBuddy customer Laura (thanks!)]
**'''Any other CACHING or related plugin:''' Try disabling such plugins, performing the required steps, and then re-activating the Caching or related plugins in question.

*Related Links
**1 : [http://ithemes.com/forum/topic/22964-cant-find-stylesheet-to-make-adjustments-to-slider/page__view__findpost__p__107933 W3 Total Cache not allowing licenses to be saved properly]
**2 : [http://ithemes.com/forum/topic/22859-bub-licenses-not-taking-effect/page__view__findpost__p__107476 W3 Total Cache not allowing licenses to be saved - easy solution!]
**3 : [http://ithemes.com/forum/index.php?/topic/19079-wont-let-me-set-a-license-key/#p91663 W3 Total Cache plugin conflict and solution]
**4 : [http://ithemes.com/forum/index.php?/topic/19436-backupbuddy-license-issue/#p92171 W3 Total Cache plugin conflict and solution]
**5 : [http://ithemes.com/forum/index.php?/topic/20228-key-does-not-work/#p95697 W3 Total Cache plugin conflict and solution]
**6 : [http://ithemes.com/forum/index.php?/topic/19041-license-problem-causes-loss-of-all-bb-settings-way-to-get-them-back/ WP Super Cache conflict and solution]

==Licensing Issues==

There are some reports that some users have issues with their license insides the Licenses area of different PluginBuddy plugins, including BackupBuddy.

Remember: All your PluginBuddy plugins, including BackupBuddy, will CONTINUE WORKING PERFECTLY even with these licensing issues. You can keep using the plugins exactly how you want them even during these licensing issues. Your plugins are NOT affected by this licensing situation in any manner.

Your membership is also completely fine and you have NOT lost any license(s). The issue is happening to some customers who simply need to upgrade manually to the latest version of their plugin, if the automatic upgrade does not work.

*Plugins with the update versions which remove this issue completely
**ALL PluginBuddy Products

*You can upgrade via one of the following:
**Automatically upgrade to the latest version
**Manually update by downloading the latest zip version of your PluginBuddy plugin from your Member's panel and then
***Overwrite your existing plugin directory via FTP with the new files.
***De-activate the existing plugin, delete it via your '''WordPress --> Plugins''' area and then upload the newly downloaded zip file. Then re-activate the plugin.
**That will remove the issue completely.
*DETACH the key and then RE-ATTACH the license key for the specific site in question IF licensing still shows issues AFTER manually upgrading to the latest version of the plugin in question (check your Member's area for the latest version download)
*Also make sure to DETACH the key, DELETE that same AND any other keys related to that specific site from the entire licenses area, and then GENERATE a new key for that site IF detaching and re-attaching the license key does not work AFTER manually upgrading (for example, manually upgrading to the latest BackupBuddy version - all plugins have their own latest version numbers - check your Member's area for the latest version download)

[http://ithemes.com/forum/index.php?/topic/6691-read-this-first-pluginbuddy-licensing-issues/page-2/#p85977 First reports]

PluginBuddy

2012-01-25T22:40:35Z

Bes: Added another W3 Total Cache conflict example & solution http://ithemes.com/forum/topic/22859-bub-licenses-not-taking-effect/page__view__findpost__p__107476 /* Plugin Conflicts */

Welcome to the PluginBuddy Knowledge Base - Tutorials, Technical Information, Debugging Information, and more.

=Premium Plugins=
* [[Ajax-Edit-Comments]]
* [[BackupBuddy]]
* DisplayBuddy
** [[Accordion]]
** [[Billboard]]
** [[Carousel]]
** [[CopiousComments]]
** [[FeaturedPosts]]
** [[Rotating Images]]
** [[RotatingText]]
** [[Slideshow]]
** [[Tipsy]]
** [[VideoShowcase]]
* [[EmailBuddy]]
* [[LoopBuddy]]
* [[Mobile]]
* [[TailoredLogin]]
* [[ThumbsUp]]
* [[VidEmbed]]

=Free Plugins (active)=
* [[Featured Text]]
* [[PB-Tweet]]
* [[ServerBuddy]]
* [[Tabber Widget]]
* [[ThemeMan]]
* [[S3 URLS]]
* [[YOURLS]]
* [[ContactBuddy]]

=Free Plugins (inactive)=
* [[WP Easy Uploader]]
* [[WP Developer Assistant]]
* [[Easy Theme and Plugin Updater]]
* [[Current Date & Time Widget]]

''[[:Category:PluginBuddy|View all PluginBuddy Wiki Pages]]''

=Misc. Documentation=
==Frequently Asked (Plugin) Questions==
*[[General Plugins FAQ]]

==License Manager Tutorial and Information==
*[[License Manager]]
==PHP Development & Advanced==
*[[.htaccess]]
*[[PHP]]
*[[Arrays]]

[[Category:PluginBuddy]]

=Translations (localization / internationalization)=

Many PluginBuddy plugins come with translation capability. That means such PluginBuddy plugins can be translated (aka localized) to other languages.

===How Translations Work===

PluginBuddy provides the capability to have a translation in such plugins. Anyone wanting to enhance PluginBuddy with specific language translations can do so voluntarily via Translation Files. Translation Files are simply language files created fully and solely by the volunteer community which use the already built in translation-capable features in many of the PluginBuddy plugins to allow such plugins to show text or outputs in different languages. Making PluginBuddy translation-capable is done by PluginBuddy. Creating, updating and sending in any language specific translation files to PluginBuddy is done by the volunteer community.

Anyone can create translation files, package them into the proper format and give PluginBuddy the final translated files that we will try to include in the next update for the plugin in question. We call such awesome people, who create or update the translation files and send us the full translation package files, '''Awesome Translator Volunteers''', and we are really thankful that they take the time to do such an awesome thing.

If you want to help us, you can translate any existing PluginBuddy plugin which supports internationalization (another way of saying localization or translation-capable) and then, once you're fully done, simply let us know in the forums the link to the final language files that we can directly save and simply try to include in any future updates for the plugin(s) in question.

===Tips on how to localize any PluginBuddy Plugin to any non-English language===

The following 9 tips can help you figure out how to approach translations, how to create translations, and how to send us the final translated file for any translation-capable PluginBuddy plugin:

*1 : Many of the PluginBuddy plugins are internationalized, meaning they have the capability to be translated, via actual external translation files, by any non-iThemes-staff Awesome Translator Volunteer who wishes such plugins to be translated to their language.
*2 : If a PluginBuddy plugin is currently not internationalized or you're not sure if it is, you can ask us in the [http://ithemes.com/forum Support Forums] and we'll let you know, or we'll have it included as a future translation feature request. After the translation capability is added to such a plugin, you can submit the actual translation file. Please remember though: we cannot help with creating, understanding or making any language translation files. Our Awesome Translator Volunteers do that voluntarily (you can too! keep on reading) and fully on their own.
*3 : There are MANY resources which teach you how to create and work with WordPress language files. Following are the official 3 directly by the WordPress community:
**1 : [http://codex.wordpress.org/WordPress_in_Your_Language WordPress in Your Language]
**2 : [http://codex.wordpress.org/Translating_WordPress Translating WordPress]
**3 : [http://codex.wordpress.org/I18n_for_WordPress_Developers What WordPress Localization in Plugins is mainly about]
*4 : Translations are sent in from volunteers from all over the world. As a courtesy, we sometimes package the actual language translation files (provided directly by the Awesome Translator Volunteers) in with the final product. If some translation is not included in the actual plugin even when the plugin has the capability to be translated, you can submit the final translation to us for consideration in the next update by posting on our forums OR you can include the translation in your own live or local WordPress install directly for your own use. More info on how to include your own language specific file for your own WordPress sites is in the resources listed in #3 above.
*5 : A translation included in with the final product does not guarantee the accuracy or quality of the translation. These files are from the Awesome Translator Volunteers, and correction of these files is also done by those Awesome Translator Volunteers.
*6 : If a translation is very inaccurate or incomplete, we can put out a request for a new translation from the volunteer community, or remove the translation from the packaged and final product. You can also let us know of any inaccuracies in any existing translation files by the Awesome Volunteers by providing us with the corrected final files. Please remember: we only accept final and full translation files that you yourself have already created or packaged properly. If you let us know only of the actual inaccuracies without providing the final correct files, we cannot make such changes ourselves to the translation files.
*7 : Unfortunately, PluginBuddy cannot work on, help with, create, nor make any updates to any specific translation files you may have, or may be working on, or want to work on. Our Awesome Volunteers do that and simply give us the final files for inclusion or consideration.
*8 : If you have corrections for any existing translation in form of final proper format translation files for an existing language, OR want to provide the final and proper translation files for a new language, please post a new thread in the appropriate product category in the [http://ithemes.com/forum/ PluginBuddy Support Forums] with the final translations files. If you have any support questions on how to create or make language specific translation files, or how translation files work, you can do so on the [http://wordpress.org/support/ WordPress forums], as such support questions are outside the scope of what PluginBuddy support guarantees with your iThemes membership.
*9 : Any final translation file provided by you (or any other Awesome Volunteer) on the support forums will then be saved and filed as a future enhancement request for the future updates of the plugin(s) in question. In your support forum thread, where you share the final complete translation files you inclusion, you can upload your files directly to the forums OR upload them somewhere and link to them in your support forum thread. We will then download and save such files. Remember please: we cannot guarantee looking inside such files or verifying that they are correct in any manner (because of so many languages in the world and so many possible language files everywhere).

Thank you SO MUCH for being interested in providing translation files for our PluginBuddy plugins. We hope you will become one of our Awesome Translator Volunteers, in addition to being our AWESOME CUSTOMER, and create/update any language-specific translation file package and provide it to us so that we can consider including it in future updates.

===Resources for understanding, creating, updating and submitting final translation files===
*Here are the 3 official resources again which you can use to create, update, start work on and finish translation on any of the translation-capable PluginBuddy plugins:
**1 : [http://codex.wordpress.org/WordPress_in_Your_Language WordPress in Your Language]
**2 : [http://codex.wordpress.org/Translating_WordPress Translating WordPress]
**3 : [http://codex.wordpress.org/I18n_for_WordPress_Developers What WordPress Localization in Plugins is mainly about]

=Extra Customizations=
While any extra customization of any PluginBuddy Plugin is beyond the scope of the official support, we do from time to time offer different tips and tutorials on editing the awesome PluginBuddy plugins to better fit your individual needs. All such edits are, however, beyond what is officially supported and provided in the actual plugin admin panel and officially stated features on the individual plugin pages. No official support is provided nor guaranteed in, before, during, after or related to anything resulting from any such edits/customizations.

No support is provided on any of these extra customizations. Any of the steps mentioned in any of these extra custom edits may change at any time depending on newer versions of the plugins being released. Any use or customization of anything, beyond what is provided by default inside the plugin admin menu, means you are proceeding at your own risk and that you accept 100% responsibility and liability for everything you change or modify in any manner in the plugin. Your purchase and use of any PluginBuddy plugin implies and shows that you are buying and using PluginBuddy plugin(s) the way it(they) came in their original unmodified form, with no exceptions.

*Remember:
**[http://pluginbuddy.com/purchase/backupbuddy/ Make a backup of your entire site with BackupBuddy] before making any edits!
** PluginBuddy only supports the official unedited, unmodified versions of all PluginBuddy plugins.
** Use a good text editor to make any file changes. Again, maintain backups!
** Any changes you make to files WILL MOST PROBABLY be lost when the plugin is upgraded to any newer version.
** You are 100% responsible and liable for anything resulting from any of these changes.
** No support is provided nor guaranteed on any of these extra changes in any form or shape, whatsoever, regardless of who suggested these custom edits or suggestions.
** Any extra customization info or suggestion is added voluntarily by PluginBuddy staff to help users as much as possible, even if such customization is outside the scope of any membership support.
** Whether a PluginBuddy staff or representative offered or suggested the edit/customization, another customer or anyone else, PluginBuddy does not officially support nor provide any official support on any such edits.
** We cannot guarantee providing any support on any edits or customization tips we provide.
** Absolutely no support is guaranteed in any manner on any of our free plugins, whether or not there is any customization/edit involved.

=External Plugins Compatibility=

PluginBuddy does not promise, guarantee or provide support for any compatibility with any external plugin. If any PluginBuddy Plugin works without any problems when used with any external plugin in question, that means the PluginBuddy Plugin is most probably working without any issues overall. PluginBuddy is not responsible for making PluginBuddy plugins work in any manner, whether custom, fully, fixed or other, with any external non-PluginBuddy plugins. PluginBuddy is also not responsible for providing any support whatsoever for any external plugin, whether or not such an external plugin is used along with any PluginBuddy plugin.

=Free Plugins=

Free plugins are provided as is. There is no guaranteed support that comes with them. Guaranteed support is limited only and mainly for our premium unmodified plugins.

=Bugs, Features and ETA on new updates=

With every new release of any plugin, there may be a new bug or two. You may also want to have new features added to specific plugins. All existing versions of all plugins can have bugs reported OR new features suggested. All of this is done via the [http://ithemes.com/forum official forums].

New updates are also usually released regularly and at the same time, at very different paces, depending on the current number of bugs, features, new plans and tasks at hand. Therefore it is the official policy that there is NO pre-defined ETA on any bug fix, feature imeplemention OR new update OR new plugin roll-out UNLESS otherwise specified specifically in writing somewhere by an official iThemes employee.

==Bugs, bug reports and bug fixes==

Bug reports are filed and noted as they are encountered (thanks for reporting them to us!). There is never any ETA on any bug fixes unless otherwise noted.

==Feature Requests==

Feature requests and feature suggestions are basically future suggested features that users can suggest, and/or future features PluginBuddy may consider adding to the future versions of the plugin(s) in question (again, thanks for suggesting new features!).

There is no guaranteed ETA on when such feature requests will be implemented, unless otherwise noted. All suggested features are just that: suggestions. They remain suggestions until they're confirmed as officially in the works and to be included. Even then, unless a feature is actually rolled out publicly, there is no guarantee any feature suggestion will be implemented. We do our best to try and accommodate as many feature suggestions as possible.

Also, there is no guarantee that any feature request suggested will be implemented, unless otherwise noted.

==ETA on new updates==

Just like bug fixes and new features, there is never a guaranteed date nor a guaranteed time frame on when new updates will roll out. We work every single day of the week, all the time, on our plugins and thus every day there is something new and improved happening in almost all our plugins daily. Whenever we are ready to release any new updates publicly, you'll find out by seeing the plugin update notice in your WordPress OR in your [http://ithemes.com/member/member.php Member's area].

=What does BETA mean?=

Some of PluginBuddy plugins may be in Beta status OR may have Beta features. BETA simply means that some feature or specific part of the plugin is currently still in testing mode, and can cause issues if not used properly. All BETA plugins/features are not yet 100% stable, and thus should NOT be relied on to be working properly OR working at all. Throughout the iThemes Codex, any time the word "Beta" is used in any form, it refers to Beta plugins, Beta features, Beta status and/or anything related to the Beta nature that is officially announced or mentioned as such by any iThemes staff or on any of the Plugin pages, or in this Codex.

Beta implies that any new features or plugins are very close to being released as 100% working very soon, and that there may still be some issues to fix or test more before removing the Beta status. Since no single software of any kind can be tested under every system and site configuration in the world, the Beta status enables the Beta features to be tested out by as many people on as many different websites and configurations as possible.

*Some points to keep in mind when using any BETA plugin/feature:
**1 : Make [http://pluginbuddy.com/purchase/backupbuddy/ FULL WordPress backups] before using ANY beta feature.
**2 : Beta means that the current software feature is NOT complete, and that you are NOT forced to use such a feature at all. You are advised to WAIT until the BETA status is removed.
**3 : Using any Beta feature of any kind, whether it is an entire plugin or something inside a plugin, means and shows that you are fully accepting any liability for any risks involved.
**4 : Using any Beta feature of any kind, whether it is an entire plugin or something inside a plugin, means and shows that you are fully aware that there are all different kinds of risks involved with such features.
**5 : If you are concerned about your important data or anything bad that might happen as a result of using any Beta feature, do NOT use such Beta features.
**6 : ALWAYS make full [http://pluginbuddy.com/purchase/backupbuddy/ BackupBuddy Backups of all your important data] before using any Beta software, whether that Beta software is from PluginBuddy or from any other place.
**7 : If any issues are found in Beta, they are usually added to the list of bug fixes to be released as a whole, or for the next big update, instead of being updated OR fixed individually on a case by case basis.
**8 : Beta features are recommended to test and play with on test sites/servers and configurations with any dummy data, as long as you have [http://pluginbuddy.com/purchase/backupbuddy/ full backups of all important data] still.
**9 : iThemes is not liable nor cannot be held accountable for any unwanted results resulting from the use of BETA features.
**10 : The very name and nature of BETA shows clearly, without any doubt, that there will most probably be issues and problems involved when such labeled features are used anywhere.
**11 : Support for Beta features may be very limited. We usually simply collect all reports related to Beta features and collect them all for one big update in the future.
**12 : If you lose any important data or settings anywhere, or encounter damaged data or settings anywhere, because of any Beta feature, we will not be able to help you and will simply tell you to revert to your previous [http://pluginbuddy.com/purchase/backupbuddy/ backups]. We will also tell you to always wait for BETA status to be removed before using any such features.

If you do not fully understand what Beta means, OR are not willing to fully accept and be fully liable for any risks involved because of using such Beta software, you should NOT use the Beta software in any manner. In such a case, you should simply wait until the Beta status is removed.

*[http://pluginbuddy.com/what-does-beta-mean/ Blog post announcing what BETA means]

=PluginBuddy Licenses=

==Plugin Conflicts==

Some times, external plugins may cause issues in detaching, deleting, generating OR saving license keys. Such plugins may also cause issues when you want to manually or automatically upgrade plugins when you try to solve licensing issues.

Following is a list of currently known plugins which cause license detaching, deleting, generating OR saving issues. Please disable the following plugins, even temporarily, while you perform all the steps of manually OR automatically upgrading the PluginBuddy plugins in question, and detaching, deleting, generating and saving license keys for them. Keep such plugins disabled UNTIL all license key issues are gone OR at least while you perform these steps.

*Plugins causing PluginBuddy licensing issues
**'''W3 Total Cache or WP Super Cache :''' If you are using any caching plugin like '''W3 Total Cache''' or '''WP Super Cache''', please disable it temporarily and then carry out any required steps. You can re-enable the plugin in the end after everything works in terms of the licenses.
***Fix: Follow the above steps to fix this issue. [http://ithemes.com/forum/index.php?/topic/19436-backupbuddy-license-issue/#p92171 Steps also explained by BackupBuddy customer Laura (thanks!)]
**'''Any other CACHING or related plugin:''' Try disabling such plugins, performing the required steps, and then re-activating the Caching or related plugins in question.

*Related Links
**1 : [http://ithemes.com/forum/topic/22859-bub-licenses-not-taking-effect/page__view__findpost__p__107476 W3 Total Cache not allowing licenses to be saved - easy solution!]
**2 : [http://ithemes.com/forum/index.php?/topic/19079-wont-let-me-set-a-license-key/#p91663 W3 Total Cache plugin conflict and solution]
**3 : [http://ithemes.com/forum/index.php?/topic/19436-backupbuddy-license-issue/#p92171 W3 Total Cache plugin conflict and solution]
**4 : [http://ithemes.com/forum/index.php?/topic/20228-key-does-not-work/#p95697 W3 Total Cache plugin conflict and solution]
**5 : [http://ithemes.com/forum/index.php?/topic/19041-license-problem-causes-loss-of-all-bb-settings-way-to-get-them-back/ WP Super Cache conflict and solution]

==Licensing Issues==

There are some reports that some users have issues with their license insides the Licenses area of different PluginBuddy plugins, including BackupBuddy.

Remember: All your PluginBuddy plugins, including BackupBuddy, will CONTINUE WORKING PERFECTLY even with these licensing issues. You can keep using the plugins exactly how you want them even during these licensing issues. Your plugins are NOT affected by this licensing situation in any manner.

Your membership is also completely fine and you have NOT lost any license(s). The issue is happening to some customers who simply need to upgrade manually to the latest version of their plugin, if the automatic upgrade does not work.

*Plugins with the update versions which remove this issue completely
**ALL PluginBuddy Products

*You can upgrade via one of the following:
**Automatically upgrade to the latest version
**Manually update by downloading the latest zip version of your PluginBuddy plugin from your Member's panel and then
***Overwrite your existing plugin directory via FTP with the new files.
***De-activate the existing plugin, delete it via your '''WordPress --> Plugins''' area and then upload the newly downloaded zip file. Then re-activate the plugin.
**That will remove the issue completely.
*DETACH the key and then RE-ATTACH the license key for the specific site in question IF licensing still shows issues AFTER manually upgrading to the latest version of the plugin in question (check your Member's area for the latest version download)
*Also make sure to DETACH the key, DELETE that same AND any other keys related to that specific site from the entire licenses area, and then GENERATE a new key for that site IF detaching and re-attaching the license key does not work AFTER manually upgrading (for example, manually upgrading to the latest BackupBuddy version - all plugins have their own latest version numbers - check your Member's area for the latest version download)

[http://ithemes.com/forum/index.php?/topic/6691-read-this-first-pluginbuddy-licensing-issues/page-2/#p85977 First reports]

Talk:BackupBuddy

2012-01-16T22:57:37Z

Bes: /* All support questions on the forums */ new section

Please can someone help. I have followed the instructions and keep geting this error message when I try and start the migration. Parse error: syntax error, unexpected T_DEC, expecting T_STRING or T_VARIABLE or '$' in /home/salesand/public_html/zaarma.com/partners/importbuddy.php on line 1199

'''[http://ithemes.com/forum/forum/74-backupbuddy/ Admin reply: Please post your questions on the forums]'''

== All support questions on the forums ==

'''[http://ithemes.com/forum/forum/74-backupbuddy/ Please post all BackupBuddy support questions on the BackupBuddy Support Forums]'''

Talk:BackupBuddy

2012-01-16T22:55:14Z

Bes: Added link to forums to have all support go there http://ithemes.com/forum/forum/74-backupbuddy/

PluginBuddy

2011-12-02T19:11:39Z

Bes: Changed header from "September issues" to general title - also made version numbers more universal /* September, 2011 Licensing Issues */

Welcome to the PluginBuddy Knowledge Base - Tutorials, Technical Information, Debugging Information, and more.

=Premium Plugins=
* [[Ajax-Edit-Comments]]
* [[BackupBuddy]]
* DisplayBuddy
** [[Accordion]]
** [[Billboard]]
** [[Carousel]]
** [[CopiousComments]]
** [[FeaturedPosts]]
** [[Rotating Images]]
** [[RotatingText]]
** [[Slideshow]]
** [[Tipsy]]
** [[VideoShowcase]]
* [[EmailBuddy]]
* [[LoopBuddy]]
* [[Mobile]]
* [[TailoredLogin]]
* [[ThumbsUp]]
* [[VidEmbed]]

=Free Plugins (active)=
* [[Featured Text]]
* [[PB-Tweet]]
* [[ServerBuddy]]
* [[Tabber Widget]]
* [[ThemeMan]]
* [[S3 URLS]]
* [[YOURLS]]
* [[ContactBuddy]]

=Free Plugins (inactive)=
* [[WP Easy Uploader]]
* [[WP Developer Assistant]]
* [[Easy Theme and Plugin Updater]]
* [[Current Date & Time Widget]]

''[[:Category:PluginBuddy|View all PluginBuddy Wiki Pages]]''

=Misc. Documentation=
==Frequently Asked (Plugin) Questions==
*[[General Plugins FAQ]]

==License Manager Tutorial and Information==
*[[License Manager]]
==PHP Development & Advanced==
*[[.htaccess]]
*[[PHP]]
*[[Arrays]]

[[Category:PluginBuddy]]

=Translations (localization / internationalization)=

Many PluginBuddy plugins come with translation capability. That means such PluginBuddy plugins can be translated (aka localized) to other languages.

===How Translations Work===

PluginBuddy provides the capability to have a translation in such plugins. Anyone wanting to enhance PluginBuddy with specific language translations can do so voluntarily via Translation Files. Translation Files are simply language files created fully and solely by the volunteer community which use the already built in translation-capable features in many of the PluginBuddy plugins to allow such plugins to show text or outputs in different languages. Making PluginBuddy translation-capable is done by PluginBuddy. Creating, updating and sending in any language specific translation files to PluginBuddy is done by the volunteer community.

Anyone can create translation files, package them into the proper format and give PluginBuddy the final translated files that we will try to include in the next update for the plugin in question. We call such awesome people, who create or update the translation files and send us the full translation package files, '''Awesome Translator Volunteers''', and we are really thankful that they take the time to do such an awesome thing.

If you want to help us, you can translate any existing PluginBuddy plugin which supports internationalization (another way of saying localization or translation-capable) and then, once you're fully done, simply let us know in the forums the link to the final language files that we can directly save and simply try to include in any future updates for the plugin(s) in question.

===Tips on how to localize any PluginBuddy Plugin to any non-English language===

The following 9 tips can help you figure out how to approach translations, how to create translations, and how to send us the final translated file for any translation-capable PluginBuddy plugin:

*1 : Many of the PluginBuddy plugins are internationalized, meaning they have the capability to be translated, via actual external translation files, by any non-iThemes-staff Awesome Translator Volunteer who wishes such plugins to be translated to their language.
*2 : If a PluginBuddy plugin is currently not internationalized or you're not sure if it is, you can ask us in the [http://ithemes.com/forum Support Forums] and we'll let you know, or we'll have it included as a future translation feature request. After the translation capability is added to such a plugin, you can submit the actual translation file. Please remember though: we cannot help with creating, understanding or making any language translation files. Our Awesome Translator Volunteers do that voluntarily (you can too! keep on reading) and fully on their own.
*3 : There are MANY resources which teach you how to create and work with WordPress language files. Following are the official 3 directly by the WordPress community:
**1 : [http://codex.wordpress.org/WordPress_in_Your_Language WordPress in Your Language]
**2 : [http://codex.wordpress.org/Translating_WordPress Translating WordPress]
**3 : [http://codex.wordpress.org/I18n_for_WordPress_Developers What WordPress Localization in Plugins is mainly about]
*4 : Translations are sent in from volunteers from all over the world. As a courtesy, we sometimes package the actual language translation files (provided directly by the Awesome Translator Volunteers) in with the final product. If some translation is not included in the actual plugin even when the plugin has the capability to be translated, you can submit the final translation to us for consideration in the next update by posting on our forums OR you can include the translation in your own live or local WordPress install directly for your own use. More info on how to include your own language specific file for your own WordPress sites is in the resources listed in #3 above.
*5 : A translation included in with the final product does not guarantee the accuracy or quality of the translation. These files are from the Awesome Translator Volunteers, and correction of these files is also done by those Awesome Translator Volunteers.
*6 : If a translation is very inaccurate or incomplete, we can put out a request for a new translation from the volunteer community, or remove the translation from the packaged and final product. You can also let us know of any inaccuracies in any existing translation files by the Awesome Volunteers by providing us with the corrected final files. Please remember: we only accept final and full translation files that you yourself have already created or packaged properly. If you let us know only of the actual inaccuracies without providing the final correct files, we cannot make such changes ourselves to the translation files.
*7 : Unfortunately, PluginBuddy cannot work on, help with, create, nor make any updates to any specific translation files you may have, or may be working on, or want to work on. Our Awesome Volunteers do that and simply give us the final files for inclusion or consideration.
*8 : If you have corrections for any existing translation in form of final proper format translation files for an existing language, OR want to provide the final and proper translation files for a new language, please post a new thread in the appropriate product category in the [http://ithemes.com/forum/ PluginBuddy Support Forums] with the final translations files. If you have any support questions on how to create or make language specific translation files, or how translation files work, you can do so on the [http://wordpress.org/support/ WordPress forums], as such support questions are outside the scope of what PluginBuddy support guarantees with your iThemes membership.
*9 : Any final translation file provided by you (or any other Awesome Volunteer) on the support forums will then be saved and filed as a future enhancement request for the future updates of the plugin(s) in question. In your support forum thread, where you share the final complete translation files you inclusion, you can upload your files directly to the forums OR upload them somewhere and link to them in your support forum thread. We will then download and save such files. Remember please: we cannot guarantee looking inside such files or verifying that they are correct in any manner (because of so many languages in the world and so many possible language files everywhere).

Thank you SO MUCH for being interested in providing translation files for our PluginBuddy plugins. We hope you will become one of our Awesome Translator Volunteers, in addition to being our AWESOME CUSTOMER, and create/update any language-specific translation file package and provide it to us so that we can consider including it in future updates.

===Resources for understanding, creating, updating and submitting final translation files===
*Here are the 3 official resources again which you can use to create, update, start work on and finish translation on any of the translation-capable PluginBuddy plugins:
**1 : [http://codex.wordpress.org/WordPress_in_Your_Language WordPress in Your Language]
**2 : [http://codex.wordpress.org/Translating_WordPress Translating WordPress]
**3 : [http://codex.wordpress.org/I18n_for_WordPress_Developers What WordPress Localization in Plugins is mainly about]

=Extra Customizations=
While any extra customization of any PluginBuddy Plugin is beyond the scope of the official support, we do from time to time offer different tips and tutorials on editing the awesome PluginBuddy plugins to better fit your individual needs. All such edits are, however, beyond what is officially supported and provided in the actual plugin admin panel and officially stated features on the individual plugin pages. No official support is provided nor guaranteed in, before, during, after or related to anything resulting from any such edits/customizations.

No support is provided on any of these extra customizations. Any of the steps mentioned in any of these extra custom edits may change at any time depending on newer versions of the plugins being released. Any use or customization of anything, beyond what is provided by default inside the plugin admin menu, means you are proceeding at your own risk and that you accept 100% responsibility and liability for everything you change or modify in any manner in the plugin. Your purchase and use of any PluginBuddy plugin implies and shows that you are buying and using PluginBuddy plugin(s) the way it(they) came in their original unmodified form, with no exceptions.

*Remember:
**[http://pluginbuddy.com/purchase/backupbuddy/ Make a backup of your entire site with BackupBuddy] before making any edits!
** PluginBuddy only supports the official unedited, unmodified versions of all PluginBuddy plugins.
** Use a good text editor to make any file changes. Again, maintain backups!
** Any changes you make to files WILL MOST PROBABLY be lost when the plugin is upgraded to any newer version.
** You are 100% responsible and liable for anything resulting from any of these changes.
** No support is provided nor guaranteed on any of these extra changes in any form or shape, whatsoever, regardless of who suggested these custom edits or suggestions.
** Any extra customization info or suggestion is added voluntarily by PluginBuddy staff to help users as much as possible, even if such customization is outside the scope of any membership support.
** Whether a PluginBuddy staff or representative offered or suggested the edit/customization, another customer or anyone else, PluginBuddy does not officially support nor provide any official support on any such edits.
** We cannot guarantee providing any support on any edits or customization tips we provide.
** Absolutely no support is guaranteed in any manner on any of our free plugins, whether or not there is any customization/edit involved.

=External Plugins Compatibility=

PluginBuddy does not promise, guarantee or provide support for any compatibility with any external plugin. If any PluginBuddy Plugin works without any problems when used with any external plugin in question, that means the PluginBuddy Plugin is most probably working without any issues overall. PluginBuddy is not responsible for making PluginBuddy plugins work in any manner, whether custom, fully, fixed or other, with any external non-PluginBuddy plugins. PluginBuddy is also not responsible for providing any support whatsoever for any external plugin, whether or not such an external plugin is used along with any PluginBuddy plugin.

=Free Plugins=

Free plugins are provided as is. There is no guaranteed support that comes with them. Guaranteed support is limited only and mainly for our premium unmodified plugins.

=Bugs, Features and ETA on new updates=

With every new release of any plugin, there may be a new bug or two. You may also want to have new features added to specific plugins. All existing versions of all plugins can have bugs reported OR new features suggested. All of this is done via the [http://ithemes.com/forum official forums].

New updates are also usually released regularly and at the same time, at very different paces, depending on the current number of bugs, features, new plans and tasks at hand. Therefore it is the official policy that there is NO pre-defined ETA on any bug fix, feature imeplemention OR new update OR new plugin roll-out UNLESS otherwise specified specifically in writing somewhere by an official iThemes employee.

==Bugs, bug reports and bug fixes==

Bug reports are filed and noted as they are encountered (thanks for reporting them to us!). There is never any ETA on any bug fixes unless otherwise noted.

==Feature Requests==

Feature requests and feature suggestions are basically future suggested features that users can suggest, and/or future features PluginBuddy may consider adding to the future versions of the plugin(s) in question (again, thanks for suggesting new features!).

There is no guaranteed ETA on when such feature requests will be implemented, unless otherwise noted. All suggested features are just that: suggestions. They remain suggestions until they're confirmed as officially in the works and to be included. Even then, unless a feature is actually rolled out publicly, there is no guarantee any feature suggestion will be implemented. We do our best to try and accommodate as many feature suggestions as possible.

Also, there is no guarantee that any feature request suggested will be implemented, unless otherwise noted.

==ETA on new updates==

Just like bug fixes and new features, there is never a guaranteed date nor a guaranteed time frame on when new updates will roll out. We work every single day of the week, all the time, on our plugins and thus every day there is something new and improved happening in almost all our plugins daily. Whenever we are ready to release any new updates publicly, you'll find out by seeing the plugin update notice in your WordPress OR in your [http://ithemes.com/member/member.php Member's area].

=What does BETA mean?=

Some of PluginBuddy plugins may be in Beta status OR may have Beta features. BETA simply means that some feature or specific part of the plugin is currently still in testing mode, and can cause issues if not used properly. All BETA plugins/features are not yet 100% stable, and thus should NOT be relied on to be working properly OR working at all. Throughout the iThemes Codex, any time the word "Beta" is used in any form, it refers to Beta plugins, Beta features, Beta status and/or anything related to the Beta nature that is officially announced or mentioned as such by any iThemes staff or on any of the Plugin pages, or in this Codex.

Beta implies that any new features or plugins are very close to being released as 100% working very soon, and that there may still be some issues to fix or test more before removing the Beta status. Since no single software of any kind can be tested under every system and site configuration in the world, the Beta status enables the Beta features to be tested out by as many people on as many different websites and configurations as possible.

*Some points to keep in mind when using any BETA plugin/feature:
**1 : Make [http://pluginbuddy.com/purchase/backupbuddy/ FULL WordPress backups] before using ANY beta feature.
**2 : Beta means that the current software feature is NOT complete, and that you are NOT forced to use such a feature at all. You are advised to WAIT until the BETA status is removed.
**3 : Using any Beta feature of any kind, whether it is an entire plugin or something inside a plugin, means and shows that you are fully accepting any liability for any risks involved.
**4 : Using any Beta feature of any kind, whether it is an entire plugin or something inside a plugin, means and shows that you are fully aware that there are all different kinds of risks involved with such features.
**5 : If you are concerned about your important data or anything bad that might happen as a result of using any Beta feature, do NOT use such Beta features.
**6 : ALWAYS make full [http://pluginbuddy.com/purchase/backupbuddy/ BackupBuddy Backups of all your important data] before using any Beta software, whether that Beta software is from PluginBuddy or from any other place.
**7 : If any issues are found in Beta, they are usually added to the list of bug fixes to be released as a whole, or for the next big update, instead of being updated OR fixed individually on a case by case basis.
**8 : Beta features are recommended to test and play with on test sites/servers and configurations with any dummy data, as long as you have [http://pluginbuddy.com/purchase/backupbuddy/ full backups of all important data] still.
**9 : iThemes is not liable nor cannot be held accountable for any unwanted results resulting from the use of BETA features.
**10 : The very name and nature of BETA shows clearly, without any doubt, that there will most probably be issues and problems involved when such labeled features are used anywhere.
**11 : Support for Beta features may be very limited. We usually simply collect all reports related to Beta features and collect them all for one big update in the future.
**12 : If you lose any important data or settings anywhere, or encounter damaged data or settings anywhere, because of any Beta feature, we will not be able to help you and will simply tell you to revert to your previous [http://pluginbuddy.com/purchase/backupbuddy/ backups]. We will also tell you to always wait for BETA status to be removed before using any such features.

If you do not fully understand what Beta means, OR are not willing to fully accept and be fully liable for any risks involved because of using such Beta software, you should NOT use the Beta software in any manner. In such a case, you should simply wait until the Beta status is removed.

*[http://pluginbuddy.com/what-does-beta-mean/ Blog post announcing what BETA means]

=PluginBuddy Licenses=

==Plugin Conflicts==

Some times, external plugins may cause issues in detaching, deleting, generating OR saving license keys. Such plugins may also cause issues when you want to manually or automatically upgrade plugins when you try to solve licensing issues.

Following is a list of currently known plugins which cause license detaching, deleting, generating OR saving issues. Please disable the following plugins, even temporarily, while you perform all the steps of manually OR automatically upgrading the PluginBuddy plugins in question, and detaching, deleting, generating and saving license keys for them. Keep such plugins disabled UNTIL all license key issues are gone OR at least while you perform these steps.

*Plugins causing PluginBuddy licensing issues
**'''W3 Total Cache or WP Super Cache :''' If you are using any caching plugin like '''W3 Total Cache''' or '''WP Super Cache''', please disable it temporarily and then carry out any required steps. You can re-enable the plugin in the end after everything works in terms of the licenses.
***Fix: Follow the above steps to fix this issue. [http://ithemes.com/forum/index.php?/topic/19436-backupbuddy-license-issue/#p92171 Steps also explained by BackupBuddy customer Laura (thanks!)]
**'''Any other CACHING or related plugin:''' Try disabling such plugins, performing the required steps, and then re-activating the Caching or related plugins in question.

*Related Links
**1 : [http://ithemes.com/forum/index.php?/topic/19079-wont-let-me-set-a-license-key/#p91663 W3 Total Cache plugin conflict and solution]
**2 : [http://ithemes.com/forum/index.php?/topic/19436-backupbuddy-license-issue/#p92171 W3 Total Cache plugin conflict and solution]
**3 : [http://ithemes.com/forum/index.php?/topic/20228-key-does-not-work/#p95697 W3 Total Cache plugin conflict and solution]
**4 : [http://ithemes.com/forum/index.php?/topic/19041-license-problem-causes-loss-of-all-bb-settings-way-to-get-them-back/ WP Super Cache conflict and solution]

==Licensing Issues==

There are some reports that some users have issues with their license insides the Licenses area of different PluginBuddy plugins, including BackupBuddy.

Remember: All your PluginBuddy plugins, including BackupBuddy, will CONTINUE WORKING PERFECTLY even with these licensing issues. You can keep using the plugins exactly how you want them even during these licensing issues. Your plugins are NOT affected by this licensing situation in any manner.

Your membership is also completely fine and you have NOT lost any license(s). The issue is happening to some customers who simply need to upgrade manually to the latest version of their plugin, if the automatic upgrade does not work.

*Plugins with the update versions which remove this issue completely
**ALL PluginBuddy Products

*You can upgrade via one of the following:
**Automatically upgrade to the latest version
**Manually update by downloading the latest zip version of your PluginBuddy plugin from your Member's panel and then
***Overwrite your existing plugin directory via FTP with the new files.
***De-activate the existing plugin, delete it via your '''WordPress --> Plugins''' area and then upload the newly downloaded zip file. Then re-activate the plugin.
**That will remove the issue completely.
*DETACH the key and then RE-ATTACH the license key for the specific site in question IF licensing still shows issues AFTER manually upgrading to the latest version of the plugin in question (check your Member's area for the latest version download)
*Also make sure to DETACH the key, DELETE that same AND any other keys related to that specific site from the entire licenses area, and then GENERATE a new key for that site IF detaching and re-attaching the license key does not work AFTER manually upgrading (for example, manually upgrading to the latest BackupBuddy version - all plugins have their own latest version numbers - check your Member's area for the latest version download)

[http://ithemes.com/forum/index.php?/topic/6691-read-this-first-pluginbuddy-licensing-issues/page-2/#p85977 First reports]

Mobile

2011-11-30T22:35:15Z

Bes: Updated the "Link to Full Site" code according to http://ithemes.com/support/mobile/view-full-site-link-doesnt-always-work/

Advanced technical support for Mobile:

* [[Mobile: Error Codes]]
* [[Mobile: Advanced Debugging]]

=Documentation=

===Theme Creation===
Live themes are stored in /files/pluginbuddy_mobile/THEMENAME/ (multisites) OR /wp-content/uploads/pluginbuddy_mobile/THEMENAME/ . You should always edit the theme files in these directories.

Non-live original theme files (backups and originals) are stored in /wp-content/plugins/mobile/themes/THEMENAME/ You should never edit the files in this directory.

If you would like to edit an existing theme you may do so by editing the live theme files. If you do this we suggest unchecking the option in Settings for automatically upgrading theme files on automatic upgrades to prevent your changes from being lost. Style manager edits create a CSS file within /files/pluginbuddy_mobile/THEMENAME.css (multisites) or /wp-content/uploads/pluginbuddy_mobile/THEMENAME.css so that these changes will not be lost on upgrades.

To create a new theme you can just clone an existing theme to /files/pluginbuddy_mobile/THEMENAME/ (multisites) or /wp-content/uploads/pluginbuddy_mobile/NEWTHEMENAME/

'''Additional Head HTML (includes Apple icon definitions)'''
<pre>
if ( defined('MOBILEBUDDY_HEAD_CONTENT') ) {
echo MOBILEBUDDY_HEAD_CONTENT;
}
</pre>

'''Link to Full Site'''
<pre>
if ( defined('MOBILEBUDDY_FULL_SITE_LINK') ) {
echo '<a href="' . add_query_arg( 'nomobile', '', str_replace( 'mobile', '', $_SERVER['REQUEST_URI'] ) ) . '">View Full Site</a>';
}
</pre>

*Related forum
**http://ithemes.com/forum/index.php?/topic/20587-view-full-site-link-doesnt-always-work/

=Customize Mobile=

===Extra Customizations Policies===
[http://ithemes.com/codex/page/PluginBuddy#Extra_Customizations Check out the official policy and details on any Extra Customizations]

===Remove Footer Link===
You can remove or change the footer text and/or link that is shown to all mobile users by default.

*1 : To remove OR change that footer, edit the footer.php file in the appropriate theme folder, depending on which Mobile theme you are using. That file will be in one of the theme directories in either of the following directories:
**wp-content/uploads/pluginbuddy_mobile
**OR (on Multisites) wp-content/blogs.dir/X/files/pluginbuddy_mobile (change the X to the appropriate site number)
*2 : Find line 12 of the footer.php to what you want. It currently says <pre brush="html">Mobile Site By <a href="http://pluginbuddy.com/">PluginBuddy</a><br /></pre>
*3 : Change the above to anything you wish to be shown OR hidden from the mobile users in question who will be viewing that theme.

*Related thread:
**http://ithemes.com/forum/index.php?/topic/14450-removing-the-pluginbuddy-link-from-the-footer/

=Plugin Conflicts=
The following plugins are known to cause conflicts with OR in Mobile. You can either disable the following plugins, upgrade them to their latest versions OR let their development team know about this. Mobile works perfectly when such plugins (or some certain versions of them) are not active.

*SexyBookmarks (by Shareaholic) - Version 4.0.6.2
**Dropdown menu has been confirmed to not work properly with this version
***http://ithemes.com/forum/index.php?/topic/19455-mobile-theme-not-working/

=Additional Resources=
* [http://pluginbuddy.com/purchase/mobile/ Purchase Mobile]
* [http://pluginbuddy.com/tutorials/ PluginBuddy Tutorials]
* [http://pluginbuddy.com/ PluginBuddy.com]
* [http://pluginbuddy.com/support/ Support Forums]

[[Category:PluginBuddy]]

VideoShowcase

2011-11-29T23:47:34Z

Bes: Added /* Adding Thumbnails to Videos */ section

{{#ev:youtube|FZXSR-0WPkQ|400|right}}
'''Series:''' [[DisplayBuddy]]
==Description==
Video Showcase is a plugin that uses video links from [http://youtube.com Youtube] and [http://vimeo.com Vimeo] to generate thumbnail images for the videos and display those images as video embed links on the front end of your site. When a visitor clicks one of the thumbnail image links the video for that link is displayed in a styled thickbox. The different video links are stored in groups so that the different groups can be displayed through out your website by placing them in widget areas or using shortcodes.

==3 Step Process==
====Step 1. Create a Group====
The first step in adding VideoShowcase to your site is to create a group to store the video entries in. The link to VideoShowcase in the WordPress admin area is in the DisplayBuddy section of the menu. When you click the VideoShowcase link it will direct you to the area where you can create a group. The only information requested to create a group is a name for that group, group image width, and group image height.

[[File:Create_group.png‎]]

After you have created a group it will be added to a table that lists all of the existing groups and lists information about them.

====Step 2. Add videos to the groups====
Once you have created a group then you will be able to add videos to that group. To add videos to a group you can click the "Add Videos" link that is next to the name of the group. There are two different forms for adding videos. The first form can be used for adding a YouTube or Vimeo video, and the second form can be used to add a stand alone video (ex: mp4, flv, and mov).
=====Adding a YouTube or Vimeo video=====
This form only requires a title and a video page URL.

[[File:Add_video.png‎]]

Example of what to put in the "video URL" are outlined in red in the images below:

[[File:Youtube_sourc.png|418px]]

[[File:Vimeo_source.png|418px]]

Since the videos are stored on YouTube and Vimeo those sites already have images for those videos that VideoShowcase retrieves from those sites and uploads them to your WordPress media library. If you decide that you don't like the image that is retrieved from YouTube or Vimeo then you can edit the video entry and upload or select an image from your media library.
=====Adding a Stand Alone video=====
This form is used for adding videos that stored in stand alone locations (ex: Amazon S3, Rackspace).
Here is a list of the required information for adding a stand alone video:
* Video Title
* Video File URL - VideoShowcase can only play mp4, flv, and mov files so it is important to make sure that the video files are in the correct format (ex:http://mysite..com/videos/anyvideo.mp4).
* Select or upload an image - Upload an image or select an image from your media library.

=====Adding Thumbnails to Videos=====
You can add thumbnails to both Stand Alone videos and externally hosted videos.

*For Stand Alone videos:
**Select and upload an image when you're adding your video under the "Add Stand Alone Video" option
[[File:Video_Showcase_‹_Besizm_—_WordPress.png]]

*For YouTube and Vimeo videos:
**Add the video
**Edit the video by clicking "Edit Video" link in front of the video
**Click the "Custom Image" button.
[[File:1Video_Showcase_‹_Besizm_—_WordPress.png]]

*Related forums
**http://ithemes.com/forum/index.php?/topic/8442-feature-requests-and-ideas/#p97488
**http://ithemes.com/forum/index.php?/topic/17519-click-to-play-icon-not-using-custom-image/#p88954

====Step 3. Display VideoShowcase on your site====
VideoShowcase can be added to your site using two different methods, widgets or shortcode.
====Widget====
Navigate to the Widgets area under Appearance in the WordPress Admin area. Drag the VideoShowcase widget into the widget area that you would like for it to display in and fill out the widget form with the information for the group you would like to show.
====Shortcode====
The groups table in VideoShowcase will display a list of information for each different group that you have created. In the row of the group that you would like to display there is a "Create Shortcode" link that will bring up a popup form to help create a customized shortcode for that group and settings you would like. If you would like to add a VideoShowcase group to a post or page all you have to do is copy that shortcode and paste it the content of a page or post.

[[File:widget_display.png]]

==Customize VideoShowcase==

====Extra Customizations Policies====
[http://ithemes.com/codex/page/PluginBuddy#Extra_Customizations Check out the official policy and details on any Extra Customizations]

====Force VideoShowcase to appear OVER/ON-TOP of Flash====

Many times, flash and other external elements can start appearing on top of VideoShowcase videos, whether or not VideoShowcase video is loaded above or before such elements.

One solution for this is to change the wmode key for your flash.
*Related links
**[http://www.actionscript.org/forums/showthread.php3?t=105396 Make your flash appear BELOW/UNDER other elements]
**http://ithemes.com/forum/index.php?/topic/18259-is-there-a-way-to-force-the-video-popup-to-the-topmost-layer/

====Change Default Video Size====

Currently, the default pop-up videos play at 500px width and 344px height.

You can change this to any other dimension you wish by changing the numeric values on lines 20 and 21 in the '''''wp-content/plugins/videoshowcase/js/jquery.pbvideosc.js''''' file.

Following are lines 20 and 21:

<code>
default_width: 500,

default_height: 344,
</code>

Only change the numeric value in the above 2 lines. Leave everything else as is.

*Related forum thread
**http://ithemes.com/forum/index.php?/topic/19110-change-video-pop-up-size-to-hd/

====Hide Video Thumbnails====

You can hide the video thumbnails completely to show only the associated Titles, if they are defined. Put the following code in your theme's css file:

<pre code="css">#videoshowcaseid-1 img
{
display: none;
}</pre>

Change the "'''1'''" in the <code>videoshowcaseid-1</code> to the number corresponding to your videoshowcase group number. That will hide the thumbnails completely.

*Related forum thread
**http://ithemes.com/forum/index.php?/topic/19341-modal-window-off-of-text-link/

==Additional Resources==
# [http://pluginbuddy.com/free-wordpress-plugins/ Free Plugins by PluginBuddy]

# [http://pluginbuddy.com/tutorials/ PluginBuddy Tutorials]
# [http://pluginbuddy.com/ PluginBuddy.com]
# [http://pluginbuddy.com/support/ Support Forums]

[[Category:PluginBuddy]]

File:1Video Showcase ‹ Besizm — WordPress.png

2011-11-29T23:39:31Z

Bes: Edit a YouTube or Vimeo video and click "Custom Image" to attach a thumbnail to it.

Edit a YouTube or Vimeo video and click "Custom Image" to attach a thumbnail to it.

File:Video Showcase ‹ Besizm — WordPress.png

2011-11-29T23:38:44Z

Bes: Adding thumbnails to self-hosted videos and external videos.

Adding thumbnails to self-hosted videos and external videos.

Tipsy

2011-11-21T23:48:43Z

Bes: Added "New Lines - Line Breaks" and /* HTML Code */ sections

{{#ev:vimeo|30376241|400|right}}

Tipsy is available as a [http://pluginbuddy.com/purchase/tipsy/ stand-alone plugin] or as part of the [http://pluginbuddy.com/purchase/displaybuddy/ DisplayBuddy series]. [http://demos.ithemes.com/tipsy/ See a demo here] or [http://trials.ithemes.com/tipsy/ try it out in WordPress live!]

==Description==
The Tipsy plugin adds the ability to create tooltips for placement in posts or pages. Tooltips are displayed when hovering or clicking on specified content. This allows you to provide additional information to visitors.

==Groups==
The first step in adding Tipsy tooltips to your site is to create a group in the Tipsy settings. Tipsy allows you to create multiple groups with unique settings, styles, and even default tip content.

==Feature Overview==
6 different tooltip layouts to choose from.

Tipsy uses oembed for embedding media within the tooltip. See a list of what media oembed supports [http://oembed.com/ here ]

==Displaying on your site==
To add a Tooltip you will need to first be editing a page or post. Highlight the text/content that you would like to be hovered or clicked to display the tooltip. Then click the Tipsy icon in the WYSIWYG editor. Select the Tipsy group you would like to use and provide the test/content you would like to display within the Tipsy tip. This can be test or other HTML elements, even video.

==Shortcode==
Display your Tipsy in style by using the shortcode <code>[tipsy content="tip content goes here" use_oembed='false' group="0"]content that the tip applies to[/tipsy]</code>. We recommend doing this in the HTML Mode editor.

===Shortcode Parameters===
''content'' · Content that goes inside of the tooltip.
''group'' · group number for the tooltip group that you want to display.
''use_oembed'' . true or false - Whether to embed videos or not (uses oEmbed)

===Display Videos inside Tipsy Shortcode===

Use the following format to show YouTube videos inside the Tipsy tooltip in the HTML Mode editor. Change the video link to any YouTube link you wish:

<code>[tipsy content="http://www.youtube.com/watch?v=FDHNequGw4k" use_oembed='true' group="0"]content that the tip applies to[/tipsy]</code>

===Display Images inside Tipsy Shortcode===

Use the following format to show images inside the Tipsy tooltip in the HTML Mode editor. Change the image link to any image link online:

<code>[tipsy content='<img src="http://pluginbuddy.com/files/2011/10/Tipsy-copy-150x150.png">' group="0" ]content that the tip applies to[/tipsy]</code>

===Display iframe inside Tipsy Shortcode===

Use the following format to show any kind of an iframe inside the Tipsy tooltip in the HTML Mode editor. Change the link and width/height dimensions to your needs:

<code>[tipsy content='<iframe src="http://www.ithemes.com" frameborder="0" width="200" height="110"></iframe>' group="2" ]testing iframes[/tipsy]</code>

*Related link
**http://ithemes.com/forum/index.php?/topic/20204-using-tipsy-to-display-iframe-content/

===SAMPLE Shortcode Text File===

If you are having trouble copy pasting the above code OR not getting it to work, here is a sample TEXT file that you can copy paste from. Simply copy paste the contents into your Page or Post editor, in HTML Mode, test that it works, and then change the links accordingly.

http://bes.internal.ithemes.com/tipsy-media-shortcode.txt

===Special Characters===

If you want to show special characters in your Tipsy, like " @ & % $ and others, simply replace them with their [http://www.utexas.edu/learn/html/spchar.html HTML counterpart ]

===New Lines - Line Breaks===

If you want to have a line break in Tipsy, simply put the line break (ENTER key) inside the Tipsy content instead of using any html code.

Example of a line break:

<pre brush="html">[tipsy content="Actual content Actual content

NEW NEW LINE WITHOUT HTML" group="0" ]Testing 1[/tipsy]</pre>

===HTML Code===

Simply putting in html code inside the Tipsy shortcode should work.

Example of html inside Tipsy:

<pre brush="html">[tipsy content="Actual content Actual content <ul><li>abc</li></ul>" group="0" ]Testing 1[/tipsy]</pre>

==Template Tag==
You can manually call Tipsy if you know the Group ID.

<pre class="brush:php">
<?php
/*
* pb_tipsy()
* Insert a Tipsy tooltip
*
*
* The defaults for the parameter $args are:
* content - Default is an empty string - The content to show in the tooltip
* group - Default is 0 - The Group ID (you can get this from the Tipsy settings)
* filler - Default is an empty string - The text that people hover/click on to view the tooltip
* use_oembed - Default is false - Whether you intend to use oembed to embed a video
*
*
* @param array $args Elements that make up a voting group to insert.
* @return Tip HTML on success */
?>
</pre>
<pre class="brush:php">
<td id="accordion" align="left">
<?php echo pb_tipsy( array(
'content' => 'http://www.youtube.com/watch?v=NfBsRc0R3Ps&hd=1',
'filler' => 'Admin Dashboard',
'group' => 1,
'use_oembed' => true

) ); ?>
</pre>

To see a live example of this template tag in use, please download our Tipsy Page Template (should be able to drop into any theme to test it): [[File:Tipsy.php.zip]]
==Group Settings==
Here is a list of all of the Tipsy settings and a description of what each setting controls.

'''Group Title''' - This setting will allow you to change the title of the group at any time.

'''Tip activation''' - Method upon which the tooltip is activated. Can be set on hover, focus, or click.

'''Tip Position''' - Default orientation tooltip should show up as. You can set it to: "top", "bottom", "left" or "right".

'''Auto hide''' - When set to true the tooltip will only fadeout when you hover over the actual tooltip and then hover off of it.

'''Max width''' - CSS max-width property for the Tipsy element.

'''Edge offset''' - Distances the Tipsy popup from the element with tooltip applied to it by the number of pixels specified.

'''Display delay''' - Number of milliseconds to delay before showing the Tipsy popup after you mouseover an element with tooltip applied to it.

'''Fade in speed''' - Speed at which the Tipsy popup will fade into view.

'''Fade out speed''' - Speed at which the Tipsy popup will fade out of view.

'''Tip Content''' - Default content that goes inside the tooltip itself.

==Customize Tipsy==

===Extra Customizations Policies===
[http://ithemes.com/codex/page/PluginBuddy#Extra_Customizations Check out the official policy and details on any Extra Customizations]

===Edit and/or Create More Layouts===
Tipsy comes with six current layouts that you can choose from to style your Tipsy tooltips. You can edit any existing layout OR create a new one to suit your needs.

Make a [http://pluginbuddy.com/purchase/backupbuddy/ BackupBuddy backup of everything before you proceed], or at least download the existing styles to your computer as a backup. You can also always download the latest Tipsy from your [http://ithemes.com/member/member.php Member's Area], unzip it on your computer and upload only the wp-content/plugins/tipsy/layouts in case you want to restore the default layouts (in case you accidentally mess up something that you want to undo).

*Remember: if you edit any existing default layout that comes with Tipsy, all your changes will be lost when you upgrade Tipsy to any newer version.

=====Edit Existing Layout=====
*To edit any existing layout display:
**Go to wp-content/plugins/tipsy/layouts folder
**Go into the layout you want to edit. Each layout is ordered in the manner it is shown in your Tipsy Group Settings area, from left to right.
**Edit the style.css file in that folder to your liking.
**Save. Your Tipsy will now be shown according to your styling changes in the style.css file.

Note that you will have to edit any existing layout again after upgrades, as upgrading to any new Tipsy version would override the default templates with never versions. It is recommended that you instead create a new layout, as explained below.

=====Create New Layout=====
*To create a new Tipsy layout, you can do one of the following 2:
**1 : Create a new folder in the wp-content/plugins/tipsy/layouts folder
***Put a style.css file in that folder and any image with the name screenshot.png
***Put any form of styling you wish in that style.css file. You can check the existing layout folders to copy paste the styling classes from.
**2 : Duplicate any existing folder in the wp-content/plugins/tipsy/layouts folder and work on that css file.
***Go to the wp-content/plugins/tipsy/layouts folder
****If you are using a control panel like cPanel, duplicate any folder and give it any different name you wish.
****If you are using an FTP program, download any layout folder to your computer, rename it, and then upload it back up.
***Edit the style.css file in that newly duplicated/renamed/uploaded folder to suit your needs.

After you edit any existing layout OR create a new Tipsy layout, simply go into any Tipsy Group Settings and choose the appropriate Layout image for the styling you just worked on in the new folder.

*Remember:
**1 : Each image shown in Tipsy Group Settings page corresponds to the folder order list in the wp-content/plugins/tipsy/layouts folder. So if you click on the 4th image on your Tipsy Group Settings page, you are basically choosing the 4th folder, listed alphabetically, in the wp-content/plugins/tipsy/layouts folder.
**2 : If you edit any existing default Tipsy layout instead of creating a new Tipsy layout, all your changes will be lost when you upgrade to a newer version. Upgrading results in all the default files, including the default templates, to be overwritten also. You will have to redo the changes again if you choose this route. Better option would be to create a new layout as explained above.

===Change color of the arrow in Default layout===

To change the color of the arrow in the Default layout, you want to style the <code>#tiptip_holder.tip_right #tiptip_arrow_inner</code> property.

To do this, edit the '''style.css''' file in the '''wp-content/plugins/tipsy/layouts/default''' folder (OR any folder you have your layout in) and modify (or have) the following:

<pre brush="css">#tiptip_holder.tip_right #tiptip_arrow_inner {
margin-top: -6px;
margin-left: -5px;
border-right-color: rgb(255,0,0);
border-right-color: rgba(255,0,0,0.92);
}
</pre>

Change the <code>250,0,0</code> to your prefer color's RGB code. In the above example, <code>250,0,0</code> is RED.

*Related links
**[http://www.w3.org/TR/css3-color/ Info on CSS3 colors and their RGB codes]
**[http://www.google.com/#hl=en&sugexp=gsihc&cp=8&gs_id=r&xhr=t&q=color+rgb Google search for RGB values of colors]

===Change position of the Tipsy box===

To change the position of the tipsy box, you can either change the "'''''Edge offset'''''" value in Tipsy group settings, or modify the <code>#tiptip_holder</code> property in the style.css file of your folder of the layout you have currently chosen in Tipsy '''wp-content/plugins/tipsy/layouts/YOUR-CHOSEN-LAYOUT-NAME'''

Edit the style.css file and the entire section below to anything you like:

<pre brush="css">#tiptip_holder {
display: none;
position: absolute;
top: 0;
left: 100px;
z-index: 99999;
}</pre>

'''Top''' and '''left''' values change the location of the entire Tipsy tooltip. In the above example, <code>left: 100px;</code> basically moves the entire Tipsy 100 pixels to the right.

==Additional Resources==
# [http://pluginbuddy.com/free-wordpress-plugins/ Free Plugins by PluginBuddy]
# [http://pluginbuddy.com/tutorials/ PluginBuddy Tutorials]
# [http://pluginbuddy.com/ PluginBuddy.com]
# [http://ithemes.com/forum/tipsy/ Tipsy Support Forums]

[[Category:PluginBuddy]]

Mobile

2011-11-21T17:48:14Z

Bes: Described editing theme files on Multisites and regular sites a bit more clearly /* Theme Creation */

Advanced technical support for Mobile:

* [[Mobile: Error Codes]]
* [[Mobile: Advanced Debugging]]

=Documentation=

===Theme Creation===
Live themes are stored in /files/pluginbuddy_mobile/THEMENAME/ (multisites) OR /wp-content/uploads/pluginbuddy_mobile/THEMENAME/ . You should always edit the theme files in these directories.

Non-live original theme files (backups and originals) are stored in /wp-content/plugins/mobile/themes/THEMENAME/ You should never edit the files in this directory.

If you would like to edit an existing theme you may do so by editing the live theme files. If you do this we suggest unchecking the option in Settings for automatically upgrading theme files on automatic upgrades to prevent your changes from being lost. Style manager edits create a CSS file within /files/pluginbuddy_mobile/THEMENAME.css (multisites) or /wp-content/uploads/pluginbuddy_mobile/THEMENAME.css so that these changes will not be lost on upgrades.

To create a new theme you can just clone an existing theme to /files/pluginbuddy_mobile/THEMENAME/ (multisites) or /wp-content/uploads/pluginbuddy_mobile/NEWTHEMENAME/

'''Additional Head HTML (includes Apple icon definitions)'''
<pre>
if ( defined('MOBILEBUDDY_HEAD_CONTENT') ) {
echo MOBILEBUDDY_HEAD_CONTENT;
}
</pre>

'''Link to Full Site'''
<pre>
if ( defined('MOBILEBUDDY_FULL_SITE_LINK') ) {
echo '<a href="' . add_query_arg( 'nomobile', '' ) . '">View Full Site</a>';
}
</pre>

=Customize Mobile=

===Extra Customizations Policies===
[http://ithemes.com/codex/page/PluginBuddy#Extra_Customizations Check out the official policy and details on any Extra Customizations]

===Remove Footer Link===
You can remove or change the footer text and/or link that is shown to all mobile users by default.

*1 : To remove OR change that footer, edit the footer.php file in the appropriate theme folder, depending on which Mobile theme you are using. That file will be in one of the theme directories in either of the following directories:
**wp-content/uploads/pluginbuddy_mobile
**OR (on Multisites) wp-content/blogs.dir/X/files/pluginbuddy_mobile (change the X to the appropriate site number)
*2 : Find line 12 of the footer.php to what you want. It currently says <pre brush="html">Mobile Site By <a href="http://pluginbuddy.com/">PluginBuddy</a><br /></pre>
*3 : Change the above to anything you wish to be shown OR hidden from the mobile users in question who will be viewing that theme.

*Related thread:
**http://ithemes.com/forum/index.php?/topic/14450-removing-the-pluginbuddy-link-from-the-footer/

=Plugin Conflicts=
The following plugins are known to cause conflicts with OR in Mobile. You can either disable the following plugins, upgrade them to their latest versions OR let their development team know about this. Mobile works perfectly when such plugins (or some certain versions of them) are not active.

*SexyBookmarks (by Shareaholic) - Version 4.0.6.2
**Dropdown menu has been confirmed to not work properly with this version
***http://ithemes.com/forum/index.php?/topic/19455-mobile-theme-not-working/

=Additional Resources=
* [http://pluginbuddy.com/purchase/mobile/ Purchase Mobile]
* [http://pluginbuddy.com/tutorials/ PluginBuddy Tutorials]
* [http://pluginbuddy.com/ PluginBuddy.com]
* [http://pluginbuddy.com/support/ Support Forums]

[[Category:PluginBuddy]]

PluginBuddy

2011-11-17T23:19:52Z

Bes: Added another W3 Total Cache plugin conflict example url /* Plugin Conflicts */

Welcome to the PluginBuddy Knowledge Base - Tutorials, Technical Information, Debugging Information, and more.

=Premium Plugins=
* [[Ajax-Edit-Comments]]
* [[BackupBuddy]]
* DisplayBuddy
** [[Accordion]]
** [[Billboard]]
** [[Carousel]]
** [[CopiousComments]]
** [[FeaturedPosts]]
** [[Rotating Images]]
** [[RotatingText]]
** [[Slideshow]]
** [[Tipsy]]
** [[VideoShowcase]]
* [[EmailBuddy]]
* [[LoopBuddy]]
* [[Mobile]]
* [[TailoredLogin]]
* [[ThumbsUp]]
* [[VidEmbed]]

=Free Plugins (active)=
* [[Featured Text]]
* [[PB-Tweet]]
* [[ServerBuddy]]
* [[Tabber Widget]]
* [[ThemeMan]]
* [[S3 URLS]]
* [[YOURLS]]
* [[ContactBuddy]]

=Free Plugins (inactive)=
* [[WP Easy Uploader]]
* [[WP Developer Assistant]]
* [[Easy Theme and Plugin Updater]]
* [[Current Date & Time Widget]]

''[[:Category:PluginBuddy|View all PluginBuddy Wiki Pages]]''

=Misc. Documentation=
==Frequently Asked (Plugin) Questions==
*[[General Plugins FAQ]]

==License Manager Tutorial and Information==
*[[License Manager]]
==PHP Development & Advanced==
*[[.htaccess]]
*[[PHP]]
*[[Arrays]]

[[Category:PluginBuddy]]

=Translations (localization / internationalization)=

Many PluginBuddy plugins come with translation capability. That means such PluginBuddy plugins can be translated (aka localized) to other languages.

===How Translations Work===

PluginBuddy provides the capability to have a translation in such plugins. Anyone wanting to enhance PluginBuddy with specific language translations can do so voluntarily via Translation Files. Translation Files are simply language files created fully and solely by the volunteer community which use the already built in translation-capable features in many of the PluginBuddy plugins to allow such plugins to show text or outputs in different languages. Making PluginBuddy translation-capable is done by PluginBuddy. Creating, updating and sending in any language specific translation files to PluginBuddy is done by the volunteer community.

Anyone can create translation files, package them into the proper format and give PluginBuddy the final translated files that we will try to include in the next update for the plugin in question. We call such awesome people, who create or update the translation files and send us the full translation package files, '''Awesome Translator Volunteers''', and we are really thankful that they take the time to do such an awesome thing.

If you want to help us, you can translate any existing PluginBuddy plugin which supports internationalization (another way of saying localization or translation-capable) and then, once you're fully done, simply let us know in the forums the link to the final language files that we can directly save and simply try to include in any future updates for the plugin(s) in question.

===Tips on how to localize any PluginBuddy Plugin to any non-English language===

The following 9 tips can help you figure out how to approach translations, how to create translations, and how to send us the final translated file for any translation-capable PluginBuddy plugin:

*1 : Many of the PluginBuddy plugins are internationalized, meaning they have the capability to be translated, via actual external translation files, by any non-iThemes-staff Awesome Translator Volunteer who wishes such plugins to be translated to their language.
*2 : If a PluginBuddy plugin is currently not internationalized or you're not sure if it is, you can ask us in the [http://ithemes.com/forum Support Forums] and we'll let you know, or we'll have it included as a future translation feature request. After the translation capability is added to such a plugin, you can submit the actual translation file. Please remember though: we cannot help with creating, understanding or making any language translation files. Our Awesome Translator Volunteers do that voluntarily (you can too! keep on reading) and fully on their own.
*3 : There are MANY resources which teach you how to create and work with WordPress language files. Following are the official 3 directly by the WordPress community:
**1 : [http://codex.wordpress.org/WordPress_in_Your_Language WordPress in Your Language]
**2 : [http://codex.wordpress.org/Translating_WordPress Translating WordPress]
**3 : [http://codex.wordpress.org/I18n_for_WordPress_Developers What WordPress Localization in Plugins is mainly about]
*4 : Translations are sent in from volunteers from all over the world. As a courtesy, we sometimes package the actual language translation files (provided directly by the Awesome Translator Volunteers) in with the final product. If some translation is not included in the actual plugin even when the plugin has the capability to be translated, you can submit the final translation to us for consideration in the next update by posting on our forums OR you can include the translation in your own live or local WordPress install directly for your own use. More info on how to include your own language specific file for your own WordPress sites is in the resources listed in #3 above.
*5 : A translation included in with the final product does not guarantee the accuracy or quality of the translation. These files are from the Awesome Translator Volunteers, and correction of these files is also done by those Awesome Translator Volunteers.
*6 : If a translation is very inaccurate or incomplete, we can put out a request for a new translation from the volunteer community, or remove the translation from the packaged and final product. You can also let us know of any inaccuracies in any existing translation files by the Awesome Volunteers by providing us with the corrected final files. Please remember: we only accept final and full translation files that you yourself have already created or packaged properly. If you let us know only of the actual inaccuracies without providing the final correct files, we cannot make such changes ourselves to the translation files.
*7 : Unfortunately, PluginBuddy cannot work on, help with, create, nor make any updates to any specific translation files you may have, or may be working on, or want to work on. Our Awesome Volunteers do that and simply give us the final files for inclusion or consideration.
*8 : If you have corrections for any existing translation in form of final proper format translation files for an existing language, OR want to provide the final and proper translation files for a new language, please post a new thread in the appropriate product category in the [http://ithemes.com/forum/ PluginBuddy Support Forums] with the final translations files. If you have any support questions on how to create or make language specific translation files, or how translation files work, you can do so on the [http://wordpress.org/support/ WordPress forums], as such support questions are outside the scope of what PluginBuddy support guarantees with your iThemes membership.
*9 : Any final translation file provided by you (or any other Awesome Volunteer) on the support forums will then be saved and filed as a future enhancement request for the future updates of the plugin(s) in question. In your support forum thread, where you share the final complete translation files you inclusion, you can upload your files directly to the forums OR upload them somewhere and link to them in your support forum thread. We will then download and save such files. Remember please: we cannot guarantee looking inside such files or verifying that they are correct in any manner (because of so many languages in the world and so many possible language files everywhere).

Thank you SO MUCH for being interested in providing translation files for our PluginBuddy plugins. We hope you will become one of our Awesome Translator Volunteers, in addition to being our AWESOME CUSTOMER, and create/update any language-specific translation file package and provide it to us so that we can consider including it in future updates.

===Resources for understanding, creating, updating and submitting final translation files===
*Here are the 3 official resources again which you can use to create, update, start work on and finish translation on any of the translation-capable PluginBuddy plugins:
**1 : [http://codex.wordpress.org/WordPress_in_Your_Language WordPress in Your Language]
**2 : [http://codex.wordpress.org/Translating_WordPress Translating WordPress]
**3 : [http://codex.wordpress.org/I18n_for_WordPress_Developers What WordPress Localization in Plugins is mainly about]

=Extra Customizations=
While any extra customization of any PluginBuddy Plugin is beyond the scope of the official support, we do from time to time offer different tips and tutorials on editing the awesome PluginBuddy plugins to better fit your individual needs. All such edits are, however, beyond what is officially supported and provided in the actual plugin admin panel and officially stated features on the individual plugin pages. No official support is provided nor guaranteed in, before, during, after or related to anything resulting from any such edits/customizations.

No support is provided on any of these extra customizations. Any of the steps mentioned in any of these extra custom edits may change at any time depending on newer versions of the plugins being released. Any use or customization of anything, beyond what is provided by default inside the plugin admin menu, means you are proceeding at your own risk and that you accept 100% responsibility and liability for everything you change or modify in any manner in the plugin. Your purchase and use of any PluginBuddy plugin implies and shows that you are buying and using PluginBuddy plugin(s) the way it(they) came in their original unmodified form, with no exceptions.

*Remember:
**[http://pluginbuddy.com/purchase/backupbuddy/ Make a backup of your entire site with BackupBuddy] before making any edits!
** PluginBuddy only supports the official unedited, unmodified versions of all PluginBuddy plugins.
** Use a good text editor to make any file changes. Again, maintain backups!
** Any changes you make to files WILL MOST PROBABLY be lost when the plugin is upgraded to any newer version.
** You are 100% responsible and liable for anything resulting from any of these changes.
** No support is provided nor guaranteed on any of these extra changes in any form or shape, whatsoever, regardless of who suggested these custom edits or suggestions.
** Any extra customization info or suggestion is added voluntarily by PluginBuddy staff to help users as much as possible, even if such customization is outside the scope of any membership support.
** Whether a PluginBuddy staff or representative offered or suggested the edit/customization, another customer or anyone else, PluginBuddy does not officially support nor provide any official support on any such edits.
** We cannot guarantee providing any support on any edits or customization tips we provide.
** Absolutely no support is guaranteed in any manner on any of our free plugins, whether or not there is any customization/edit involved.

=External Plugins Compatibility=

PluginBuddy does not promise, guarantee or provide support for any compatibility with any external plugin. If any PluginBuddy Plugin works without any problems when used with any external plugin in question, that means the PluginBuddy Plugin is most probably working without any issues overall. PluginBuddy is not responsible for making PluginBuddy plugins work in any manner, whether custom, fully, fixed or other, with any external non-PluginBuddy plugins. PluginBuddy is also not responsible for providing any support whatsoever for any external plugin, whether or not such an external plugin is used along with any PluginBuddy plugin.

=Free Plugins=

Free plugins are provided as is. There is no guaranteed support that comes with them. Guaranteed support is limited only and mainly for our premium unmodified plugins.

=Bugs, Features and ETA on new updates=

With every new release of any plugin, there may be a new bug or two. You may also want to have new features added to specific plugins. All existing versions of all plugins can have bugs reported OR new features suggested. All of this is done via the [http://ithemes.com/forum official forums].

New updates are also usually released regularly and at the same time, at very different paces, depending on the current number of bugs, features, new plans and tasks at hand. Therefore it is the official policy that there is NO pre-defined ETA on any bug fix, feature imeplemention OR new update OR new plugin roll-out UNLESS otherwise specified specifically in writing somewhere by an official iThemes employee.

==Bugs, bug reports and bug fixes==

Bug reports are filed and noted as they are encountered (thanks for reporting them to us!). There is never any ETA on any bug fixes unless otherwise noted.

==Feature Requests==

Feature requests and feature suggestions are basically future suggested features that users can suggest, and/or future features PluginBuddy may consider adding to the future versions of the plugin(s) in question (again, thanks for suggesting new features!).

There is no guaranteed ETA on when such feature requests will be implemented, unless otherwise noted. All suggested features are just that: suggestions. They remain suggestions until they're confirmed as officially in the works and to be included. Even then, unless a feature is actually rolled out publicly, there is no guarantee any feature suggestion will be implemented. We do our best to try and accommodate as many feature suggestions as possible.

Also, there is no guarantee that any feature request suggested will be implemented, unless otherwise noted.

==ETA on new updates==

Just like bug fixes and new features, there is never a guaranteed date nor a guaranteed time frame on when new updates will roll out. We work every single day of the week, all the time, on our plugins and thus every day there is something new and improved happening in almost all our plugins daily. Whenever we are ready to release any new updates publicly, you'll find out by seeing the plugin update notice in your WordPress OR in your [http://ithemes.com/member/member.php Member's area].

=What does BETA mean?=

Some of PluginBuddy plugins may be in Beta status OR may have Beta features. BETA simply means that some feature or specific part of the plugin is currently still in testing mode, and can cause issues if not used properly. All BETA plugins/features are not yet 100% stable, and thus should NOT be relied on to be working properly OR working at all. Throughout the iThemes Codex, any time the word "Beta" is used in any form, it refers to Beta plugins, Beta features, Beta status and/or anything related to the Beta nature that is officially announced or mentioned as such by any iThemes staff or on any of the Plugin pages, or in this Codex.

Beta implies that any new features or plugins are very close to being released as 100% working very soon, and that there may still be some issues to fix or test more before removing the Beta status. Since no single software of any kind can be tested under every system and site configuration in the world, the Beta status enables the Beta features to be tested out by as many people on as many different websites and configurations as possible.

*Some points to keep in mind when using any BETA plugin/feature:
**1 : Make [http://pluginbuddy.com/purchase/backupbuddy/ FULL WordPress backups] before using ANY beta feature.
**2 : Beta means that the current software feature is NOT complete, and that you are NOT forced to use such a feature at all. You are advised to WAIT until the BETA status is removed.
**3 : Using any Beta feature of any kind, whether it is an entire plugin or something inside a plugin, means and shows that you are fully accepting any liability for any risks involved.
**4 : Using any Beta feature of any kind, whether it is an entire plugin or something inside a plugin, means and shows that you are fully aware that there are all different kinds of risks involved with such features.
**5 : If you are concerned about your important data or anything bad that might happen as a result of using any Beta feature, do NOT use such Beta features.
**6 : ALWAYS make full [http://pluginbuddy.com/purchase/backupbuddy/ BackupBuddy Backups of all your important data] before using any Beta software, whether that Beta software is from PluginBuddy or from any other place.
**7 : If any issues are found in Beta, they are usually added to the list of bug fixes to be released as a whole, or for the next big update, instead of being updated OR fixed individually on a case by case basis.
**8 : Beta features are recommended to test and play with on test sites/servers and configurations with any dummy data, as long as you have [http://pluginbuddy.com/purchase/backupbuddy/ full backups of all important data] still.
**9 : iThemes is not liable nor cannot be held accountable for any unwanted results resulting from the use of BETA features.
**10 : The very name and nature of BETA shows clearly, without any doubt, that there will most probably be issues and problems involved when such labeled features are used anywhere.
**11 : Support for Beta features may be very limited. We usually simply collect all reports related to Beta features and collect them all for one big update in the future.
**12 : If you lose any important data or settings anywhere, or encounter damaged data or settings anywhere, because of any Beta feature, we will not be able to help you and will simply tell you to revert to your previous [http://pluginbuddy.com/purchase/backupbuddy/ backups]. We will also tell you to always wait for BETA status to be removed before using any such features.

If you do not fully understand what Beta means, OR are not willing to fully accept and be fully liable for any risks involved because of using such Beta software, you should NOT use the Beta software in any manner. In such a case, you should simply wait until the Beta status is removed.

*[http://pluginbuddy.com/what-does-beta-mean/ Blog post announcing what BETA means]

=PluginBuddy Licenses=

==Plugin Conflicts==

Some times, external plugins may cause issues in detaching, deleting, generating OR saving license keys. Such plugins may also cause issues when you want to manually or automatically upgrade plugins when you try to solve licensing issues.

Following is a list of currently known plugins which cause license detaching, deleting, generating OR saving issues. Please disable the following plugins, even temporarily, while you perform all the steps of manually OR automatically upgrading the PluginBuddy plugins in question, and detaching, deleting, generating and saving license keys for them. Keep such plugins disabled UNTIL all license key issues are gone OR at least while you perform these steps.

*Plugins causing PluginBuddy licensing issues
**'''W3 Total Cache or WP Super Cache :''' If you are using any caching plugin like '''W3 Total Cache''' or '''WP Super Cache''', please disable it temporarily and then carry out any required steps. You can re-enable the plugin in the end after everything works in terms of the licenses.
***Fix: Follow the above steps to fix this issue. [http://ithemes.com/forum/index.php?/topic/19436-backupbuddy-license-issue/#p92171 Steps also explained by BackupBuddy customer Laura (thanks!)]
**'''Any other CACHING or related plugin:''' Try disabling such plugins, performing the required steps, and then re-activating the Caching or related plugins in question.

*Related Links
**1 : [http://ithemes.com/forum/index.php?/topic/19079-wont-let-me-set-a-license-key/#p91663 W3 Total Cache plugin conflict and solution]
**2 : [http://ithemes.com/forum/index.php?/topic/19436-backupbuddy-license-issue/#p92171 W3 Total Cache plugin conflict and solution]
**3 : [http://ithemes.com/forum/index.php?/topic/20228-key-does-not-work/#p95697 W3 Total Cache plugin conflict and solution]
**4 : [http://ithemes.com/forum/index.php?/topic/19041-license-problem-causes-loss-of-all-bb-settings-way-to-get-them-back/ WP Super Cache conflict and solution]

==September, 2011 Licensing Issues==

'''This issue is now resolved and the update already out.''' Upgrade manually to the latest versions of the plugins and such issues will go away.

Some users reported (in mid-September, 2011) that they were having issues with their license inside the Licenses area of different PluginBuddy plugins, including BackupBuddy.

Remember: All your PluginBuddy plugins, including BackupBuddy, will CONTINUE WORKING PERFECTLY even with these licensing issues. You can keep using the plugins exactly how you want them even during these licensing issues. Your plugins are NOT affected by this licensing situation in any manner.

Your membership is also completely fine and you have NOT lost any license(s). The issue is happening to some customers who simply need to upgrade manually to the latest version of their plugin, if the automatic upgrade does not work.

*Plugins with the update versions which remove this issue completely
**ALL PluginBuddy Products

*You can upgrade via one of the following:
**Automatically upgrade to the latest version
**Manually update by downloading the latest zip version of your PluginBuddy plugin from your Member's panel and then
***Overwrite your existing plugin directory via FTP with the new files.
***De-activate the existing plugin, delete it via your '''WordPress --> Plugins''' area and then upload the newly downloaded zip file. Then re-activate the plugin.
**That will remove the issue completely.
*DETACH the key and then RE-ATTACH the license key for the specific site in question IF licensing still shows issues AFTER manually upgrading (for example, manually upgrading to at least BackupBuddy 2.2.24 - other plugins have their own new version numbers - check your Member's area for the latest version download)
*Also make sure to DETACH the key, DELETE that same AND any other keys related to that specific site from the entire licenses area, and then GENERATE a new key for that site IF detaching and re-attaching the license key does not work AFTER manually upgrading (for example, manually upgrading to at least BackupBuddy 2.2.24 - other plugins have their own new version numbers - check your Member's area for the latest version download)

[http://ithemes.com/forum/index.php?/topic/6691-read-this-first-pluginbuddy-licensing-issues/page-2/#p85977 First reports]

Tipsy

2011-11-16T20:12:03Z

Bes: Added /* Display iframe inside Tipsy Shortcode */ section

{{#ev:vimeo|30376241|400|right}}

Tipsy is available as a [http://pluginbuddy.com/purchase/tipsy/ stand-alone plugin] or as part of the [http://pluginbuddy.com/purchase/displaybuddy/ DisplayBuddy series]. [http://demos.ithemes.com/tipsy/ See a demo here] or [http://trials.ithemes.com/tipsy/ try it out in WordPress live!]

==Description==
The Tipsy plugin adds the ability to create tooltips for placement in posts or pages. Tooltips are displayed when hovering or clicking on specified content. This allows you to provide additional information to visitors.

==Groups==
The first step in adding Tipsy tooltips to your site is to create a group in the Tipsy settings. Tipsy allows you to create multiple groups with unique settings, styles, and even default tip content.

==Feature Overview==
6 different tooltip layouts to choose from.

Tipsy uses oembed for embedding media within the tooltip. See a list of what media oembed supports [http://oembed.com/ here ]

==Displaying on your site==
To add a Tooltip you will need to first be editing a page or post. Highlight the text/content that you would like to be hovered or clicked to display the tooltip. Then click the Tipsy icon in the WYSIWYG editor. Select the Tipsy group you would like to use and provide the test/content you would like to display within the Tipsy tip. This can be test or other HTML elements, even video.

==Shortcode==
Display your Tipsy in style by using the shortcode <code>[tipsy content="tip content goes here" use_oembed='false' group="0"]content that the tip applies to[/tipsy]</code>. We recommend doing this in the HTML Mode editor.

===Shortcode Parameters===
''content'' · Content that goes inside of the tooltip.
''group'' · group number for the tooltip group that you want to display.
''use_oembed'' . true or false - Whether to embed videos or not (uses oEmbed)

===Display Videos inside Tipsy Shortcode===

Use the following format to show YouTube videos inside the Tipsy tooltip in the HTML Mode editor. Change the video link to any YouTube link you wish:

<code>[tipsy content="http://www.youtube.com/watch?v=FDHNequGw4k" use_oembed='true' group="0"]content that the tip applies to[/tipsy]</code>

===Display Images inside Tipsy Shortcode===

Use the following format to show images inside the Tipsy tooltip in the HTML Mode editor. Change the image link to any image link online:

<code>[tipsy content='<img src="http://pluginbuddy.com/files/2011/10/Tipsy-copy-150x150.png">' group="0" ]content that the tip applies to[/tipsy]</code>

===Display iframe inside Tipsy Shortcode===

Use the following format to show any kind of an iframe inside the Tipsy tooltip in the HTML Mode editor. Change the link and width/height dimensions to your needs:

<code>[tipsy content='<iframe src="http://www.ithemes.com" frameborder="0" width="200" height="110"></iframe>' group="2" ]testing iframes[/tipsy]</code>

*Related link
**http://ithemes.com/forum/index.php?/topic/20204-using-tipsy-to-display-iframe-content/

===SAMPLE Shortcode Text File===

If you are having trouble copy pasting the above code OR not getting it to work, here is a sample TEXT file that you can copy paste from. Simply copy paste the contents into your Page or Post editor, in HTML Mode, test that it works, and then change the links accordingly.

http://bes.internal.ithemes.com/tipsy-media-shortcode.txt

===Special Characters===

If you want to show special characters in your Tipsy, like " @ & % $ and others, simply replace them with their [http://www.utexas.edu/learn/html/spchar.html HTML counterpart ]

==Template Tag==
You can manually call Tipsy if you know the Group ID.

<pre class="brush:php">
<?php
/*
* pb_tipsy()
* Insert a Tipsy tooltip
*
*
* The defaults for the parameter $args are:
* content - Default is an empty string - The content to show in the tooltip
* group - Default is 0 - The Group ID (you can get this from the Tipsy settings)
* filler - Default is an empty string - The text that people hover/click on to view the tooltip
* use_oembed - Default is false - Whether you intend to use oembed to embed a video
*
*
* @param array $args Elements that make up a voting group to insert.
* @return Tip HTML on success */
?>
</pre>
<pre class="brush:php">
<td id="accordion" align="left">
<?php echo pb_tipsy( array(
'content' => 'http://www.youtube.com/watch?v=NfBsRc0R3Ps&hd=1',
'filler' => 'Admin Dashboard',
'group' => 1,
'use_oembed' => true

) ); ?>
</pre>

To see a live example of this template tag in use, please download our Tipsy Page Template (should be able to drop into any theme to test it): [[File:Tipsy.php.zip]]
==Group Settings==
Here is a list of all of the Tipsy settings and a description of what each setting controls.

'''Group Title''' - This setting will allow you to change the title of the group at any time.

'''Tip activation''' - Method upon which the tooltip is activated. Can be set on hover, focus, or click.

'''Tip Position''' - Default orientation tooltip should show up as. You can set it to: "top", "bottom", "left" or "right".

'''Auto hide''' - When set to true the tooltip will only fadeout when you hover over the actual tooltip and then hover off of it.

'''Max width''' - CSS max-width property for the Tipsy element.

'''Edge offset''' - Distances the Tipsy popup from the element with tooltip applied to it by the number of pixels specified.

'''Display delay''' - Number of milliseconds to delay before showing the Tipsy popup after you mouseover an element with tooltip applied to it.

'''Fade in speed''' - Speed at which the Tipsy popup will fade into view.

'''Fade out speed''' - Speed at which the Tipsy popup will fade out of view.

'''Tip Content''' - Default content that goes inside the tooltip itself.

==Customize Tipsy==

===Extra Customizations Policies===
[http://ithemes.com/codex/page/PluginBuddy#Extra_Customizations Check out the official policy and details on any Extra Customizations]

===Edit and/or Create More Layouts===
Tipsy comes with six current layouts that you can choose from to style your Tipsy tooltips. You can edit any existing layout OR create a new one to suit your needs.

Make a [http://pluginbuddy.com/purchase/backupbuddy/ BackupBuddy backup of everything before you proceed], or at least download the existing styles to your computer as a backup. You can also always download the latest Tipsy from your [http://ithemes.com/member/member.php Member's Area], unzip it on your computer and upload only the wp-content/plugins/tipsy/layouts in case you want to restore the default layouts (in case you accidentally mess up something that you want to undo).

*Remember: if you edit any existing default layout that comes with Tipsy, all your changes will be lost when you upgrade Tipsy to any newer version.

=====Edit Existing Layout=====
*To edit any existing layout display:
**Go to wp-content/plugins/tipsy/layouts folder
**Go into the layout you want to edit. Each layout is ordered in the manner it is shown in your Tipsy Group Settings area, from left to right.
**Edit the style.css file in that folder to your liking.
**Save. Your Tipsy will now be shown according to your styling changes in the style.css file.

Note that you will have to edit any existing layout again after upgrades, as upgrading to any new Tipsy version would override the default templates with never versions. It is recommended that you instead create a new layout, as explained below.

=====Create New Layout=====
*To create a new Tipsy layout, you can do one of the following 2:
**1 : Create a new folder in the wp-content/plugins/tipsy/layouts folder
***Put a style.css file in that folder and any image with the name screenshot.png
***Put any form of styling you wish in that style.css file. You can check the existing layout folders to copy paste the styling classes from.
**2 : Duplicate any existing folder in the wp-content/plugins/tipsy/layouts folder and work on that css file.
***Go to the wp-content/plugins/tipsy/layouts folder
****If you are using a control panel like cPanel, duplicate any folder and give it any different name you wish.
****If you are using an FTP program, download any layout folder to your computer, rename it, and then upload it back up.
***Edit the style.css file in that newly duplicated/renamed/uploaded folder to suit your needs.

After you edit any existing layout OR create a new Tipsy layout, simply go into any Tipsy Group Settings and choose the appropriate Layout image for the styling you just worked on in the new folder.

*Remember:
**1 : Each image shown in Tipsy Group Settings page corresponds to the folder order list in the wp-content/plugins/tipsy/layouts folder. So if you click on the 4th image on your Tipsy Group Settings page, you are basically choosing the 4th folder, listed alphabetically, in the wp-content/plugins/tipsy/layouts folder.
**2 : If you edit any existing default Tipsy layout instead of creating a new Tipsy layout, all your changes will be lost when you upgrade to a newer version. Upgrading results in all the default files, including the default templates, to be overwritten also. You will have to redo the changes again if you choose this route. Better option would be to create a new layout as explained above.

===Change color of the arrow in Default layout===

To change the color of the arrow in the Default layout, you want to style the <code>#tiptip_holder.tip_right #tiptip_arrow_inner</code> property.

To do this, edit the '''style.css''' file in the '''wp-content/plugins/tipsy/layouts/default''' folder (OR any folder you have your layout in) and modify (or have) the following:

<pre brush="css">#tiptip_holder.tip_right #tiptip_arrow_inner {
margin-top: -6px;
margin-left: -5px;
border-right-color: rgb(255,0,0);
border-right-color: rgba(255,0,0,0.92);
}
</pre>

Change the <code>250,0,0</code> to your prefer color's RGB code. In the above example, <code>250,0,0</code> is RED.

*Related links
**[http://www.w3.org/TR/css3-color/ Info on CSS3 colors and their RGB codes]
**[http://www.google.com/#hl=en&sugexp=gsihc&cp=8&gs_id=r&xhr=t&q=color+rgb Google search for RGB values of colors]

===Change position of the Tipsy box===

To change the position of the tipsy box, you can either change the "'''''Edge offset'''''" value in Tipsy group settings, or modify the <code>#tiptip_holder</code> property in the style.css file of your folder of the layout you have currently chosen in Tipsy '''wp-content/plugins/tipsy/layouts/YOUR-CHOSEN-LAYOUT-NAME'''

Edit the style.css file and the entire section below to anything you like:

<pre brush="css">#tiptip_holder {
display: none;
position: absolute;
top: 0;
left: 100px;
z-index: 99999;
}</pre>

'''Top''' and '''left''' values change the location of the entire Tipsy tooltip. In the above example, <code>left: 100px;</code> basically moves the entire Tipsy 100 pixels to the right.

==Additional Resources==
# [http://pluginbuddy.com/free-wordpress-plugins/ Free Plugins by PluginBuddy]
# [http://pluginbuddy.com/tutorials/ PluginBuddy Tutorials]
# [http://pluginbuddy.com/ PluginBuddy.com]
# [http://ithemes.com/forum/tipsy/ Tipsy Support Forums]

[[Category:PluginBuddy]]

BackupBuddy: Error Codes

2011-11-14T18:10:12Z

Bes: Added tip and link related to having enough defined storage quota or available disk space available /* 3382 */

==3382==
<strong>Backup FAILED. Unable to successfully generate ZIP archive. Error #3382.12:20:04: Failed function backup_zip_files. Backup terminated.</strong>

* The 3382 error literally means that both command line zip AND pclzip were unable to create a .zip file and failed for some reason.
* Possible causes:
** Command line zip is being actively killed. (Cheapest packages at Godaddy kill off exec() within about 10 seconds, throwing the user into compatibility mode which cannot handle larger sites).
** Permissions may be blocking backup file creation. Make sure permissions are set to 755 for the /wp-content/uploads/ directory recursively.
** Your hosting account may not have enough free space to create the backup file.
** There may be one or more files/folders being included in the backup which neither the native zip command nor the pclzip function are able to access, e.g., unreadable files or broken symbolic links
* Possible solutions:
** If you have BackupBuddy Version 2.2.29 or later then visit the Settings page and enable the Alternative Zip System option and save. Then repeat a Full backup and study the Advanced Details for indications of failure.
*** For the native zip command alternatives there will usually be an exit code followed by some general descriptive text concerning the reason for failure (such as being unable to read a file, lack of disk space, etc.).
*** If the failure is file based then unfortunately at present we are unable to isolate the specific file details from this command. However, the backup will fall back to the Compatibility Mode and the failure indication from that will almost certainly provide a specific indication of the file (including the absolute file path) that is causing the issue. In such a case you must correct the issue by making the file readable if that is appropriate for the file or alternatively use the Exclusions on the Settings page to exclude the folder that contains the bad file.
*** If you cannot make the file readable and you cannot exclude the folder (because it contains other files that you need) then you will need to consult your host support to try and resolve what is the issue with the file.
*** If you are having trouble interpreting the diagnostic information in the Advanced Details then please create a topic in the BackupBuddy Forum and we can help explain it to you - however, this doesn't mean to say that we can resolve the issue as it relates to your files and server.
** Verify permissions are set correctly for /wp-content/uploads/ recursively to 755.
** Verify allowed disk usage isn't close or exceeded. (ie Your hosting account is limited to 5GB and you've used 4.95GB.)
** Reducing backup size often helps. (directory exclusion, etc)
** Turning Zip Compression on or off may help.
** Have at least double the amount of defined storage quota available (or the same amount of free space as your used disk space) so that the backup can be created.
* Related link:
** http://ithemes.com/forum/index.php?/topic/17953-backup-failure/#p85314
** http://ithemes.com/forum/index.php?/topic/20145-another-solution-to-error-3382/

==9001==
'''Unable to read database table wp_redirection_logs. Your backup will not include data from this table (you may ignore this warning if you do not need this specific data). This is due to the following error: MySQL client ran out of memory in /www/wp-content/plugins/backupbuddy/backupbuddy.php on line 1757'''

* '''MySQL client ran out of memory'''
** This is typically caused by your PHP memory limit being low, resulting in part of the data returned being clipped. If you do not need the data from this specific table of the database to be backed up then you may safely ignore this. Some tables, such as wp_redirection_logs, contain logs that you most likely do not need.
** BackupBuddy attempts to increase the PHP memory limit on runtime but many hosts block this.
** Add/modify this line in your php.ini with a higher number than the default, such as: php_value memory_limit 128M
** PHP memory is separate from mysql memory. Your host has to up the mysql memory as it is not possible for you the client to do so at all.
* '''Unable to save result set'''
** This is typically caused by a corrupt database/table. [http://textpattern.com/faq/36/warning-unable-to-save-result-set/ Citation of problem.]
** Repair the database/table using a tool such as phpMyAdmin or the free plugin [http://wordpress.org/extend/plugins/wp-dbmanager/ WP-dbManager]
** Add this line to wp-config.php to allow WordPress to repair tables: define('WP_ALLOW_REPAIR', true)
* '''MySQL server has gone away'''
** MySQL server is dying, this is mostly a host issue. Probably need to contact host to get them to fix the issue.
* WordPress Revisions may also be clogging up the system
** Disabling WordPress' automatic revisions, or at least limiting how many to keep, can help with this error
** http://codex.wordpress.org/Editing_wp-config.php#Post_Revisions

==9002==
'''Unable to create temporary storage directory ((/www/wp-content/uploads/temp_xxxxxxxxxx)'''

*This error means that BackupBuddy was unable to create a temporary storage directory at the location listed in the error message. BackupBuddy must temporarily create this directory to place temporary files to be backed up into the ZIP file.
* Adjust permissions to allow write & directory creation access to your uploads folder. ie: /www/wp-content/uploads/

==9003==

'''BackupBuddy data file (backupbuddy_dat.php) missing or unreadable. There may be a problem with the backup file, the files could not be extracted (you may manually extract the zip file in this directory to manually do this portion of restore), or the files were deleted before this portion of the restore was reached. Start the import process over or try manually extracting (unzipping) the files then starting over. Restore will not continue to protect integrity of any existing data.'''

* This error is often caused by the importbuddy.php script being replaced by an older version during the unzip step. See [http://ithemes.com/codex/page/BackupBuddy:_Frequent_Support_Issues#Old_importbuddy_overwriting_on_unzip|Old importbuddy overwriting on unzip]
* This error is often caused by the server timing out before zip file extraction could complete.
** Manually extract files using either cPanel or extracting (unzipping) the files locally then uploading them & selecting the importbuddy.php advanced option to skip file extraction.
** Ask your server host to extend the maximum script execution time.
** Create a custom php.ini file if your host allows for this.
*** Tutorial: Create custom php.ini & enable in cPanel: http://pluginbuddy.com/tutorials/custom_php_ini/
*** Dreamhost users may use this tool if they do not want to use the above method: http://sxi.sabrextreme.com/dh-phpini
*** Increase php.ini max_execution_time
** Change hosts & let your current host know why you changed.
* Additional potential causes (very rare):
** File permissions not allowing reading of the backupbuddy_dat.php file.
** Incomplete backup. Verify the backup is marked as Good on the source site.

==9004==

'''Error! The unzip process reported success but the backup data file, backupbuddy_dat.php was not found in the extracted files. The unzip process either failed (most likely) or the zip file is not a proper BackupBuddy backup.''' (importbuddy.php)

* Manually extract backup ZIP. This usually resolves this issue.
* Force compatibility mode to see if it able to unzip to completion.
* Contact the host to see if they can verify that the Linux command line ZIP is set up properly.

==9005==

'''File extraction process did not complete successfully. Unable to continue to next step. Manually extract the backup ZIP file and choose to "Skip File Extraction" from the advanced options on Step 1.''' (importbuddy.php)
* This ZIP file was unable to be extracted for some reason.
** Unzipping may have taken too long and the PHP process halted.
** Server memory usage may have been exceeded.
** Server configuration may be blocking extracting of ZIP files.

* Attempt manual extraction & disable File Extraction from the advanced debugging options of Step 1.

==9006==
'''ERROR: Unable to connect to database server and/or log in. Verify the database server name, username, and password.''' (importbuddy.php)
* Verify the server address, your username, and your password. One of these settings is wrong.
* cPanel sometimes prefixes your username with a prefix. Check if this exists.

==9007==
'''Unable to select your specified database. Verify the database name and that you have set up proper permissions for your specified username to access it.''' (importbuddy.php)
* Verify the database name exists.
* Verify the mysql username has been granted ALL permissions to this database.

==9008==
'''ERROR: A database prefix is required for importing.''' (importbuddy.php)
* You must specify a WordPress database table prefix. Default is "wp_" without quotes.

==9009==
'''ERROR: Unable to find any database backup data in the selected backup.''' (importbuddy.php)
* Database file is missing from the backup.

==9010==
'''ERROR: Unable to import SQL query:''' (importbuddy.php)
* Something went wrong attempting to import this row into the database.
* If it says duplicate table or row then the user is importing/migrating into a database that has an existing WordPress installation with the same prefix. This could cause problems if it's a different install or a lot has changed.

==9011==
'''ERROR #9011. FTP/FTPs login failed on scheduled FTP. Credentials: username:password@server.com.'''
* Unable to log in to FTP or FTPs server due to a problem with the login credentials. Verify your username and password.

==9012==
'''FTP/FTPs file upload failed. Check file permissions & disk quota. Details: [additional details here]'''
* BackupBuddy was able to connect to the FTP server but was not able to upload the file.
* Verify file permissions allow writing and that enough disk space is available.

==9013==
'''Sorry! PHP version x.x or newer is required for BackupBuddy to properly run. You are running PHP version x.x.x.'''
* BackupBuddy currently requires PHP 5.x. See the Sales page or [[BackupBuddy]] codex page for the latest version requirements.
* Most hosts allow you to change the PHP version from their control panel.

==9014==
'''Fatal error. The database already contains a WordPress installation with this prefix (27 tables). Restore has been stopped to prevent overwriting existing data. Please go back and enter a new database name and/or prefix OR clear our your database prior to restoring again.'''
* WordPress already exists in the database/prefix combo entered.
* Choose a new prefix, database, or delete the existing WordPress tables from the database.

==9015==
'''Temp data directory is not writable. Check your permissions. (#directory#)'''
* Verify user permissions for this directory. Make sure the user can create & write files.
* Use SUPHP so PHP will run as your user. This insures it will have proper file/directory permissions.

==9016==
'''Archive file is not writable. is not writable. Check your permissions. (#directory#)'''
* Verify user permissions for this directory. Make sure the user can create & write files.
* Use SUPHP so PHP will run as your user. This insures it will have proper file/directory permissions.

==9017==
'''Temp data file is not creatable/writable. Check your permissions. (#directory#)'''
* Verify user permissions for this directory. Make sure the user can create & write files.
* Use SUPHP so PHP will run as your user. This insures it will have proper file/directory permissions.

==9018==
'''Database file is not creatable/writable. Check your permissions. (#directory#)'''
* Verify user permissions for this directory. Make sure the user can create & write files.
* Use SUPHP so PHP will run as your user. This insures it will have proper file/directory permissions.

==9019==
'''Invalid or corrupt AJAX data. (#DATA#)'''
* The backup data sent by the browser was invalid. Refresh and try again.
* Make sure you are using a modern browser on a stable internet connection.

==9020==
'''Unable to write to file [.htaccess/wp-config.php]. Permissions are preventing this file from being modified.'''
* Verify write permissions are properly configured for this file. Suggestion: 755.
* For .htaccess: Another option is to delete the .htaccess file & in the WordPress admin navigate to Settings: Permalinks & click the Save button to regenerate the file.

==9021==
'''PHP Timeout or Fatal Error Occurred'''
* "The page did not finish loading as expected. The most common cause for this is the PHP process taking more time than it has been allowed by your host (php.ini setting max_execution_time). If a PHP error is displayed above this can also cause this error. "
* Increase the maximum allowed PHP runtime by contacting your host or creating a php.ini file to override host settings (if allowed).
* If on the unzip step, manually extract the ZIP file on your local PC then upload or use another server-based software such as cpanel.

==9022==
'''Error: Unable to create backup storage directory `/www/wp-content/uploads/backupbuddy_backups/`. Please verify that proper write permissions are enabled to create this directory. You may also manually create this directory. If you do so make sure to give permissions to allow writing backups into this directory.'''

*This error means that BackupBuddy was unable to create a storage directory at the location listed in the error message. BackupBuddy must create this directory to place backup files into.
* Adjust permissions to allow write & directory creation access to your uploads folder. ie: /www/wp-content/uploads/

==9023==
'''The backup is of a full Multisite Network. You cannot import a Network into a Network. You may only import standalone sites and sites exported from a Multisite.'''
* If you want to import a site from a Multisite Network you must first use BackupBuddy to export a site from it. You can then import that individually exported site into another Multisite Network using BackupBuddy's Multisite Import or even as a standalone site with importbuddy.php.

==5445589==
'''Error #5445589 – Invalid b/u serial Verify b/u directory writer permission'''
*This basically means there was a mismatch where the unique backup serial that ajax passed was not found server-side. There are 3 known reasons and fixes for this.
**1 : Fix the file and folder permissions on all your BackupBuddy folders and the wp-content/uploads folder.
**2 : Increase the available disk space.
**3 : Upgrade to the latest version of BackupBuddy. There have been updates to BackupBuddy to address this error more efficiently.

*Related forum threads
**[http://ithemes.com/forum/index.php?/topic/13796-error-5445589-invalid-backup-serial/ File permissions causing 5445589 error]
**[http://ithemes.com/forum/index.php?/topic/14834-error-5445589-invalid-backup-serial-0i64w23keq-fatal-error/ Increase the available disk space]

==Additional Resources==
# [[BackupBuddy: Advanced Debugging]]
# [http://pluginbuddy.com/purchase/backupbuddy/ Purchase BackupBuddy]
# [http://pluginbuddy.com/tutorials/ PluginBuddy Tutorials]
# [http://pluginbuddy.com/ PluginBuddy.com]
# [http://pluginbuddy.com/support/ Support Forums]

[[Category:PluginBuddy]]

Slideshow

2011-11-11T23:00:36Z

Bes: Added code to show Rotating Text over Slideshow /* Show Image OR Text OVER Slideshow */

{{#ev:youtube|lxlqcjiR9zw|400|right}}
'''Series:''' [[DisplayBuddy]]
==Description==
This plugin add the ability to display image slideshows anywhere on your site with fully customizable animated transitions and advanced effects. Slideshow has two different sliders that you can choose from, Slider and Cycle. Each slider has different animation effects and customizations.

==Slider==
The transitions for this mode focus on slicing up the image into multiple pieces and using those pieces for different transition effects.Since this mode focuses on slicing up the image for transition effects the settings for this mode also allow you to choose how many slices the image is divided into. This mode also offers the ability to display small thumbnail versions of the images in the group as pagination buttons that allow visitors to your site to easily control which image the slider is showing.

'''Animation transition effects'''
* Randomly use different effects
* Slice down
* Slice down left
* Slice up
* Slice up left
* Fold
* Fade

==Cycle==
The transitions for this mode focuses on shuffling images around. This mode has many different effects to choose from, providing more options so that you can pick the effect that you like the best.

'''Animation transition effects'''

blindX, blindY, blindZ, cover, curtainX, curtainY, fade, fadeZoom, growX, growY, scrollUp, scrollDown, scrollLeft, scrollRight, scrollHorz, scrollVert, shuffle, slideX, slideY, toss, turnUp, turnDown, turnLeft, turnRight, uncover, wipe, and zoom.

==Groups==
Carousel has the ability to save multiple groups that can each have different images and settings. The only information required to create a group is a group name.

==Adding Images==
In order to add images you will need to select a group then adjust the "Slide Image Dimensions" width and height so that the Carousel plugin will know what dimensions it will need to resize the images to. After saving the desired image dimensions then you can add an image by clicking the "+Add image" button. Carousel uses WordPress's built in media up-loader. This will allow you to either upload new images or select images that you have already added to the media library. In order to select an image to add from the list of images click the "show" link for that image and then click the "select this image" button as shown in the image below.

[[File:Displaybuddyselectimage.png|408px]]

==Displaying Slideshow on your site==
Slideshow can be added to your site using two different methods, widgets or shortcode.
====Widget====
Navigate to the Widgets area under Appearance in the WordPress Admin area. Drag the Slideshow widget into the widget area that you would like for it to display in and select the group from the drop-down menu that you would like to display.
====Shortcode====
The groups table in slideshow will display a shortcode for each different group that you have created. If you would like to add a Slideshow group to a post or page all you have to do is copy that shortcode and paste it the content of the page or post you would like for it to display in.

==Customize Slideshow==

====Extra Customizations Policies====
[http://ithemes.com/codex/page/PluginBuddy#Extra_Customizations Check out the official policy and details on any Extra Customizations]

====Change Background Color of Caption Text====
Put the following in your theme's CSS file at the very end, changing the color code example used here, #fd4507 which is red, to anything you wish:

<pre brush="css">
.nivo-caption {
background-color: #fd4507 !important;
}
</pre>
*Related links:
**http://ithemes.com/forum/index.php?/topic/18152-background-color/

====Show Image OR Text OVER Slideshow====
You can also show images or texts ON TOP OF (over) a Slideshow so that the slides and the image/text blend in together.

Use the following template to add the necessary code to your theme's css file at the very end.
<pre brush="css">
#builder-module-4e738d2279b5e .builder-module-block { /* Shows any top area TEXT, that is in a widget ABOVE the Slideshow WIDGET< on top of the Slideshow. Change the module # to your own current module # */
position: absolute;
z-index: 2 ! important;
}

#builder-module-4e738d2279b21 img { /* Positions the image in question from a certain Widget module right above the Slideshow. Change this module # to your own widget's module # */
padding-top: 30px ! important;
position: absolute;
z-index: 1 ! important;
}
#pb_slideshow_slider-1 .nivo-slice { /* Prevents the Slideshow transitions from hiding the overlapping text or image. This means NO MORE TRANSITIONS. This will also mean that the styling is applied to Slideshow numbered 1 (one) in your Slideshow admin area. The Slideshow shortcode will show you what number it is. */
display: none;
}
</pre>

*Related link
**http://ithemes.com/forum/index.php?/topic/18317-is-it-possible-to-have-slideshow-run-images-behind-header-title/#p86185

Another example is of using Rotating Text over a Slideshow with the following code:

<pre brush="css">
#pb_slideshow_slider-1 {
z-index: 55;
}
.rotatingtext-wrapper { margin-bottom: -90px !important; z-index: 60;
position: absolute !important;
right: 820px;
top: 350px;
}
</pre>

*Related link
**http://ithemes.com/forum/index.php?/topic/20000-can-i-have-my-words-fly-into-image-in-a-plugin-buddy/

====Change/Remove Empty Space Under Slideshow OR Change Slideshow Height====

If you want, you can customize the height of your Slideshow so that it can also change or remove the empty space under Slideshows.

Use the following css styling template in your theme's css file:
<pre brush="css">
#builder-module-4e74d5b55108d .builder-module-block-outer-wrapper { /* This will change the entire Builder widget, in which the Slideshow is, to a height of 250px. Be sure to change the module # to your own current module # in question. You can change the 250px height to anything you want. */
height: 250px !important;
}
</pre>

*Related link
**http://ithemes.com/forum/index.php?/topic/18317-is-it-possible-to-have-slideshow-run-images-behind-header-title/#p86698

====Change or Remove Slideshow Shadows====

You can change OR remove the slideshow shadows, regardless of the Shadow settings in your Slideshow groups.

To remove the shadow completely, put the following in your theme's css file:

<pre brush="css">
.nivoSlider {
-moz-box-shadow:0px 0px 0px #333 !important;
-webkit-box-shadow:0px 0px 0px #333 !important;
box-shadow:0px 0px 0px #333 !important;
}
</pre>

To change the color or size of the shadows instead of removing them, change the #333 to any other color, and the "0" to any number you want for the size of the shadow.

*Related links
**[http://www.webmonkey.com/2010/02/color_charts/ Color hex codes]
**[http://ithemes.com/forum/index.php?/topic/19434-cannot-remove-shadow-around-slideshow/ Client shadow question and answer]

==FAQ==

====Absolute Links====
Currently, you must use absolute links in Slideshow is order for them to be processed and to be shown.

For example, using <code>/support</code> will NOT work. However, <code>http://www.ithemes.com/support</code> will work.

==Additional Resources==
# [http://pluginbuddy.com/free-wordpress-plugins/ Free Plugins by PluginBuddy]
# [http://pluginbuddy.com/tutorials/ PluginBuddy Tutorials]
# [http://pluginbuddy.com/ PluginBuddy.com]
# [http://pluginbuddy.com/support/ Support Forums]

[[Category:PluginBuddy]]

Tabber Widget

2011-11-10T19:29:23Z

Bes: Making Tabber Widget Compatible with different themes

==Customize Tabber Widget==

====Extra Customizations Policies====
[http://ithemes.com/codex/page/PluginBuddy#Extra_Customizations Check out the official policy and details on any Extra Customizations]

====Adjust Height of TabberWidget OR Specific Tabs====

You can easily adjust the height of each Tab inside the TabberWidget OR the entire Tabber Widget wrapper itself. Use the following styling template and customize the height to your own needs, and then put it in your theme's css file at the very end:

<pre code="css">
#tabber_widget-4-content, #tab-tabber_widget-4-1, #tab-tabber_widget-4-2, #tab-tabber_widget-4-3
/* tabber_widget-4-content is the TabberWidget in question, tab-tabber_widget-4-1 is the first tab, tab-tabber_widget-4-1 is the second tab, and so on. Make sure you change the actual tabber_widget-4-content and tab-tabber_widget-4 to your own tabberwidget id. */
{
height: 350px;
}
</pre>

*Related link
**http://ithemes.com/forum/index.php?/topic/18291-tabber-widget-not-displaying-tab-content/

====Place icons Or images before Tab Titles====

It is currently VERY easy to place any icon or image before a Tab Title.

*Steps for placing icons/images before Tab Titles
**1 : Create a Tabber Widget
**2 : Edit the Tabber Widget in question
**3 : Right before the actual title, place the image html code.
***Example, instead of "Your Title", put in "<code><img src="http://www.google.com/imagelink.jpg"> Your Title</code>" Replace that link and image name with your own link and image that you want to use.
**4 : Save. All done!

That will show the image right before your title.

*Related link
**http://ithemes.com/forum/index.php?/topic/18669-how-to-place-a-social-networking-icon-in-a-tabber-widget-tab/

====Change Number of Tabs====

By default, TabberWidget allows a maximum of 10 tabs to be used in the Widgets section at one time.

*You can change this number to any other number if you wish by following these steps:
**1 : Open the editor.php file in the wp-content/plugins/tabber-widget folder.
**2 : Replace 10 with the number you wish. Following are your options on how to do this:
***2A : Search for and replace 10 in that entire file with any other number you wish, depending on the number of tabs you want in Tabber Widget.
***2B : OR you can change the "10" to any other number, without the quotes, on the following 4 lines:
****1 : Line 107
****2 : Line 189
****3 : Line 225
****4 : Line 273
**3 : Save. You're done.

This MAY result in your TabberWidget settings area to look different or strange because of the number of Tabs you choose above. However, you will still get the different number of tabs you wish with this method.

*Related thread
**http://ithemes.com/forum/index.php?/topic/19201-need-more-than-10-widgets-in-tabber/

====Making Tabber Widget Compatible with different themes====

Sometimes, because of Tabber Widget having tabs and because of all modern themes supporting widgets, there may be conflicts with themes where the tab styling or names may have conflicts. In such cases, focus on changing the conflicting names of the classes or properties.

*[http://ithemes.com/forum/index.php?/topic/8892-using-tabber-with-headway/#p94318 Example of making Tabber Widget compatible with Headway Themes]

==Additional Resources==
# [http://pluginbuddy.com/free-wordpress-plugins/ Free Plugins by PluginBuddy]
# [http://pluginbuddy.com/tutorials/ PluginBuddy Tutorials]
# [http://pluginbuddy.com/ PluginBuddy.com]
# [http://pluginbuddy.com/support/ Support Forums]

[[Category:PluginBuddy]]

LoopBuddy

2011-11-04T22:01:33Z

Bes: Clarified the loopbuddy plugin folder location /* Change OLDER POSTS and NEWER POSTS pagination text */

'''Release date:''' July 19, 2011

==LoopBuddy Overview==

LoopBuddy is a tool that overwrites a WordPress Loop using a combination of a custom query and a custom Loop layout. You can also create your own Loops using the LoopBuddy shortcode and LoopBuddy widget.

===Query Editor===

If LoopBuddy was a body, the Query Editor would be the brain, with the Layout Editor being the outside bodily appearance.

[[File:Query_editor.png|400px|border|LoopBuddy Query Editor]]

With the Query Editor, you can create Query Groups. Each Query Group defines what data a WordPress Loop is supposed to pull in.

With the Query Editor, you can define:

* Which posts to gather
* Whether pagination or comments are enabled
* Whether to use the default post ID (if on a single post or page)
* and much, much more...

[[File:Query_editor_options.png|400px|border|Query Editor Options]]

===Layout Editor===

The Layout Editor controls how a particular WordPress Loop is supposed to be structured. At the heart of the Layout Editor is Layout Tags. There are several Layout Tags built-in, but you can use the LoopBuddy Hooks to create your own custom Layout Tag and Layout Tag Items.

[[File:Layout_editor.png|400px|border|LoopBuddy Layout Editor]]

With the Layout Editor, simply drag Layout Tags into the appropriate area. If you create a new Layout, there are several default tags that are added automatically.

[[File:Layout_editor_options.png|500px|border|Layout Editor Options]]

===Global Settings===

The Global LoopBuddy Settings allow you to globally override a default WordPress Loop. If your theme doesn't support the Loop Standard, you'll see an error message at the top.

If your theme does support the Loop Standard, you can use the options to override the default WordPress Loops in various areas of the site.

Although LoopBuddy attempts to work without a custom Query, it is highly advisable to use a custom Query and Layout.

[[File:Loopbuddy_settings.png|500px|border|General Settings]]

===Import/Export===

Within the Query and Layout editors, you can export/import the items so you can use the same Queries/Layouts on a different site.

===LoopBuddy Widget===

You can use the LoopBuddy Widget to display a LoopBuddy Query/Layout in any widgetized area of a site. Please note that you must have a Query AND a Layout for the widget to work.

===LoopBuddy Shortcode===

The LoopBuddy shortcode takes two attributes: a Query ID and a Layout ID. Please note that you must have a Query AND a Layout for the widget to work.

Simply insert the shortcode into a post or page:

<pre class='brush:php'>
[loopbuddy query_id='0' layout_id='0']
</pre>

===LoopBuddy Full 1 Hour Webinar===

Learn the ins and outs of LoopBuddy with the following 1 hour Webinar, made by our very own [http://www.webdesign.com Webdesign.com]
{{#ev:vimeo|26482158|580|363}}

==The Loop Standard==
The Loop Standard divides a loop into two main concepts: a loop and one or more entries.

Both a loop and an entry have three sections: a header, a content section, and a footer. The header contains title information, any meta information, and any necessary navigation links. The content section contains the content relevant to that loop or entry. The footer section is a place to hold additional or duplicate meta information and navigation links.

===The Loop Explained===

The content of a loop is a bit more complex than the content of an entry as a loop's content contains the entries. To better visualize this, here is the basic structure described so far:

* Loop
** Header
*** title
*** navigation
*** meta
** Content
*** Entry
**** Header
***** title
***** navigation
***** meta
**** Content
**** Footer
***** navigation
***** meta
*** Additional entries...
*** Footer
**** navigation
**** meta

The idea is that each section is broken out in a repeatable pattern. This makes styling easier as any content that follows this form can be styled without having to first read through the code in order to understand the structure.

You may notice that there are titles, navigation, and meta for both the entries and the loop. This is because some titles, navigation, and meta are relevant to the loop (the title archive, navigating between pages of posts, or information about an author in an author archive) while other titles, navigation, and meta are relevant to the entry (the blog post's title, navigating through a page split into multiple pages, or a blog post's category information). The rule of thumb is that if the information is specific to an individual post's, page's, etc content, it is an entry-level structure; otherwise, it is a loop-level structure.

Each of these sections have a specific class in the Loop Standard. Here is the structure again with the classes replacing the names:

* loop
** loop-header
*** loop-title
*** loop-utility
*** loop-meta
** loop-content
*** hentry
**** entry-header
***** entry-title
***** entry-utility
***** entry-meta
**** entry-content
**** entry-footer
***** entry-utility
***** entry-meta
*** hentry...
** loop-footer
*** loop-utility
*** loop-meta

Notice the "hentry" class. This looks odd but is actually generated by WordPress internally. It is produced by the <code>post_class()</code> function that is in 2010 and 2011 theme template files. So when you see "hentry", know that this is simply the div that looks like :

<pre class='brush:php'>
<div <?php post_class(); ?>></div>
</pre>

Here is the standard loop in practice:
* loop
** loop-header
*** loop-title (page-title)
** loop-content
*** hentry
**** entry-header (title)
***** entry-title (post-title)
***** entry-meta (post-meta)
***** entry-meta date (date)
**** entry-content (post-content)
**** entry-footer (meta-bottom)
***** entry-meta alignright (alignright)
***** entry-meta alignleft (meta-bottom-left)
*** hentry...
** loop-footer
*** loop-utility (paging)

Not all the elements from above structure examples were used since not all were needed. In the end, only three elements had to be added. The rest of the changes were simply modifying or adding classes to conform to the Loop Standard structure. For some elements, such as "date", the "date" class remained while also getting the "entry-meta" class. This makes it clear what type of structure it is while still giving the additional meaning of it being a container for the date.

===Modifying a Theme to Use LoopBuddy===

Here's an example of TwentyTen's index.php file before it begins loading the various templates:

<pre class='brush:php'>
<?php if ( ! dynamic_loop() ) : ?>
<div class="loop">
<?php
/* Run the loop to output the posts.
* If you want to overload this in a child theme then include a file
* called loop-index.php and that will be used instead.
*/
get_template_part( 'loop', 'index' );
?>
</div>
<?php endif; ?>
</pre>

When <code>dynamic_loop()</code> is executed, LoopBuddy searches to see if this particular loop should be overridden. If not, the normal loop executes. If so, then LoopBuddy overwrites the content of the loop with LoopBuddy content.

===Example of TwentyTen Using the Loop Standard===
Here's an example TwentyTen Loop converted to using the Loop Standard

<pre class='brush:php'>
<?php if ( have_posts() ) while ( have_posts() ) : the_post(); ?>

<div class="loop-content">
<div id="nav-above" class="navigation loop-utility loop-utility-above">
<div class="nav-previous"><?php previous_post_link( '%link', '<span class="meta-nav">' . _x( '←', 'Previous post link', 'twentyten' ) . '</span> %title' ); ?></div>
<div class="nav-next"><?php next_post_link( '%link', '%title <span class="meta-nav">' . _x( '→', 'Next post link', 'twentyten' ) . '</span>' ); ?></div>
</div>

<div id="post-<?php the_ID(); ?>" <?php post_class(); ?>>
<div class="entry-header">
<h1 class="entry-title"><?php the_title(); ?></h1>

<div class="entry-meta">
<?php twentyten_posted_on(); ?>
</div>
</div>
<div class="entry-content">
<?php the_content(); ?>
<?php wp_link_pages( array( 'before' => '<div class="page-link">' . __( 'Pages:', 'twentyten' ), 'after' => '</div>' ) ); ?>
</div>
<div class="entry-footer">
<?php if ( get_the_author_meta( 'description' ) ) : // If a user has filled out their description, show a bio on their entries ?>
<div id="entry-author-info" class="entry-meta entry-meta-below">
<div id="author-avatar">
<?php echo get_avatar( get_the_author_meta( 'user_email' ), apply_filters( 'twentyten_author_bio_avatar_size', 60 ) ); ?>
</div>
<div id="author-description">
<h2><?php printf( esc_attr__( 'About %s', 'twentyten' ), get_the_author() ); ?></h2>
<?php the_author_meta( 'description' ); ?>
<div id="author-link">
<a href="<?php echo get_author_posts_url( get_the_author_meta( 'ID' ) ); ?>">
<?php printf( __( 'View all posts by %s <span class="meta-nav">→</span>', 'twentyten' ), get_the_author() ); ?>
</a>
</div>
</div>
</div>
<?php endif; ?>

<div class="entry-utility">
<?php twentyten_posted_in(); ?>
<?php edit_post_link( __( 'Edit', 'twentyten' ), '<span class="edit-link">', '</span>' ); ?>
</div>
</div>
</div>
<div class="loop-footer">
<div id="nav-below" class="navigation loop-utility loop-utility-below">
<div class="nav-previous"><?php previous_post_link( '%link', '<span class="meta-nav">' . _x( '←', 'Previous post link', 'twentyten' ) . '</span> %title' ); ?></div>
<div class="nav-next"><?php next_post_link( '%link', '%title <span class="meta-nav">' . _x( '→', 'Next post link', 'twentyten' ) . '</span>' ); ?></div>
</div>
</div>

<?php comments_template( '', true ); ?>
</div>

<?php endwhile; // end of the loop. ?>

</pre>

After updating the template files, go through the theme's style.css file in order to update class references to match the new ones. Here are some basic replacements to make:

* .page-title → .loop-title
* .title → .entry-header
* .post-title [h1, h2, h3, etc] (any instance of .post-title followed by a header tag) → .entry-title
* .post-title → .entry-title
* .post-meta → .entry-meta
* .post-content → .entry-content
* .meta-top → .entry-header
* .meta-bottom → .entry-footer
* .post → .hentry
* .paging → .loop-utility

===Showing LoopBuddy Theme Support===

After you've modified your theme's loops, show LoopBuddy that your theme supports it by adding in the following line to your theme's functions.php file:

<pre class='brush:php'>
// Add support for the Loop Standard
add_theme_support( 'loop-standard' );
</pre>

===Adding the Dynamic Loop Function to Your Theme===
The Dynamic Loop function must be added to your theme's functions.php file. This is achieved by adding the following code to the end of the function.php file:

<pre class='brush:php'>
// Add dynamic_loop function for LoopBuddy

/*
Copyright 2011 iThemes (email: support@ithemes.com)

Written by Chris Jean
Version 0.0.1

Version History
0.0.1 - 2011-02-28 - Chris Jean
Initial version
*/

if ( ! function_exists( 'dynamic_loop' ) ) {
function dynamic_loop() {
global $dynamic_loop_handlers;

if ( empty( $dynamic_loop_handlers ) || ! is_array( $dynamic_loop_handlers ) )
return false;

ksort( $dynamic_loop_handlers );

foreach ( (array) $dynamic_loop_handlers as $handlers ) {
foreach ( (array) $handlers as $function ) {
if ( is_callable( $function ) && ( false != call_user_func( $function ) ) ) {
return true;
}
}
}

return false;
}
}

if ( ! function_exists( 'register_dynamic_loop_handler' ) ) {
function register_dynamic_loop_handler( $function, $priority = 10 ) {
global $dynamic_loop_handlers;

if ( ! is_numeric( $priority ) )
$priority = 10;

if ( ! isset( $dynamic_loop_handlers ) || ! is_array( $dynamic_loop_handlers ) )
$dynamic_loop_handlers = array();

if ( ! isset( $dynamic_loop_handlers[$priority] ) || ! is_array( $dynamic_loop_handlers[$priority] ) )
$dynamic_loop_handlers[$priority] = array();

$dynamic_loop_handlers[$priority][] = $function;
}
}

</pre>

==LoopBuddy Downloads==

===Example TwentyEleven Theme===

Here's an example TwentyEleven theme that has been modified to be compatible with LoopBuddy.

[[Media:twentyeleven-loopstandard.zip|TwentyEleven Loop Standard]]

===Example Layout Tag===

Check out the LoopBuddy Marquee Plugin: [[Media:Loopbuddy_marquee.zip|LoopBuddy Marquee]] as an example of creating custom tags.

===Example Queries/Layouts===

Please see below for a ZIP file of some sample layouts and queries that can be imported.

[[Media:Loopbuddy_export.zip|LoopBuddy Export File]]

==LoopBuddy Query==
The LoopBuddy Query is where you create Queries, which in turn create and produce the Loops you want in WordPress. From showing certain posts to the number of posts, categories, posts with specific meta values and more, the '''LoopBuddy Query''' area is where you specify exactly what should be shown, and exactly what should not be shown, in a LoopBuddy output.

===Advanced Meta Queries===

With LoopBuddy 1.2, LoopBuddy Queries now allow you to perform some very powerful advanced Meta queries. Here is a video explaining and giving some examples of the advanced meta queries:

{{#ev:youtube|4snQn7PDylE|580|363}}
*[http://pluginbuddy.com/loopbuddy-1-2-released/ Blog Post announcing Advanced Meta Queries in LoopBuddy 1.2]

===Advanced Taxonomy Queries===

With LoopBuddy 1.2, LoopBuddy Queries now allow you to perform some very powerful advanced Taxonomy queries. Here is a video explaining and giving some examples of the advanced Taxonomy queries:

{{#ev:youtube|ta0GZA5jz9g|580|363}}
*[http://pluginbuddy.com/loopbuddy-1-2-released/ Blog Post announcing Advanced Taxonomy Queries in LoopBuddy 1.2]

==Hooks==

LoopBuddy allows you to create custom tags for the Layout editor. This is advanced functionality, so please don't attempt these steps if you are not intimately familiar with PHP and how LoopBuddy operates.

To create the custom tag, you must use the following hooks.

===Creating a new Custom Tag===

<pre class="brush:php">
<?php
add_filter( 'pb_loopbuddy_custom_tags', 'my_custom_tag_add' );
function my_custom_tag_add( $custom_tags ) {
//Always return $custom_tags
$custom_tags[ 'start_wrap' ] = array(
'My Tag Label',
array(
'wrap' => 'div',
'custom_class' => 'default class'
)
);
return $custom_tags;
} //end my_custom_tag_add

//Start off with the tag name, give the tag a label, and pass it which items it supports (all should ideally contain the 'wrap' and 'custom_class' items
?>
</pre>

Here are some built in tag items that you can choose from:

* link_text
* custom_url
* custom_class
* link_title
* before_text
* after_text
* meta_key
* max_width
* max_height
* shortcode
* author_link_destination
* user_profile
* permalink
* attachment_link_display
* separator
* text
* date_format
* comment_number_zero
* comment_number_one
* comment_number_more
* post_date
* bloginfo
* content_more
* url_display
* image_size

===Creating a new custom tag item===

<pre class='brush:php'>
<?php
add_filter( 'pb_loopbuddy_tag_items', 'my_custom_item_add' );
function my_custom_item_add( $loopbuddy_items ) {
//Always return $loopbuddy_items

$loopbuddy_items[ 'my_custom_item' ] = array(
'function' => 'callback_function',
'args' => array(
'label' => __( 'Link Text', 'LION' ),
'tip' => __( 'Optional text for link. Leave blank to use link as the text.', 'LION' ),
'options' => array( 'option1', 'option2' )
)
);
return $loopbuddy_items;
} //end my_custom_item_add

/* $settings are the arguments passed for the tag item and looks like this
[label] => HTML Wrapper
[tip] => Choose which HTML element to wrap around the item
[options] => Array
(
[0] => none
[1] => span
[2] => div
[3] => p
[4] => h1
[5] => h2
[6] => h3
[7] => h4
[8] => h5
[9] => h6
)

[key] => wrap
[settings] => Array
(
[image_size] => thumbnail
[max_width] =>
[max_height] =>
[wrap] => p
[before_text] =>
[after_text] =>
[custom_url] =>
[custom_class] => attachment
[tag] => wp_get_attachment_image
)

)
*/
function callback_function( $settings ) {
$defaults = array(
'key' => '',
'label' => '',
'tip' => false,
'settings' => array(),
'options' => array()
);
extract( wp_parse_args( $settings, $defaults ) );
//Output HTML for the item
} //end callback_function

?>
</pre>

===Callback function for displaying the tag - pb_loopbuddy_tag_callback-{tag_name}===
<pre class='brush:php'>
<?php
/*$settings contains the tag items and the tag item's value
Example
Array
(
[image_size] => thumbnail
[max_width] =>
[max_height] =>
[wrap] => p
[before_text] =>
[after_text] =>
[custom_url] =>
[custom_class] => attachment
[tag] => wp_get_attachment_image
)
*/

//Add header code
add_action( 'pb_loopbuddy_tag_header-mytagname', 'my_custom_tag_header' );
function my_custom_tag_header( $settings ) {
echo "my header, notes, or other code";
//Render your tag based on its settings
} //end my_custom_tag_header

//Add footer code
add_action( 'pb_loopbuddy_tag_footer-mytagname', 'my_custom_tag_footer' );
function my_custom_tag_footer( $settings ) {
echo "my footer, notes, or other code";
//Render your tag based on its settings
} //end my_custom_tag_header

add_filter( 'pb_loopbuddy_tag_supports-mytagname', 'my_custom_tag_supports' );
//Return an array of what tag items the tag supports
function my_custom_tag_supports( $support_tag_items ) {
return array( 'wrap', 'link_text', 'before_text', 'after_text', 'custom_class' );
//Render your tag based on its settings
} //end my_custom_tag_supports
?>
</pre>

===Rendering the Tag on the Front-end - pb_loopbuddy_render-{tag_name}===

<pre class="brush:php">
<?php
add_filter( 'pb_loopbuddy_render-mytagname', 'mytagname_frontend', 10, 2 );
function mytagname_frontend( $post_object, $tag_items ) {
/* $tag_items look like this
(
[wrap] => none
[link_text] => Edit Post
[before_text] =>
[after_text] =>
[custom_url] =>
[custom_class] =>
[tag] => edit_post_link
)
*/
$return = false; //Populate the $return variable
$return = pluginbuddy_loopbuddy_render_slotitems::get_output( $return, $post_object, $tag_items, true ); //The last argument is skip_before text
return $return;
} //end mytagname_frontend
?>
</pre>

===Ignoring Post Types in the Layout Editor===

There will be certain post types that are public and have a public user interface, but the user would still not like to be able to configure override settings in the LoopBuddy Settings page.

A plugin author can use the following hook to remove these post types:

<pre class="brush:php">
<?php
add_filter( 'pb_loopbuddy_exclude_post_types', 'myplugin_exclude_post_types' );
function myplugin_exclude_post_types( $post_types_to_exclude ) {
$post_types_to_exclude[] = 'my_custom_post_type';
return $post_types_to_exclude;
}
?>
</pre>

==Shortcodes==

Shortcodes basically allow almost any plugin or custom code to be plugged in anywhere in WordPress.

LoopBuddy supports shortcodes fully, allowing you to put any shortcode, whether from a plugin or your own, into any place in LoopBuddy Layout, including the '''Pre-Loop Text / HTML''', '''Post-Loop Text / HTML''' and '''No Results Text / HTML''' sections. This probably makes the already powerful LoopBuddy the only most powerful way to control all your content, loops and display on your site.

[http://ithemes.com/codex/page/General_WordPress_Related#Editing_or_Adding_Stuff_to_Functions.php Info on editing or adding stuff to Functions.php]

===Show Category/Taxonomy Description on NON-Archive pages via Shortcode===

Category Descriptions are a little more sophisticated than other post related variables because if there is more than one category being used, then it will be hard for WordPress to display ALL descriptions nicely OR one category (which one?).

*Outside of archive pages, to display Category Descriptions (or any taxonomy description) you have to do the following:
**1 : Put the following anywhere (usually near the end of the file) in your theme's custom functions.php file (it creates a shortcode you'll use to display the description of a Category or any Taxonomy):
<pre class="brush:php">add_action( 'init', 'lb_cat_init' );
function lb_cat_init() {
add_shortcode('taxdescription', 'lb_the_description');
} //end lb_cat_init
function lb_the_description() {
global $post;
if ( !is_object( $post ) ) return;
$terms = get_post_meta( $post->ID, 'description_terms', true );
$taxonomy = get_post_meta( $post->ID, 'description_taxonomy', true );
$return = '';
if ( $terms && $taxonomy ) {
if ( !is_array( $terms ) ) {
$terms = explode( ',', $terms );
}
foreach ( $terms as $term_name ) {
$term = get_term_by( 'slug', $term_name, $taxonomy );
if ( !$term ) continue;
$description = get_term_field( 'description', $term->term_id, $term->taxonomy );
if ( empty( $description ) || !$description ) continue;
$return .= apply_filters( 'pb_the_content', $description );
}
}
return $return;
} //end lb_the_description</pre>
**2 : In the posts you want to show the category description, add the following 2 custom field names and values:
'''Custom Field Name''' ----- '''Custom Field Value'''

description_taxonomy ----- category

description_terms ----- books '''''(OR any category name you have)'''''

**3 : Add a Shortcode Tag to your LoopBuddy layout which has the following shortcode in it:

<code><strong>[taxdescription]</strong></code>

That will show the category description anywhere you put the shortcode.

*Links with related info:
**[http://ithemes.com/forum/index.php?/topic/18153-use-of-category-description/ Use of Category Description - LoopBuddy Forums]
**[http://codex.wordpress.org/Function_Reference/category_description category_description on WordPress Codex]
**[http://codex.wordpress.org/Function_Reference/term_description term_description on WordPress Codex]

===Show Custom Page Title for Same LoopBuddy Layout on Different Pages via Shortcode===

*One awesome example of using Shortcodes with LoopBuddy is to show a custom page title, along with any LoopBuddy Layout content, where different pages use the same LoopBuddy Layout. Our awesome LoopBuddy customer Bruce provided the following info to help you all with that:
**1 : Put the following anywhere (usually near the end of the file) in your theme's custom functions.php file:
<pre class="brush:php">
function return_title() {
return '<h1>'.get_the_title().'</h1>';
}
add_shortcode('pg_title', 'return_title');</pre>
**2 : Add
<code><strong>[pg_title]</strong></code>

anywhere in the LoopBuddy Layout where you want to show the custom page title.

That will show the custom page title just for that specific post/page where the Layout is being shown.
*Related links:
**[http://ithemes.com/forum/index.php?/topic/18046-displaying-the-page-title-on-which-i-am-using-loop-buddy/ LoopBuddy user Bruce asking about and then sharing the code to show custom Page Titles on each Page where the same LoopBuddy Layout is used]

==External Plugins Compatibility==

LoopBuddy is one of those rare plugins which can play well with many external plugins. However, any external plugin compatibility is NOT guaranteed in any manner, since external plugins are not covered nor supported by PluginBuddy in any manner or fashion.

If there is a problem when any other plugin is used with LoopBuddy, it does not mean there is a bug in LoopBuddy. First you should check if there is a problem in the other plugin (since LoopBuddy already currently works without any issues in each and every aspect of its publicized features). Then you have to see if the problem exists when the other plugin is de-activated and LoopBuddy is kept activated. Only after such steps and more analysis can we at PluginBuddy devote any time or resources to see whether or not there is something in LoopBuddy that can be fixed, enhanced or improved to make it work better with the external plugin in question, if that external plugin is not the source of the problem.

===Custom Post Types===
At this time, Custom Post Types UI is the only supported plugin in LoopBuddy for creating custom post types. We recommend you try and use that to create post types.

Otherwise, you should add custom post types directly to your functions.php file in your current theme.

*Related links
**[http://wordpress.org/extend/plugins/custom-post-type-ui/ Custom Post Types UI plugin]
**[http://codex.wordpress.org/Post_Types Creating Post Types in WordPress]

===Page Navigation===

At this time, WP-PageNavi is the only supported plugin in LoopBuddy for having custom page navigation. We strongly recommend you try it for any of your custom page navigation needs.

*Related link
**[http://wordpress.org/extend/plugins/wp-pagenavi/ WP PageNavi WordPress Plugin]

===Customize Excerpts===

At this time, Advanced Excerpt is the only supported plugin in LoopBuddy for allowing custom lengths and formatting for excerpts in WordPress.

*Related link
**[http://wordpress.org/extend/plugins/advanced-excerpt/ Advanced Excerpt WordPress Plugin]

==LoopBuddy FAQ==

Here are some frequently asked or encountered LoopBuddy questions and setups, and their answers.

===Sort Custom Field Values by Meta Value (Character or Numeric)===

*Custom Field values can be sorted by meta value (character or numeric).
*Only ONE meta item can be used to sort at one time.
**Using multiple meta items will assume you would like an advanced meta query, and sorting will be ignored in such a case. '''This is a WordPress limitation.'''
*Sort Custom Field Values via the following steps (assuming you already have several posts with the same custom field):
**1 : Change the Order By parameter to either "'''Meta Value'''" or "'''Numeric Meta Value'''".
**2 : Go to Post Meta Parameters and click "'''Add Meta'''".
**3 : Set the '''Meta Key''' and '''Meta Values''' you would like to search for and sort by.
**4 : Save the query.
**5 : Assign the query to a post or section and observe the results.

===LoopBuddy does not work on static Posts page===

*LoopBuddy will NOT work on pages set as Static Posts Page in '''WordPress --> Settings --> Reading --> Front Page Displays --> Posts Page''' section. There is a good reason for it and a great workaround.
** Reason
***The Reading Screen in the WordPress Settings [http://codex.wordpress.org/Settings_Reading_Screen Settings --> Reading Screen Settings] is necessary when you want to tell WordPress that your blog content doesn't reside on the home page.
***For example, you have selected a Front Page, which will tell WordPress, "Use this page instead of showing a default blog layout."
***Since there is technically no longer a blog layout, WordPress wants to know, "Where can I find your blog content?"
***This is how WordPress works, and not a LoopBuddy bug. There is a great flawless way to get exactly what you want with the below workarounds, though.
**Workaround (any one of this will work - we recommend the PREFERRED LoopBuddy way to do it!)
*** Not have a section on your site with your blog content (readers will only be able to access your posts via category and date archives).
*** Create a page to point WordPress to, and WordPress will take care of the rest and display the appropriate blog content.
*** '''PREFERRED:''' With LoopBuddy, however, you don't have to specify a "Blog" section in WordPress.
**** You can create a regular page.
**** Allow LoopBuddy to create a blog section for you either via '''LoopBuddy --> Settings''' option OR by choosing the '''LoopBuddy options in the Post/Page Editor page''' for the page you just created.
**** WordPress doesn't need to know about it in this particular case, and it won't hurt your site in the least. You do NOT have to change the '''WordPress --> Settings --> Reading --> Front Page Displays --> Posts Page''' settings for this option to work perfectly.
*Threads and pages with more detailed info of the setup and info related to the above exact solutions
**http://ithemes.com/forum/index.php?/topic/17845-unable-to-get-loopbuddy-working/
**http://codex.wordpress.org/Settings_Reading_Screen

===Make a Custom Field (or almost anything) Clickable===
With the power of different tags in LoopBuddy Layout, you can make almost anything clickable without editing a single file. This is extremely useful when you want to make something like a Custom Field, which is text by default, clickable automatically in any or every loop.
*Steps to perform in your LoopBuddy Layout:
**1 : Start with a Text tag (first Text tag) which has the content: <code><a href="</code>
**2 : Next comes anything, including a Custom Field tag. This is the link.
**3 : Now comes another Text tag (second Text tag) which has the content: <code>"></code>
**4 : Now comes anything to show the link. It can be the same Custom Field tag again as #2 above, another custom field, or any text or image you wish.
**5 : Another Text tag (3rd Text tag) with the following content: <code></a></code>
That's it!
*Related thread
**http://ithemes.com/forum/index.php?/topic/16971-text-before-single-custom-field-and-url/

===Search within a LoopBuddy Query===

You can have search widgets which actually search specific LoopBuddy queries for the parameters you specify. There are many different ways of achieving this with LoopBuddy.

Check out the forum thread [http://ithemes.com/forum/index.php?/topic/16606-searching-within-a-loopbuddy-query/ Searching Within a LoopBuddy Query] for more details.

===Change OLDER POSTS and NEWER POSTS pagination text===

You can change the "'''Older posts'''" and "'''Newer posts'''" text to say anything by editing those words in your '''''wp-content/plugins/loopbuddy/loopbuddy.php''''' file on lines 1336 and 1337. They will look like the following:

<pre brush="php">
div class="nav-previous"><?php next_posts_link( __( '<span class="meta-nav">←</span> Older posts', 'it-l10n-loopbuddy' ) ); ?></div>
<div class="nav-next"><?php previous_posts_link( __( 'Newer posts <span class="meta-nav">→</span>', 'it-l10n-loopbuddy' ) ); ?></div>
</pre>

Only change the "'''Older posts'''" and "'''Newer posts'''" text in the above to say anything else you wish.

*Related forum thread
**http://ithemes.com/forum/index.php?/topic/19863-pagination-text/

==Video Tutorials and Tips==
These different video tutorials and tips can help you figure out more things about LoopBuddy. Remember, these videos show LoopBuddy and related things that were the most recent/updated as of the date of that video. Things may have changed in actual LoopBuddy since then.
# [http://ithemes.com/forum/index.php?/topic/18160-loop-buddy-placement/#p85184 Show custom static homepage content and 3 latest blog excerpts under it]

==Additional Resources==
# [http://pluginbuddy.com/purchase/backupbuddy/ Purchase BackupBuddy]
# [http://pluginbuddy.com/tutorials/ PluginBuddy Tutorials]
# [http://pluginbuddy.com/ PluginBuddy.com]
# [http://pluginbuddy.com/support/ Support Forums]

[[Category:PluginBuddy]]

LoopBuddy

2011-11-04T21:58:41Z

Bes: Added /* Change OLDER POSTS and NEWER POSTS pagination text */ sub-section

'''Release date:''' July 19, 2011

==LoopBuddy Overview==

LoopBuddy is a tool that overwrites a WordPress Loop using a combination of a custom query and a custom Loop layout. You can also create your own Loops using the LoopBuddy shortcode and LoopBuddy widget.

===Query Editor===

If LoopBuddy was a body, the Query Editor would be the brain, with the Layout Editor being the outside bodily appearance.

[[File:Query_editor.png|400px|border|LoopBuddy Query Editor]]

With the Query Editor, you can create Query Groups. Each Query Group defines what data a WordPress Loop is supposed to pull in.

With the Query Editor, you can define:

* Which posts to gather
* Whether pagination or comments are enabled
* Whether to use the default post ID (if on a single post or page)
* and much, much more...

[[File:Query_editor_options.png|400px|border|Query Editor Options]]

===Layout Editor===

The Layout Editor controls how a particular WordPress Loop is supposed to be structured. At the heart of the Layout Editor is Layout Tags. There are several Layout Tags built-in, but you can use the LoopBuddy Hooks to create your own custom Layout Tag and Layout Tag Items.

[[File:Layout_editor.png|400px|border|LoopBuddy Layout Editor]]

With the Layout Editor, simply drag Layout Tags into the appropriate area. If you create a new Layout, there are several default tags that are added automatically.

[[File:Layout_editor_options.png|500px|border|Layout Editor Options]]

===Global Settings===

The Global LoopBuddy Settings allow you to globally override a default WordPress Loop. If your theme doesn't support the Loop Standard, you'll see an error message at the top.

If your theme does support the Loop Standard, you can use the options to override the default WordPress Loops in various areas of the site.

Although LoopBuddy attempts to work without a custom Query, it is highly advisable to use a custom Query and Layout.

[[File:Loopbuddy_settings.png|500px|border|General Settings]]

===Import/Export===

Within the Query and Layout editors, you can export/import the items so you can use the same Queries/Layouts on a different site.

===LoopBuddy Widget===

You can use the LoopBuddy Widget to display a LoopBuddy Query/Layout in any widgetized area of a site. Please note that you must have a Query AND a Layout for the widget to work.

===LoopBuddy Shortcode===

The LoopBuddy shortcode takes two attributes: a Query ID and a Layout ID. Please note that you must have a Query AND a Layout for the widget to work.

Simply insert the shortcode into a post or page:

<pre class='brush:php'>
[loopbuddy query_id='0' layout_id='0']
</pre>

===LoopBuddy Full 1 Hour Webinar===

Learn the ins and outs of LoopBuddy with the following 1 hour Webinar, made by our very own [http://www.webdesign.com Webdesign.com]
{{#ev:vimeo|26482158|580|363}}

==The Loop Standard==
The Loop Standard divides a loop into two main concepts: a loop and one or more entries.

Both a loop and an entry have three sections: a header, a content section, and a footer. The header contains title information, any meta information, and any necessary navigation links. The content section contains the content relevant to that loop or entry. The footer section is a place to hold additional or duplicate meta information and navigation links.

===The Loop Explained===

The content of a loop is a bit more complex than the content of an entry as a loop's content contains the entries. To better visualize this, here is the basic structure described so far:

* Loop
** Header
*** title
*** navigation
*** meta
** Content
*** Entry
**** Header
***** title
***** navigation
***** meta
**** Content
**** Footer
***** navigation
***** meta
*** Additional entries...
*** Footer
**** navigation
**** meta

The idea is that each section is broken out in a repeatable pattern. This makes styling easier as any content that follows this form can be styled without having to first read through the code in order to understand the structure.

You may notice that there are titles, navigation, and meta for both the entries and the loop. This is because some titles, navigation, and meta are relevant to the loop (the title archive, navigating between pages of posts, or information about an author in an author archive) while other titles, navigation, and meta are relevant to the entry (the blog post's title, navigating through a page split into multiple pages, or a blog post's category information). The rule of thumb is that if the information is specific to an individual post's, page's, etc content, it is an entry-level structure; otherwise, it is a loop-level structure.

Each of these sections have a specific class in the Loop Standard. Here is the structure again with the classes replacing the names:

* loop
** loop-header
*** loop-title
*** loop-utility
*** loop-meta
** loop-content
*** hentry
**** entry-header
***** entry-title
***** entry-utility
***** entry-meta
**** entry-content
**** entry-footer
***** entry-utility
***** entry-meta
*** hentry...
** loop-footer
*** loop-utility
*** loop-meta

Notice the "hentry" class. This looks odd but is actually generated by WordPress internally. It is produced by the <code>post_class()</code> function that is in 2010 and 2011 theme template files. So when you see "hentry", know that this is simply the div that looks like :

<pre class='brush:php'>
<div <?php post_class(); ?>></div>
</pre>

Here is the standard loop in practice:
* loop
** loop-header
*** loop-title (page-title)
** loop-content
*** hentry
**** entry-header (title)
***** entry-title (post-title)
***** entry-meta (post-meta)
***** entry-meta date (date)
**** entry-content (post-content)
**** entry-footer (meta-bottom)
***** entry-meta alignright (alignright)
***** entry-meta alignleft (meta-bottom-left)
*** hentry...
** loop-footer
*** loop-utility (paging)

Not all the elements from above structure examples were used since not all were needed. In the end, only three elements had to be added. The rest of the changes were simply modifying or adding classes to conform to the Loop Standard structure. For some elements, such as "date", the "date" class remained while also getting the "entry-meta" class. This makes it clear what type of structure it is while still giving the additional meaning of it being a container for the date.

===Modifying a Theme to Use LoopBuddy===

Here's an example of TwentyTen's index.php file before it begins loading the various templates:

<pre class='brush:php'>
<?php if ( ! dynamic_loop() ) : ?>
<div class="loop">
<?php
/* Run the loop to output the posts.
* If you want to overload this in a child theme then include a file
* called loop-index.php and that will be used instead.
*/
get_template_part( 'loop', 'index' );
?>
</div>
<?php endif; ?>
</pre>

When <code>dynamic_loop()</code> is executed, LoopBuddy searches to see if this particular loop should be overridden. If not, the normal loop executes. If so, then LoopBuddy overwrites the content of the loop with LoopBuddy content.

===Example of TwentyTen Using the Loop Standard===
Here's an example TwentyTen Loop converted to using the Loop Standard

<pre class='brush:php'>
<?php if ( have_posts() ) while ( have_posts() ) : the_post(); ?>

<div class="loop-content">
<div id="nav-above" class="navigation loop-utility loop-utility-above">
<div class="nav-previous"><?php previous_post_link( '%link', '<span class="meta-nav">' . _x( '←', 'Previous post link', 'twentyten' ) . '</span> %title' ); ?></div>
<div class="nav-next"><?php next_post_link( '%link', '%title <span class="meta-nav">' . _x( '→', 'Next post link', 'twentyten' ) . '</span>' ); ?></div>
</div>

<div id="post-<?php the_ID(); ?>" <?php post_class(); ?>>
<div class="entry-header">
<h1 class="entry-title"><?php the_title(); ?></h1>

<div class="entry-meta">
<?php twentyten_posted_on(); ?>
</div>
</div>
<div class="entry-content">
<?php the_content(); ?>
<?php wp_link_pages( array( 'before' => '<div class="page-link">' . __( 'Pages:', 'twentyten' ), 'after' => '</div>' ) ); ?>
</div>
<div class="entry-footer">
<?php if ( get_the_author_meta( 'description' ) ) : // If a user has filled out their description, show a bio on their entries ?>
<div id="entry-author-info" class="entry-meta entry-meta-below">
<div id="author-avatar">
<?php echo get_avatar( get_the_author_meta( 'user_email' ), apply_filters( 'twentyten_author_bio_avatar_size', 60 ) ); ?>
</div>
<div id="author-description">
<h2><?php printf( esc_attr__( 'About %s', 'twentyten' ), get_the_author() ); ?></h2>
<?php the_author_meta( 'description' ); ?>
<div id="author-link">
<a href="<?php echo get_author_posts_url( get_the_author_meta( 'ID' ) ); ?>">
<?php printf( __( 'View all posts by %s <span class="meta-nav">→</span>', 'twentyten' ), get_the_author() ); ?>
</a>
</div>
</div>
</div>
<?php endif; ?>

<div class="entry-utility">
<?php twentyten_posted_in(); ?>
<?php edit_post_link( __( 'Edit', 'twentyten' ), '<span class="edit-link">', '</span>' ); ?>
</div>
</div>
</div>
<div class="loop-footer">
<div id="nav-below" class="navigation loop-utility loop-utility-below">
<div class="nav-previous"><?php previous_post_link( '%link', '<span class="meta-nav">' . _x( '←', 'Previous post link', 'twentyten' ) . '</span> %title' ); ?></div>
<div class="nav-next"><?php next_post_link( '%link', '%title <span class="meta-nav">' . _x( '→', 'Next post link', 'twentyten' ) . '</span>' ); ?></div>
</div>
</div>

<?php comments_template( '', true ); ?>
</div>

<?php endwhile; // end of the loop. ?>

</pre>

After updating the template files, go through the theme's style.css file in order to update class references to match the new ones. Here are some basic replacements to make:

* .page-title → .loop-title
* .title → .entry-header
* .post-title [h1, h2, h3, etc] (any instance of .post-title followed by a header tag) → .entry-title
* .post-title → .entry-title
* .post-meta → .entry-meta
* .post-content → .entry-content
* .meta-top → .entry-header
* .meta-bottom → .entry-footer
* .post → .hentry
* .paging → .loop-utility

===Showing LoopBuddy Theme Support===

After you've modified your theme's loops, show LoopBuddy that your theme supports it by adding in the following line to your theme's functions.php file:

<pre class='brush:php'>
// Add support for the Loop Standard
add_theme_support( 'loop-standard' );
</pre>

===Adding the Dynamic Loop Function to Your Theme===
The Dynamic Loop function must be added to your theme's functions.php file. This is achieved by adding the following code to the end of the function.php file:

<pre class='brush:php'>
// Add dynamic_loop function for LoopBuddy

/*
Copyright 2011 iThemes (email: support@ithemes.com)

Written by Chris Jean
Version 0.0.1

Version History
0.0.1 - 2011-02-28 - Chris Jean
Initial version
*/

if ( ! function_exists( 'dynamic_loop' ) ) {
function dynamic_loop() {
global $dynamic_loop_handlers;

if ( empty( $dynamic_loop_handlers ) || ! is_array( $dynamic_loop_handlers ) )
return false;

ksort( $dynamic_loop_handlers );

foreach ( (array) $dynamic_loop_handlers as $handlers ) {
foreach ( (array) $handlers as $function ) {
if ( is_callable( $function ) && ( false != call_user_func( $function ) ) ) {
return true;
}
}
}

return false;
}
}

if ( ! function_exists( 'register_dynamic_loop_handler' ) ) {
function register_dynamic_loop_handler( $function, $priority = 10 ) {
global $dynamic_loop_handlers;

if ( ! is_numeric( $priority ) )
$priority = 10;

if ( ! isset( $dynamic_loop_handlers ) || ! is_array( $dynamic_loop_handlers ) )
$dynamic_loop_handlers = array();

if ( ! isset( $dynamic_loop_handlers[$priority] ) || ! is_array( $dynamic_loop_handlers[$priority] ) )
$dynamic_loop_handlers[$priority] = array();

$dynamic_loop_handlers[$priority][] = $function;
}
}

</pre>

==LoopBuddy Downloads==

===Example TwentyEleven Theme===

Here's an example TwentyEleven theme that has been modified to be compatible with LoopBuddy.

[[Media:twentyeleven-loopstandard.zip|TwentyEleven Loop Standard]]

===Example Layout Tag===

Check out the LoopBuddy Marquee Plugin: [[Media:Loopbuddy_marquee.zip|LoopBuddy Marquee]] as an example of creating custom tags.

===Example Queries/Layouts===

Please see below for a ZIP file of some sample layouts and queries that can be imported.

[[Media:Loopbuddy_export.zip|LoopBuddy Export File]]

==LoopBuddy Query==
The LoopBuddy Query is where you create Queries, which in turn create and produce the Loops you want in WordPress. From showing certain posts to the number of posts, categories, posts with specific meta values and more, the '''LoopBuddy Query''' area is where you specify exactly what should be shown, and exactly what should not be shown, in a LoopBuddy output.

===Advanced Meta Queries===

With LoopBuddy 1.2, LoopBuddy Queries now allow you to perform some very powerful advanced Meta queries. Here is a video explaining and giving some examples of the advanced meta queries:

{{#ev:youtube|4snQn7PDylE|580|363}}
*[http://pluginbuddy.com/loopbuddy-1-2-released/ Blog Post announcing Advanced Meta Queries in LoopBuddy 1.2]

===Advanced Taxonomy Queries===

With LoopBuddy 1.2, LoopBuddy Queries now allow you to perform some very powerful advanced Taxonomy queries. Here is a video explaining and giving some examples of the advanced Taxonomy queries:

{{#ev:youtube|ta0GZA5jz9g|580|363}}
*[http://pluginbuddy.com/loopbuddy-1-2-released/ Blog Post announcing Advanced Taxonomy Queries in LoopBuddy 1.2]

==Hooks==

LoopBuddy allows you to create custom tags for the Layout editor. This is advanced functionality, so please don't attempt these steps if you are not intimately familiar with PHP and how LoopBuddy operates.

To create the custom tag, you must use the following hooks.

===Creating a new Custom Tag===

<pre class="brush:php">
<?php
add_filter( 'pb_loopbuddy_custom_tags', 'my_custom_tag_add' );
function my_custom_tag_add( $custom_tags ) {
//Always return $custom_tags
$custom_tags[ 'start_wrap' ] = array(
'My Tag Label',
array(
'wrap' => 'div',
'custom_class' => 'default class'
)
);
return $custom_tags;
} //end my_custom_tag_add

//Start off with the tag name, give the tag a label, and pass it which items it supports (all should ideally contain the 'wrap' and 'custom_class' items
?>
</pre>

Here are some built in tag items that you can choose from:

* link_text
* custom_url
* custom_class
* link_title
* before_text
* after_text
* meta_key
* max_width
* max_height
* shortcode
* author_link_destination
* user_profile
* permalink
* attachment_link_display
* separator
* text
* date_format
* comment_number_zero
* comment_number_one
* comment_number_more
* post_date
* bloginfo
* content_more
* url_display
* image_size

===Creating a new custom tag item===

<pre class='brush:php'>
<?php
add_filter( 'pb_loopbuddy_tag_items', 'my_custom_item_add' );
function my_custom_item_add( $loopbuddy_items ) {
//Always return $loopbuddy_items

$loopbuddy_items[ 'my_custom_item' ] = array(
'function' => 'callback_function',
'args' => array(
'label' => __( 'Link Text', 'LION' ),
'tip' => __( 'Optional text for link. Leave blank to use link as the text.', 'LION' ),
'options' => array( 'option1', 'option2' )
)
);
return $loopbuddy_items;
} //end my_custom_item_add

/* $settings are the arguments passed for the tag item and looks like this
[label] => HTML Wrapper
[tip] => Choose which HTML element to wrap around the item
[options] => Array
(
[0] => none
[1] => span
[2] => div
[3] => p
[4] => h1
[5] => h2
[6] => h3
[7] => h4
[8] => h5
[9] => h6
)

[key] => wrap
[settings] => Array
(
[image_size] => thumbnail
[max_width] =>
[max_height] =>
[wrap] => p
[before_text] =>
[after_text] =>
[custom_url] =>
[custom_class] => attachment
[tag] => wp_get_attachment_image
)

)
*/
function callback_function( $settings ) {
$defaults = array(
'key' => '',
'label' => '',
'tip' => false,
'settings' => array(),
'options' => array()
);
extract( wp_parse_args( $settings, $defaults ) );
//Output HTML for the item
} //end callback_function

?>
</pre>

===Callback function for displaying the tag - pb_loopbuddy_tag_callback-{tag_name}===
<pre class='brush:php'>
<?php
/*$settings contains the tag items and the tag item's value
Example
Array
(
[image_size] => thumbnail
[max_width] =>
[max_height] =>
[wrap] => p
[before_text] =>
[after_text] =>
[custom_url] =>
[custom_class] => attachment
[tag] => wp_get_attachment_image
)
*/

//Add header code
add_action( 'pb_loopbuddy_tag_header-mytagname', 'my_custom_tag_header' );
function my_custom_tag_header( $settings ) {
echo "my header, notes, or other code";
//Render your tag based on its settings
} //end my_custom_tag_header

//Add footer code
add_action( 'pb_loopbuddy_tag_footer-mytagname', 'my_custom_tag_footer' );
function my_custom_tag_footer( $settings ) {
echo "my footer, notes, or other code";
//Render your tag based on its settings
} //end my_custom_tag_header

add_filter( 'pb_loopbuddy_tag_supports-mytagname', 'my_custom_tag_supports' );
//Return an array of what tag items the tag supports
function my_custom_tag_supports( $support_tag_items ) {
return array( 'wrap', 'link_text', 'before_text', 'after_text', 'custom_class' );
//Render your tag based on its settings
} //end my_custom_tag_supports
?>
</pre>

===Rendering the Tag on the Front-end - pb_loopbuddy_render-{tag_name}===

<pre class="brush:php">
<?php
add_filter( 'pb_loopbuddy_render-mytagname', 'mytagname_frontend', 10, 2 );
function mytagname_frontend( $post_object, $tag_items ) {
/* $tag_items look like this
(
[wrap] => none
[link_text] => Edit Post
[before_text] =>
[after_text] =>
[custom_url] =>
[custom_class] =>
[tag] => edit_post_link
)
*/
$return = false; //Populate the $return variable
$return = pluginbuddy_loopbuddy_render_slotitems::get_output( $return, $post_object, $tag_items, true ); //The last argument is skip_before text
return $return;
} //end mytagname_frontend
?>
</pre>

===Ignoring Post Types in the Layout Editor===

There will be certain post types that are public and have a public user interface, but the user would still not like to be able to configure override settings in the LoopBuddy Settings page.

A plugin author can use the following hook to remove these post types:

<pre class="brush:php">
<?php
add_filter( 'pb_loopbuddy_exclude_post_types', 'myplugin_exclude_post_types' );
function myplugin_exclude_post_types( $post_types_to_exclude ) {
$post_types_to_exclude[] = 'my_custom_post_type';
return $post_types_to_exclude;
}
?>
</pre>

==Shortcodes==

Shortcodes basically allow almost any plugin or custom code to be plugged in anywhere in WordPress.

LoopBuddy supports shortcodes fully, allowing you to put any shortcode, whether from a plugin or your own, into any place in LoopBuddy Layout, including the '''Pre-Loop Text / HTML''', '''Post-Loop Text / HTML''' and '''No Results Text / HTML''' sections. This probably makes the already powerful LoopBuddy the only most powerful way to control all your content, loops and display on your site.

[http://ithemes.com/codex/page/General_WordPress_Related#Editing_or_Adding_Stuff_to_Functions.php Info on editing or adding stuff to Functions.php]

===Show Category/Taxonomy Description on NON-Archive pages via Shortcode===

Category Descriptions are a little more sophisticated than other post related variables because if there is more than one category being used, then it will be hard for WordPress to display ALL descriptions nicely OR one category (which one?).

*Outside of archive pages, to display Category Descriptions (or any taxonomy description) you have to do the following:
**1 : Put the following anywhere (usually near the end of the file) in your theme's custom functions.php file (it creates a shortcode you'll use to display the description of a Category or any Taxonomy):
<pre class="brush:php">add_action( 'init', 'lb_cat_init' );
function lb_cat_init() {
add_shortcode('taxdescription', 'lb_the_description');
} //end lb_cat_init
function lb_the_description() {
global $post;
if ( !is_object( $post ) ) return;
$terms = get_post_meta( $post->ID, 'description_terms', true );
$taxonomy = get_post_meta( $post->ID, 'description_taxonomy', true );
$return = '';
if ( $terms && $taxonomy ) {
if ( !is_array( $terms ) ) {
$terms = explode( ',', $terms );
}
foreach ( $terms as $term_name ) {
$term = get_term_by( 'slug', $term_name, $taxonomy );
if ( !$term ) continue;
$description = get_term_field( 'description', $term->term_id, $term->taxonomy );
if ( empty( $description ) || !$description ) continue;
$return .= apply_filters( 'pb_the_content', $description );
}
}
return $return;
} //end lb_the_description</pre>
**2 : In the posts you want to show the category description, add the following 2 custom field names and values:
'''Custom Field Name''' ----- '''Custom Field Value'''

description_taxonomy ----- category

description_terms ----- books '''''(OR any category name you have)'''''

**3 : Add a Shortcode Tag to your LoopBuddy layout which has the following shortcode in it:

<code><strong>[taxdescription]</strong></code>

That will show the category description anywhere you put the shortcode.

*Links with related info:
**[http://ithemes.com/forum/index.php?/topic/18153-use-of-category-description/ Use of Category Description - LoopBuddy Forums]
**[http://codex.wordpress.org/Function_Reference/category_description category_description on WordPress Codex]
**[http://codex.wordpress.org/Function_Reference/term_description term_description on WordPress Codex]

===Show Custom Page Title for Same LoopBuddy Layout on Different Pages via Shortcode===

*One awesome example of using Shortcodes with LoopBuddy is to show a custom page title, along with any LoopBuddy Layout content, where different pages use the same LoopBuddy Layout. Our awesome LoopBuddy customer Bruce provided the following info to help you all with that:
**1 : Put the following anywhere (usually near the end of the file) in your theme's custom functions.php file:
<pre class="brush:php">
function return_title() {
return '<h1>'.get_the_title().'</h1>';
}
add_shortcode('pg_title', 'return_title');</pre>
**2 : Add
<code><strong>[pg_title]</strong></code>

anywhere in the LoopBuddy Layout where you want to show the custom page title.

That will show the custom page title just for that specific post/page where the Layout is being shown.
*Related links:
**[http://ithemes.com/forum/index.php?/topic/18046-displaying-the-page-title-on-which-i-am-using-loop-buddy/ LoopBuddy user Bruce asking about and then sharing the code to show custom Page Titles on each Page where the same LoopBuddy Layout is used]

==External Plugins Compatibility==

LoopBuddy is one of those rare plugins which can play well with many external plugins. However, any external plugin compatibility is NOT guaranteed in any manner, since external plugins are not covered nor supported by PluginBuddy in any manner or fashion.

If there is a problem when any other plugin is used with LoopBuddy, it does not mean there is a bug in LoopBuddy. First you should check if there is a problem in the other plugin (since LoopBuddy already currently works without any issues in each and every aspect of its publicized features). Then you have to see if the problem exists when the other plugin is de-activated and LoopBuddy is kept activated. Only after such steps and more analysis can we at PluginBuddy devote any time or resources to see whether or not there is something in LoopBuddy that can be fixed, enhanced or improved to make it work better with the external plugin in question, if that external plugin is not the source of the problem.

===Custom Post Types===
At this time, Custom Post Types UI is the only supported plugin in LoopBuddy for creating custom post types. We recommend you try and use that to create post types.

Otherwise, you should add custom post types directly to your functions.php file in your current theme.

*Related links
**[http://wordpress.org/extend/plugins/custom-post-type-ui/ Custom Post Types UI plugin]
**[http://codex.wordpress.org/Post_Types Creating Post Types in WordPress]

===Page Navigation===

At this time, WP-PageNavi is the only supported plugin in LoopBuddy for having custom page navigation. We strongly recommend you try it for any of your custom page navigation needs.

*Related link
**[http://wordpress.org/extend/plugins/wp-pagenavi/ WP PageNavi WordPress Plugin]

===Customize Excerpts===

At this time, Advanced Excerpt is the only supported plugin in LoopBuddy for allowing custom lengths and formatting for excerpts in WordPress.

*Related link
**[http://wordpress.org/extend/plugins/advanced-excerpt/ Advanced Excerpt WordPress Plugin]

==LoopBuddy FAQ==

Here are some frequently asked or encountered LoopBuddy questions and setups, and their answers.

===Sort Custom Field Values by Meta Value (Character or Numeric)===

*Custom Field values can be sorted by meta value (character or numeric).
*Only ONE meta item can be used to sort at one time.
**Using multiple meta items will assume you would like an advanced meta query, and sorting will be ignored in such a case. '''This is a WordPress limitation.'''
*Sort Custom Field Values via the following steps (assuming you already have several posts with the same custom field):
**1 : Change the Order By parameter to either "'''Meta Value'''" or "'''Numeric Meta Value'''".
**2 : Go to Post Meta Parameters and click "'''Add Meta'''".
**3 : Set the '''Meta Key''' and '''Meta Values''' you would like to search for and sort by.
**4 : Save the query.
**5 : Assign the query to a post or section and observe the results.

===LoopBuddy does not work on static Posts page===

*LoopBuddy will NOT work on pages set as Static Posts Page in '''WordPress --> Settings --> Reading --> Front Page Displays --> Posts Page''' section. There is a good reason for it and a great workaround.
** Reason
***The Reading Screen in the WordPress Settings [http://codex.wordpress.org/Settings_Reading_Screen Settings --> Reading Screen Settings] is necessary when you want to tell WordPress that your blog content doesn't reside on the home page.
***For example, you have selected a Front Page, which will tell WordPress, "Use this page instead of showing a default blog layout."
***Since there is technically no longer a blog layout, WordPress wants to know, "Where can I find your blog content?"
***This is how WordPress works, and not a LoopBuddy bug. There is a great flawless way to get exactly what you want with the below workarounds, though.
**Workaround (any one of this will work - we recommend the PREFERRED LoopBuddy way to do it!)
*** Not have a section on your site with your blog content (readers will only be able to access your posts via category and date archives).
*** Create a page to point WordPress to, and WordPress will take care of the rest and display the appropriate blog content.
*** '''PREFERRED:''' With LoopBuddy, however, you don't have to specify a "Blog" section in WordPress.
**** You can create a regular page.
**** Allow LoopBuddy to create a blog section for you either via '''LoopBuddy --> Settings''' option OR by choosing the '''LoopBuddy options in the Post/Page Editor page''' for the page you just created.
**** WordPress doesn't need to know about it in this particular case, and it won't hurt your site in the least. You do NOT have to change the '''WordPress --> Settings --> Reading --> Front Page Displays --> Posts Page''' settings for this option to work perfectly.
*Threads and pages with more detailed info of the setup and info related to the above exact solutions
**http://ithemes.com/forum/index.php?/topic/17845-unable-to-get-loopbuddy-working/
**http://codex.wordpress.org/Settings_Reading_Screen

===Make a Custom Field (or almost anything) Clickable===
With the power of different tags in LoopBuddy Layout, you can make almost anything clickable without editing a single file. This is extremely useful when you want to make something like a Custom Field, which is text by default, clickable automatically in any or every loop.
*Steps to perform in your LoopBuddy Layout:
**1 : Start with a Text tag (first Text tag) which has the content: <code><a href="</code>
**2 : Next comes anything, including a Custom Field tag. This is the link.
**3 : Now comes another Text tag (second Text tag) which has the content: <code>"></code>
**4 : Now comes anything to show the link. It can be the same Custom Field tag again as #2 above, another custom field, or any text or image you wish.
**5 : Another Text tag (3rd Text tag) with the following content: <code></a></code>
That's it!
*Related thread
**http://ithemes.com/forum/index.php?/topic/16971-text-before-single-custom-field-and-url/

===Search within a LoopBuddy Query===

You can have search widgets which actually search specific LoopBuddy queries for the parameters you specify. There are many different ways of achieving this with LoopBuddy.

Check out the forum thread [http://ithemes.com/forum/index.php?/topic/16606-searching-within-a-loopbuddy-query/ Searching Within a LoopBuddy Query] for more details.

===Change OLDER POSTS and NEWER POSTS pagination text===

You can change the "'''Older posts'''" and "'''Newer posts'''" text to say anything by editing those words in your '''''loopbuddy/loopbuddy.php''''' file on lines 1336 and 1337. They will look like the following:

<pre brush="php">
div class="nav-previous"><?php next_posts_link( __( '<span class="meta-nav">←</span> Older posts', 'it-l10n-loopbuddy' ) ); ?></div>
<div class="nav-next"><?php previous_posts_link( __( 'Newer posts <span class="meta-nav">→</span>', 'it-l10n-loopbuddy' ) ); ?></div>
</pre>

Only change the "'''Older posts'''" and "'''Newer posts'''" text in the above to say anything else you wish.

*Related forum thread
**http://ithemes.com/forum/index.php?/topic/19863-pagination-text/

==Video Tutorials and Tips==
These different video tutorials and tips can help you figure out more things about LoopBuddy. Remember, these videos show LoopBuddy and related things that were the most recent/updated as of the date of that video. Things may have changed in actual LoopBuddy since then.
# [http://ithemes.com/forum/index.php?/topic/18160-loop-buddy-placement/#p85184 Show custom static homepage content and 3 latest blog excerpts under it]

==Additional Resources==
# [http://pluginbuddy.com/purchase/backupbuddy/ Purchase BackupBuddy]
# [http://pluginbuddy.com/tutorials/ PluginBuddy Tutorials]
# [http://pluginbuddy.com/ PluginBuddy.com]
# [http://pluginbuddy.com/support/ Support Forums]

[[Category:PluginBuddy]]

PluginBuddy

2011-11-04T19:57:52Z

Bes: Added WP Super Cache info and fixed a missing period (.). /* Plugin Conflicts */

Welcome to the PluginBuddy Knowledge Base - Tutorials, Technical Information, Debugging Information, and more.

=Premium Plugins=
* [[Ajax-Edit-Comments]]
* [[BackupBuddy]]
* DisplayBuddy
** [[Accordion]]
** [[Billboard]]
** [[Carousel]]
** [[CopiousComments]]
** [[FeaturedPosts]]
** [[Rotating Images]]
** [[RotatingText]]
** [[Slideshow]]
** [[Tipsy]]
** [[VideoShowcase]]
* [[EmailBuddy]]
* [[LoopBuddy]]
* [[Mobile]]
* [[TailoredLogin]]
* [[ThumbsUp]]
* [[VidEmbed]]

=Free Plugins (active)=
* [[Featured Text]]
* [[PB-Tweet]]
* [[ServerBuddy]]
* [[Tabber Widget]]
* [[ThemeMan]]
* [[S3 URLS]]
* [[YOURLS]]
* [[ContactBuddy]]

=Free Plugins (inactive)=
* [[WP Easy Uploader]]
* [[WP Developer Assistant]]
* [[Easy Theme and Plugin Updater]]
* [[Current Date & Time Widget]]

''[[:Category:PluginBuddy|View all PluginBuddy Wiki Pages]]''

=Misc. Documentation=
==Frequently Asked (Plugin) Questions==
*[[General Plugins FAQ]]

==License Manager Tutorial and Information==
*[[License Manager]]
==PHP Development & Advanced==
*[[.htaccess]]
*[[PHP]]
*[[Arrays]]

[[Category:PluginBuddy]]

=Translations (localization / internationalization)=

Many PluginBuddy plugins come with translation capability. That means such PluginBuddy plugins can be translated (aka localized) to other languages.

===How Translations Work===

PluginBuddy provides the capability to have a translation in such plugins. Anyone wanting to enhance PluginBuddy with specific language translations can do so voluntarily via Translation Files. Translation Files are simply language files created fully and solely by the volunteer community which use the already built in translation-capable features in many of the PluginBuddy plugins to allow such plugins to show text or outputs in different languages. Making PluginBuddy translation-capable is done by PluginBuddy. Creating, updating and sending in any language specific translation files to PluginBuddy is done by the volunteer community.

Anyone can create translation files, package them into the proper format and give PluginBuddy the final translated files that we will try to include in the next update for the plugin in question. We call such awesome people, who create or update the translation files and send us the full translation package files, '''Awesome Translator Volunteers''', and we are really thankful that they take the time to do such an awesome thing.

If you want to help us, you can translate any existing PluginBuddy plugin which supports internationalization (another way of saying localization or translation-capable) and then, once you're fully done, simply let us know in the forums the link to the final language files that we can directly save and simply try to include in any future updates for the plugin(s) in question.

===Tips on how to localize any PluginBuddy Plugin to any non-English language===

The following 9 tips can help you figure out how to approach translations, how to create translations, and how to send us the final translated file for any translation-capable PluginBuddy plugin:

*1 : Many of the PluginBuddy plugins are internationalized, meaning they have the capability to be translated, via actual external translation files, by any non-iThemes-staff Awesome Translator Volunteer who wishes such plugins to be translated to their language.
*2 : If a PluginBuddy plugin is currently not internationalized or you're not sure if it is, you can ask us in the [http://ithemes.com/forum Support Forums] and we'll let you know, or we'll have it included as a future translation feature request. After the translation capability is added to such a plugin, you can submit the actual translation file. Please remember though: we cannot help with creating, understanding or making any language translation files. Our Awesome Translator Volunteers do that voluntarily (you can too! keep on reading) and fully on their own.
*3 : There are MANY resources which teach you how to create and work with WordPress language files. Following are the official 3 directly by the WordPress community:
**1 : [http://codex.wordpress.org/WordPress_in_Your_Language WordPress in Your Language]
**2 : [http://codex.wordpress.org/Translating_WordPress Translating WordPress]
**3 : [http://codex.wordpress.org/I18n_for_WordPress_Developers What WordPress Localization in Plugins is mainly about]
*4 : Translations are sent in from volunteers from all over the world. As a courtesy, we sometimes package the actual language translation files (provided directly by the Awesome Translator Volunteers) in with the final product. If some translation is not included in the actual plugin even when the plugin has the capability to be translated, you can submit the final translation to us for consideration in the next update by posting on our forums OR you can include the translation in your own live or local WordPress install directly for your own use. More info on how to include your own language specific file for your own WordPress sites is in the resources listed in #3 above.
*5 : A translation included in with the final product does not guarantee the accuracy or quality of the translation. These files are from the Awesome Translator Volunteers, and correction of these files is also done by those Awesome Translator Volunteers.
*6 : If a translation is very inaccurate or incomplete, we can put out a request for a new translation from the volunteer community, or remove the translation from the packaged and final product. You can also let us know of any inaccuracies in any existing translation files by the Awesome Volunteers by providing us with the corrected final files. Please remember: we only accept final and full translation files that you yourself have already created or packaged properly. If you let us know only of the actual inaccuracies without providing the final correct files, we cannot make such changes ourselves to the translation files.
*7 : Unfortunately, PluginBuddy cannot work on, help with, create, nor make any updates to any specific translation files you may have, or may be working on, or want to work on. Our Awesome Volunteers do that and simply give us the final files for inclusion or consideration.
*8 : If you have corrections for any existing translation in form of final proper format translation files for an existing language, OR want to provide the final and proper translation files for a new language, please post a new thread in the appropriate product category in the [http://ithemes.com/forum/ PluginBuddy Support Forums] with the final translations files. If you have any support questions on how to create or make language specific translation files, or how translation files work, you can do so on the [http://wordpress.org/support/ WordPress forums], as such support questions are outside the scope of what PluginBuddy support guarantees with your iThemes membership.
*9 : Any final translation file provided by you (or any other Awesome Volunteer) on the support forums will then be saved and filed as a future enhancement request for the future updates of the plugin(s) in question. In your support forum thread, where you share the final complete translation files you inclusion, you can upload your files directly to the forums OR upload them somewhere and link to them in your support forum thread. We will then download and save such files. Remember please: we cannot guarantee looking inside such files or verifying that they are correct in any manner (because of so many languages in the world and so many possible language files everywhere).

Thank you SO MUCH for being interested in providing translation files for our PluginBuddy plugins. We hope you will become one of our Awesome Translator Volunteers, in addition to being our AWESOME CUSTOMER, and create/update any language-specific translation file package and provide it to us so that we can consider including it in future updates.

===Resources for understanding, creating, updating and submitting final translation files===
*Here are the 3 official resources again which you can use to create, update, start work on and finish translation on any of the translation-capable PluginBuddy plugins:
**1 : [http://codex.wordpress.org/WordPress_in_Your_Language WordPress in Your Language]
**2 : [http://codex.wordpress.org/Translating_WordPress Translating WordPress]
**3 : [http://codex.wordpress.org/I18n_for_WordPress_Developers What WordPress Localization in Plugins is mainly about]

=Extra Customizations=
While any extra customization of any PluginBuddy Plugin is beyond the scope of the official support, we do from time to time offer different tips and tutorials on editing the awesome PluginBuddy plugins to better fit your individual needs. All such edits are, however, beyond what is officially supported and provided in the actual plugin admin panel and officially stated features on the individual plugin pages. No official support is provided nor guaranteed in, before, during, after or related to anything resulting from any such edits/customizations.

No support is provided on any of these extra customizations. Any of the steps mentioned in any of these extra custom edits may change at any time depending on newer versions of the plugins being released. Any use or customization of anything, beyond what is provided by default inside the plugin admin menu, means you are proceeding at your own risk and that you accept 100% responsibility and liability for everything you change or modify in any manner in the plugin. Your purchase and use of any PluginBuddy plugin implies and shows that you are buying and using PluginBuddy plugin(s) the way it(they) came in their original unmodified form, with no exceptions.

*Remember:
**[http://pluginbuddy.com/purchase/backupbuddy/ Make a backup of your entire site with BackupBuddy] before making any edits!
** PluginBuddy only supports the official unedited, unmodified versions of all PluginBuddy plugins.
** Use a good text editor to make any file changes. Again, maintain backups!
** Any changes you make to files WILL MOST PROBABLY be lost when the plugin is upgraded to any newer version.
** You are 100% responsible and liable for anything resulting from any of these changes.
** No support is provided nor guaranteed on any of these extra changes in any form or shape, whatsoever, regardless of who suggested these custom edits or suggestions.
** Any extra customization info or suggestion is added voluntarily by PluginBuddy staff to help users as much as possible, even if such customization is outside the scope of any membership support.
** Whether a PluginBuddy staff or representative offered or suggested the edit/customization, another customer or anyone else, PluginBuddy does not officially support nor provide any official support on any such edits.
** We cannot guarantee providing any support on any edits or customization tips we provide.
** Absolutely no support is guaranteed in any manner on any of our free plugins, whether or not there is any customization/edit involved.

=External Plugins Compatibility=

PluginBuddy does not promise, guarantee or provide support for any compatibility with any external plugin. If any PluginBuddy Plugin works without any problems when used with any external plugin in question, that means the PluginBuddy Plugin is most probably working without any issues overall. PluginBuddy is not responsible for making PluginBuddy plugins work in any manner, whether custom, fully, fixed or other, with any external non-PluginBuddy plugins. PluginBuddy is also not responsible for providing any support whatsoever for any external plugin, whether or not such an external plugin is used along with any PluginBuddy plugin.

=Free Plugins=

Free plugins are provided as is. There is no guaranteed support that comes with them. Guaranteed support is limited only and mainly for our premium unmodified plugins.

=Bugs, Features and ETA on new updates=

With every new release of any plugin, there may be a new bug or two. You may also want to have new features added to specific plugins. All existing versions of all plugins can have bugs reported OR new features suggested. All of this is done via the [http://ithemes.com/forum official forums].

New updates are also usually released regularly and at the same time, at very different paces, depending on the current number of bugs, features, new plans and tasks at hand. Therefore it is the official policy that there is NO pre-defined ETA on any bug fix, feature imeplemention OR new update OR new plugin roll-out UNLESS otherwise specified specifically in writing somewhere by an official iThemes employee.

==Bugs, bug reports and bug fixes==

Bug reports are filed and noted as they are encountered (thanks for reporting them to us!). There is never any ETA on any bug fixes unless otherwise noted.

==Feature Requests==

Feature requests and feature suggestions are basically future suggested features that users can suggest, and/or future features PluginBuddy may consider adding to the future versions of the plugin(s) in question (again, thanks for suggesting new features!).

There is no guaranteed ETA on when such feature requests will be implemented, unless otherwise noted. All suggested features are just that: suggestions. They remain suggestions until they're confirmed as officially in the works and to be included. Even then, unless a feature is actually rolled out publicly, there is no guarantee any feature suggestion will be implemented. We do our best to try and accommodate as many feature suggestions as possible.

Also, there is no guarantee that any feature request suggested will be implemented, unless otherwise noted.

==ETA on new updates==

Just like bug fixes and new features, there is never a guaranteed date nor a guaranteed time frame on when new updates will roll out. We work every single day of the week, all the time, on our plugins and thus every day there is something new and improved happening in almost all our plugins daily. Whenever we are ready to release any new updates publicly, you'll find out by seeing the plugin update notice in your WordPress OR in your [http://ithemes.com/member/member.php Member's area].

=What does BETA mean?=

Some of PluginBuddy plugins may be in Beta status OR may have Beta features. BETA simply means that some feature or specific part of the plugin is currently still in testing mode, and can cause issues if not used properly. All BETA plugins/features are not yet 100% stable, and thus should NOT be relied on to be working properly OR working at all. Throughout the iThemes Codex, any time the word "Beta" is used in any form, it refers to Beta plugins, Beta features, Beta status and/or anything related to the Beta nature that is officially announced or mentioned as such by any iThemes staff or on any of the Plugin pages, or in this Codex.

Beta implies that any new features or plugins are very close to being released as 100% working very soon, and that there may still be some issues to fix or test more before removing the Beta status. Since no single software of any kind can be tested under every system and site configuration in the world, the Beta status enables the Beta features to be tested out by as many people on as many different websites and configurations as possible.

*Some points to keep in mind when using any BETA plugin/feature:
**1 : Make [http://pluginbuddy.com/purchase/backupbuddy/ FULL WordPress backups] before using ANY beta feature.
**2 : Beta means that the current software feature is NOT complete, and that you are NOT forced to use such a feature at all. You are advised to WAIT until the BETA status is removed.
**3 : Using any Beta feature of any kind, whether it is an entire plugin or something inside a plugin, means and shows that you are fully accepting any liability for any risks involved.
**4 : Using any Beta feature of any kind, whether it is an entire plugin or something inside a plugin, means and shows that you are fully aware that there are all different kinds of risks involved with such features.
**5 : If you are concerned about your important data or anything bad that might happen as a result of using any Beta feature, do NOT use such Beta features.
**6 : ALWAYS make full [http://pluginbuddy.com/purchase/backupbuddy/ BackupBuddy Backups of all your important data] before using any Beta software, whether that Beta software is from PluginBuddy or from any other place.
**7 : If any issues are found in Beta, they are usually added to the list of bug fixes to be released as a whole, or for the next big update, instead of being updated OR fixed individually on a case by case basis.
**8 : Beta features are recommended to test and play with on test sites/servers and configurations with any dummy data, as long as you have [http://pluginbuddy.com/purchase/backupbuddy/ full backups of all important data] still.
**9 : iThemes is not liable nor cannot be held accountable for any unwanted results resulting from the use of BETA features.
**10 : The very name and nature of BETA shows clearly, without any doubt, that there will most probably be issues and problems involved when such labeled features are used anywhere.
**11 : Support for Beta features may be very limited. We usually simply collect all reports related to Beta features and collect them all for one big update in the future.
**12 : If you lose any important data or settings anywhere, or encounter damaged data or settings anywhere, because of any Beta feature, we will not be able to help you and will simply tell you to revert to your previous [http://pluginbuddy.com/purchase/backupbuddy/ backups]. We will also tell you to always wait for BETA status to be removed before using any such features.

If you do not fully understand what Beta means, OR are not willing to fully accept and be fully liable for any risks involved because of using such Beta software, you should NOT use the Beta software in any manner. In such a case, you should simply wait until the Beta status is removed.

*[http://pluginbuddy.com/what-does-beta-mean/ Blog post announcing what BETA means]

=PluginBuddy Licenses=

==Plugin Conflicts==

Some times, external plugins may cause issues in detaching, deleting, generating OR saving license keys. Such plugins may also cause issues when you want to manually or automatically upgrade plugins when you try to solve licensing issues.

Following is a list of currently known plugins which cause license detaching, deleting, generating OR saving issues. Please disable the following plugins, even temporarily, while you perform all the steps of manually OR automatically upgrading the PluginBuddy plugins in question, and detaching, deleting, generating and saving license keys for them. Keep such plugins disabled UNTIL all license key issues are gone OR at least while you perform these steps.

*Plugins causing PluginBuddy licensing issues
**'''W3 Total Cache or WP Super Cache :''' If you are using any caching plugin like '''W3 Total Cache''' or '''WP Super Cache''', please disable it temporarily and then carry out any required steps. You can re-enable the plugin in the end after everything works in terms of the licenses.
***Fix: Follow the above steps to fix this issue. [http://ithemes.com/forum/index.php?/topic/19436-backupbuddy-license-issue/#p92171 Steps also explained by BackupBuddy customer Laura (thanks!)]
**'''Any other CACHING or related plugin:''' Try disabling such plugins, performing the required steps, and then re-activating the Caching or related plugins in question.

*Related Links
**1 : [http://ithemes.com/forum/index.php?/topic/19079-wont-let-me-set-a-license-key/#p91663 W3 Total Cache plugin conflict and solution]
**2 : [http://ithemes.com/forum/index.php?/topic/19436-backupbuddy-license-issue/#p92171 W3 Total Cache plugin conflict and solution]
**3 : [http://ithemes.com/forum/index.php?/topic/19041-license-problem-causes-loss-of-all-bb-settings-way-to-get-them-back/ WP Super Cache conflict and solution]

==September, 2011 Licensing Issues==

'''This issue is now resolved and the update already out.''' Upgrade manually to the latest versions of the plugins and such issues will go away.

Some users reported (in mid-September, 2011) that they were having issues with their license inside the Licenses area of different PluginBuddy plugins, including BackupBuddy.

Remember: All your PluginBuddy plugins, including BackupBuddy, will CONTINUE WORKING PERFECTLY even with these licensing issues. You can keep using the plugins exactly how you want them even during these licensing issues. Your plugins are NOT affected by this licensing situation in any manner.

Your membership is also completely fine and you have NOT lost any license(s). The issue is happening to some customers who simply need to upgrade manually to the latest version of their plugin, if the automatic upgrade does not work.

*Plugins with the update versions which remove this issue completely
**ALL PluginBuddy Products

*You can upgrade via one of the following:
**Automatically upgrade to the latest version
**Manually update by downloading the latest zip version of your PluginBuddy plugin from your Member's panel and then
***Overwrite your existing plugin directory via FTP with the new files.
***De-activate the existing plugin, delete it via your '''WordPress --> Plugins''' area and then upload the newly downloaded zip file. Then re-activate the plugin.
**That will remove the issue completely.
*DETACH the key and then RE-ATTACH the license key for the specific site in question IF licensing still shows issues AFTER manually upgrading (for example, manually upgrading to at least BackupBuddy 2.2.24 - other plugins have their own new version numbers - check your Member's area for the latest version download)
*Also make sure to DETACH the key, DELETE that same AND any other keys related to that specific site from the entire licenses area, and then GENERATE a new key for that site IF detaching and re-attaching the license key does not work AFTER manually upgrading (for example, manually upgrading to at least BackupBuddy 2.2.24 - other plugins have their own new version numbers - check your Member's area for the latest version download)

[http://ithemes.com/forum/index.php?/topic/6691-read-this-first-pluginbuddy-licensing-issues/page-2/#p85977 First reports]

LoopBuddy

2011-11-04T18:47:33Z

Bes: Changed "function.php" to the correct name "functions.php" /* Adding the Dynamic Loop Function to Your Theme */

'''Release date:''' July 19, 2011

==LoopBuddy Overview==

LoopBuddy is a tool that overwrites a WordPress Loop using a combination of a custom query and a custom Loop layout. You can also create your own Loops using the LoopBuddy shortcode and LoopBuddy widget.

===Query Editor===

If LoopBuddy was a body, the Query Editor would be the brain, with the Layout Editor being the outside bodily appearance.

[[File:Query_editor.png|400px|border|LoopBuddy Query Editor]]

With the Query Editor, you can create Query Groups. Each Query Group defines what data a WordPress Loop is supposed to pull in.

With the Query Editor, you can define:

* Which posts to gather
* Whether pagination or comments are enabled
* Whether to use the default post ID (if on a single post or page)
* and much, much more...

[[File:Query_editor_options.png|400px|border|Query Editor Options]]

===Layout Editor===

The Layout Editor controls how a particular WordPress Loop is supposed to be structured. At the heart of the Layout Editor is Layout Tags. There are several Layout Tags built-in, but you can use the LoopBuddy Hooks to create your own custom Layout Tag and Layout Tag Items.

[[File:Layout_editor.png|400px|border|LoopBuddy Layout Editor]]

With the Layout Editor, simply drag Layout Tags into the appropriate area. If you create a new Layout, there are several default tags that are added automatically.

[[File:Layout_editor_options.png|500px|border|Layout Editor Options]]

===Global Settings===

The Global LoopBuddy Settings allow you to globally override a default WordPress Loop. If your theme doesn't support the Loop Standard, you'll see an error message at the top.

If your theme does support the Loop Standard, you can use the options to override the default WordPress Loops in various areas of the site.

Although LoopBuddy attempts to work without a custom Query, it is highly advisable to use a custom Query and Layout.

[[File:Loopbuddy_settings.png|500px|border|General Settings]]

===Import/Export===

Within the Query and Layout editors, you can export/import the items so you can use the same Queries/Layouts on a different site.

===LoopBuddy Widget===

You can use the LoopBuddy Widget to display a LoopBuddy Query/Layout in any widgetized area of a site. Please note that you must have a Query AND a Layout for the widget to work.

===LoopBuddy Shortcode===

The LoopBuddy shortcode takes two attributes: a Query ID and a Layout ID. Please note that you must have a Query AND a Layout for the widget to work.

Simply insert the shortcode into a post or page:

<pre class='brush:php'>
[loopbuddy query_id='0' layout_id='0']
</pre>

===LoopBuddy Full 1 Hour Webinar===

Learn the ins and outs of LoopBuddy with the following 1 hour Webinar, made by our very own [http://www.webdesign.com Webdesign.com]
{{#ev:vimeo|26482158|580|363}}

==The Loop Standard==
The Loop Standard divides a loop into two main concepts: a loop and one or more entries.

Both a loop and an entry have three sections: a header, a content section, and a footer. The header contains title information, any meta information, and any necessary navigation links. The content section contains the content relevant to that loop or entry. The footer section is a place to hold additional or duplicate meta information and navigation links.

===The Loop Explained===

The content of a loop is a bit more complex than the content of an entry as a loop's content contains the entries. To better visualize this, here is the basic structure described so far:

* Loop
** Header
*** title
*** navigation
*** meta
** Content
*** Entry
**** Header
***** title
***** navigation
***** meta
**** Content
**** Footer
***** navigation
***** meta
*** Additional entries...
*** Footer
**** navigation
**** meta

The idea is that each section is broken out in a repeatable pattern. This makes styling easier as any content that follows this form can be styled without having to first read through the code in order to understand the structure.

You may notice that there are titles, navigation, and meta for both the entries and the loop. This is because some titles, navigation, and meta are relevant to the loop (the title archive, navigating between pages of posts, or information about an author in an author archive) while other titles, navigation, and meta are relevant to the entry (the blog post's title, navigating through a page split into multiple pages, or a blog post's category information). The rule of thumb is that if the information is specific to an individual post's, page's, etc content, it is an entry-level structure; otherwise, it is a loop-level structure.

Each of these sections have a specific class in the Loop Standard. Here is the structure again with the classes replacing the names:

* loop
** loop-header
*** loop-title
*** loop-utility
*** loop-meta
** loop-content
*** hentry
**** entry-header
***** entry-title
***** entry-utility
***** entry-meta
**** entry-content
**** entry-footer
***** entry-utility
***** entry-meta
*** hentry...
** loop-footer
*** loop-utility
*** loop-meta

Notice the "hentry" class. This looks odd but is actually generated by WordPress internally. It is produced by the <code>post_class()</code> function that is in 2010 and 2011 theme template files. So when you see "hentry", know that this is simply the div that looks like :

<pre class='brush:php'>
<div <?php post_class(); ?>></div>
</pre>

Here is the standard loop in practice:
* loop
** loop-header
*** loop-title (page-title)
** loop-content
*** hentry
**** entry-header (title)
***** entry-title (post-title)
***** entry-meta (post-meta)
***** entry-meta date (date)
**** entry-content (post-content)
**** entry-footer (meta-bottom)
***** entry-meta alignright (alignright)
***** entry-meta alignleft (meta-bottom-left)
*** hentry...
** loop-footer
*** loop-utility (paging)

Not all the elements from above structure examples were used since not all were needed. In the end, only three elements had to be added. The rest of the changes were simply modifying or adding classes to conform to the Loop Standard structure. For some elements, such as "date", the "date" class remained while also getting the "entry-meta" class. This makes it clear what type of structure it is while still giving the additional meaning of it being a container for the date.

===Modifying a Theme to Use LoopBuddy===

Here's an example of TwentyTen's index.php file before it begins loading the various templates:

<pre class='brush:php'>
<?php if ( ! dynamic_loop() ) : ?>
<div class="loop">
<?php
/* Run the loop to output the posts.
* If you want to overload this in a child theme then include a file
* called loop-index.php and that will be used instead.
*/
get_template_part( 'loop', 'index' );
?>
</div>
<?php endif; ?>
</pre>

When <code>dynamic_loop()</code> is executed, LoopBuddy searches to see if this particular loop should be overridden. If not, the normal loop executes. If so, then LoopBuddy overwrites the content of the loop with LoopBuddy content.

===Example of TwentyTen Using the Loop Standard===
Here's an example TwentyTen Loop converted to using the Loop Standard

<pre class='brush:php'>
<?php if ( have_posts() ) while ( have_posts() ) : the_post(); ?>

<div class="loop-content">
<div id="nav-above" class="navigation loop-utility loop-utility-above">
<div class="nav-previous"><?php previous_post_link( '%link', '<span class="meta-nav">' . _x( '←', 'Previous post link', 'twentyten' ) . '</span> %title' ); ?></div>
<div class="nav-next"><?php next_post_link( '%link', '%title <span class="meta-nav">' . _x( '→', 'Next post link', 'twentyten' ) . '</span>' ); ?></div>
</div>

<div id="post-<?php the_ID(); ?>" <?php post_class(); ?>>
<div class="entry-header">
<h1 class="entry-title"><?php the_title(); ?></h1>

<div class="entry-meta">
<?php twentyten_posted_on(); ?>
</div>
</div>
<div class="entry-content">
<?php the_content(); ?>
<?php wp_link_pages( array( 'before' => '<div class="page-link">' . __( 'Pages:', 'twentyten' ), 'after' => '</div>' ) ); ?>
</div>
<div class="entry-footer">
<?php if ( get_the_author_meta( 'description' ) ) : // If a user has filled out their description, show a bio on their entries ?>
<div id="entry-author-info" class="entry-meta entry-meta-below">
<div id="author-avatar">
<?php echo get_avatar( get_the_author_meta( 'user_email' ), apply_filters( 'twentyten_author_bio_avatar_size', 60 ) ); ?>
</div>
<div id="author-description">
<h2><?php printf( esc_attr__( 'About %s', 'twentyten' ), get_the_author() ); ?></h2>
<?php the_author_meta( 'description' ); ?>
<div id="author-link">
<a href="<?php echo get_author_posts_url( get_the_author_meta( 'ID' ) ); ?>">
<?php printf( __( 'View all posts by %s <span class="meta-nav">→</span>', 'twentyten' ), get_the_author() ); ?>
</a>
</div>
</div>
</div>
<?php endif; ?>

<div class="entry-utility">
<?php twentyten_posted_in(); ?>
<?php edit_post_link( __( 'Edit', 'twentyten' ), '<span class="edit-link">', '</span>' ); ?>
</div>
</div>
</div>
<div class="loop-footer">
<div id="nav-below" class="navigation loop-utility loop-utility-below">
<div class="nav-previous"><?php previous_post_link( '%link', '<span class="meta-nav">' . _x( '←', 'Previous post link', 'twentyten' ) . '</span> %title' ); ?></div>
<div class="nav-next"><?php next_post_link( '%link', '%title <span class="meta-nav">' . _x( '→', 'Next post link', 'twentyten' ) . '</span>' ); ?></div>
</div>
</div>

<?php comments_template( '', true ); ?>
</div>

<?php endwhile; // end of the loop. ?>

</pre>

After updating the template files, go through the theme's style.css file in order to update class references to match the new ones. Here are some basic replacements to make:

* .page-title → .loop-title
* .title → .entry-header
* .post-title [h1, h2, h3, etc] (any instance of .post-title followed by a header tag) → .entry-title
* .post-title → .entry-title
* .post-meta → .entry-meta
* .post-content → .entry-content
* .meta-top → .entry-header
* .meta-bottom → .entry-footer
* .post → .hentry
* .paging → .loop-utility

===Showing LoopBuddy Theme Support===

After you've modified your theme's loops, show LoopBuddy that your theme supports it by adding in the following line to your theme's functions.php file:

<pre class='brush:php'>
// Add support for the Loop Standard
add_theme_support( 'loop-standard' );
</pre>

===Adding the Dynamic Loop Function to Your Theme===
The Dynamic Loop function must be added to your theme's functions.php file. This is achieved by adding the following code to the end of the function.php file:

<pre class='brush:php'>
// Add dynamic_loop function for LoopBuddy

/*
Copyright 2011 iThemes (email: support@ithemes.com)

Written by Chris Jean
Version 0.0.1

Version History
0.0.1 - 2011-02-28 - Chris Jean
Initial version
*/

if ( ! function_exists( 'dynamic_loop' ) ) {
function dynamic_loop() {
global $dynamic_loop_handlers;

if ( empty( $dynamic_loop_handlers ) || ! is_array( $dynamic_loop_handlers ) )
return false;

ksort( $dynamic_loop_handlers );

foreach ( (array) $dynamic_loop_handlers as $handlers ) {
foreach ( (array) $handlers as $function ) {
if ( is_callable( $function ) && ( false != call_user_func( $function ) ) ) {
return true;
}
}
}

return false;
}
}

if ( ! function_exists( 'register_dynamic_loop_handler' ) ) {
function register_dynamic_loop_handler( $function, $priority = 10 ) {
global $dynamic_loop_handlers;

if ( ! is_numeric( $priority ) )
$priority = 10;

if ( ! isset( $dynamic_loop_handlers ) || ! is_array( $dynamic_loop_handlers ) )
$dynamic_loop_handlers = array();

if ( ! isset( $dynamic_loop_handlers[$priority] ) || ! is_array( $dynamic_loop_handlers[$priority] ) )
$dynamic_loop_handlers[$priority] = array();

$dynamic_loop_handlers[$priority][] = $function;
}
}

</pre>

==LoopBuddy Downloads==

===Example TwentyEleven Theme===

Here's an example TwentyEleven theme that has been modified to be compatible with LoopBuddy.

[[Media:twentyeleven-loopstandard.zip|TwentyEleven Loop Standard]]

===Example Layout Tag===

Check out the LoopBuddy Marquee Plugin: [[Media:Loopbuddy_marquee.zip|LoopBuddy Marquee]] as an example of creating custom tags.

===Example Queries/Layouts===

Please see below for a ZIP file of some sample layouts and queries that can be imported.

[[Media:Loopbuddy_export.zip|LoopBuddy Export File]]

==LoopBuddy Query==
The LoopBuddy Query is where you create Queries, which in turn create and produce the Loops you want in WordPress. From showing certain posts to the number of posts, categories, posts with specific meta values and more, the '''LoopBuddy Query''' area is where you specify exactly what should be shown, and exactly what should not be shown, in a LoopBuddy output.

===Advanced Meta Queries===

With LoopBuddy 1.2, LoopBuddy Queries now allow you to perform some very powerful advanced Meta queries. Here is a video explaining and giving some examples of the advanced meta queries:

{{#ev:youtube|4snQn7PDylE|580|363}}
*[http://pluginbuddy.com/loopbuddy-1-2-released/ Blog Post announcing Advanced Meta Queries in LoopBuddy 1.2]

===Advanced Taxonomy Queries===

With LoopBuddy 1.2, LoopBuddy Queries now allow you to perform some very powerful advanced Taxonomy queries. Here is a video explaining and giving some examples of the advanced Taxonomy queries:

{{#ev:youtube|ta0GZA5jz9g|580|363}}
*[http://pluginbuddy.com/loopbuddy-1-2-released/ Blog Post announcing Advanced Taxonomy Queries in LoopBuddy 1.2]

==Hooks==

LoopBuddy allows you to create custom tags for the Layout editor. This is advanced functionality, so please don't attempt these steps if you are not intimately familiar with PHP and how LoopBuddy operates.

To create the custom tag, you must use the following hooks.

===Creating a new Custom Tag===

<pre class="brush:php">
<?php
add_filter( 'pb_loopbuddy_custom_tags', 'my_custom_tag_add' );
function my_custom_tag_add( $custom_tags ) {
//Always return $custom_tags
$custom_tags[ 'start_wrap' ] = array(
'My Tag Label',
array(
'wrap' => 'div',
'custom_class' => 'default class'
)
);
return $custom_tags;
} //end my_custom_tag_add

//Start off with the tag name, give the tag a label, and pass it which items it supports (all should ideally contain the 'wrap' and 'custom_class' items
?>
</pre>

Here are some built in tag items that you can choose from:

* link_text
* custom_url
* custom_class
* link_title
* before_text
* after_text
* meta_key
* max_width
* max_height
* shortcode
* author_link_destination
* user_profile
* permalink
* attachment_link_display
* separator
* text
* date_format
* comment_number_zero
* comment_number_one
* comment_number_more
* post_date
* bloginfo
* content_more
* url_display
* image_size

===Creating a new custom tag item===

<pre class='brush:php'>
<?php
add_filter( 'pb_loopbuddy_tag_items', 'my_custom_item_add' );
function my_custom_item_add( $loopbuddy_items ) {
//Always return $loopbuddy_items

$loopbuddy_items[ 'my_custom_item' ] = array(
'function' => 'callback_function',
'args' => array(
'label' => __( 'Link Text', 'LION' ),
'tip' => __( 'Optional text for link. Leave blank to use link as the text.', 'LION' ),
'options' => array( 'option1', 'option2' )
)
);
return $loopbuddy_items;
} //end my_custom_item_add

/* $settings are the arguments passed for the tag item and looks like this
[label] => HTML Wrapper
[tip] => Choose which HTML element to wrap around the item
[options] => Array
(
[0] => none
[1] => span
[2] => div
[3] => p
[4] => h1
[5] => h2
[6] => h3
[7] => h4
[8] => h5
[9] => h6
)

[key] => wrap
[settings] => Array
(
[image_size] => thumbnail
[max_width] =>
[max_height] =>
[wrap] => p
[before_text] =>
[after_text] =>
[custom_url] =>
[custom_class] => attachment
[tag] => wp_get_attachment_image
)

)
*/
function callback_function( $settings ) {
$defaults = array(
'key' => '',
'label' => '',
'tip' => false,
'settings' => array(),
'options' => array()
);
extract( wp_parse_args( $settings, $defaults ) );
//Output HTML for the item
} //end callback_function

?>
</pre>

===Callback function for displaying the tag - pb_loopbuddy_tag_callback-{tag_name}===
<pre class='brush:php'>
<?php
/*$settings contains the tag items and the tag item's value
Example
Array
(
[image_size] => thumbnail
[max_width] =>
[max_height] =>
[wrap] => p
[before_text] =>
[after_text] =>
[custom_url] =>
[custom_class] => attachment
[tag] => wp_get_attachment_image
)
*/

//Add header code
add_action( 'pb_loopbuddy_tag_header-mytagname', 'my_custom_tag_header' );
function my_custom_tag_header( $settings ) {
echo "my header, notes, or other code";
//Render your tag based on its settings
} //end my_custom_tag_header

//Add footer code
add_action( 'pb_loopbuddy_tag_footer-mytagname', 'my_custom_tag_footer' );
function my_custom_tag_footer( $settings ) {
echo "my footer, notes, or other code";
//Render your tag based on its settings
} //end my_custom_tag_header

add_filter( 'pb_loopbuddy_tag_supports-mytagname', 'my_custom_tag_supports' );
//Return an array of what tag items the tag supports
function my_custom_tag_supports( $support_tag_items ) {
return array( 'wrap', 'link_text', 'before_text', 'after_text', 'custom_class' );
//Render your tag based on its settings
} //end my_custom_tag_supports
?>
</pre>

===Rendering the Tag on the Front-end - pb_loopbuddy_render-{tag_name}===

<pre class="brush:php">
<?php
add_filter( 'pb_loopbuddy_render-mytagname', 'mytagname_frontend', 10, 2 );
function mytagname_frontend( $post_object, $tag_items ) {
/* $tag_items look like this
(
[wrap] => none
[link_text] => Edit Post
[before_text] =>
[after_text] =>
[custom_url] =>
[custom_class] =>
[tag] => edit_post_link
)
*/
$return = false; //Populate the $return variable
$return = pluginbuddy_loopbuddy_render_slotitems::get_output( $return, $post_object, $tag_items, true ); //The last argument is skip_before text
return $return;
} //end mytagname_frontend
?>
</pre>

===Ignoring Post Types in the Layout Editor===

There will be certain post types that are public and have a public user interface, but the user would still not like to be able to configure override settings in the LoopBuddy Settings page.

A plugin author can use the following hook to remove these post types:

<pre class="brush:php">
<?php
add_filter( 'pb_loopbuddy_exclude_post_types', 'myplugin_exclude_post_types' );
function myplugin_exclude_post_types( $post_types_to_exclude ) {
$post_types_to_exclude[] = 'my_custom_post_type';
return $post_types_to_exclude;
}
?>
</pre>

==Shortcodes==

Shortcodes basically allow almost any plugin or custom code to be plugged in anywhere in WordPress.

LoopBuddy supports shortcodes fully, allowing you to put any shortcode, whether from a plugin or your own, into any place in LoopBuddy Layout, including the '''Pre-Loop Text / HTML''', '''Post-Loop Text / HTML''' and '''No Results Text / HTML''' sections. This probably makes the already powerful LoopBuddy the only most powerful way to control all your content, loops and display on your site.

[http://ithemes.com/codex/page/General_WordPress_Related#Editing_or_Adding_Stuff_to_Functions.php Info on editing or adding stuff to Functions.php]

===Show Category/Taxonomy Description on NON-Archive pages via Shortcode===

Category Descriptions are a little more sophisticated than other post related variables because if there is more than one category being used, then it will be hard for WordPress to display ALL descriptions nicely OR one category (which one?).

*Outside of archive pages, to display Category Descriptions (or any taxonomy description) you have to do the following:
**1 : Put the following anywhere (usually near the end of the file) in your theme's custom functions.php file (it creates a shortcode you'll use to display the description of a Category or any Taxonomy):
<pre class="brush:php">add_action( 'init', 'lb_cat_init' );
function lb_cat_init() {
add_shortcode('taxdescription', 'lb_the_description');
} //end lb_cat_init
function lb_the_description() {
global $post;
if ( !is_object( $post ) ) return;
$terms = get_post_meta( $post->ID, 'description_terms', true );
$taxonomy = get_post_meta( $post->ID, 'description_taxonomy', true );
$return = '';
if ( $terms && $taxonomy ) {
if ( !is_array( $terms ) ) {
$terms = explode( ',', $terms );
}
foreach ( $terms as $term_name ) {
$term = get_term_by( 'slug', $term_name, $taxonomy );
if ( !$term ) continue;
$description = get_term_field( 'description', $term->term_id, $term->taxonomy );
if ( empty( $description ) || !$description ) continue;
$return .= apply_filters( 'pb_the_content', $description );
}
}
return $return;
} //end lb_the_description</pre>
**2 : In the posts you want to show the category description, add the following 2 custom field names and values:
'''Custom Field Name''' ----- '''Custom Field Value'''

description_taxonomy ----- category

description_terms ----- books '''''(OR any category name you have)'''''

**3 : Add a Shortcode Tag to your LoopBuddy layout which has the following shortcode in it:

<code><strong>[taxdescription]</strong></code>

That will show the category description anywhere you put the shortcode.

*Links with related info:
**[http://ithemes.com/forum/index.php?/topic/18153-use-of-category-description/ Use of Category Description - LoopBuddy Forums]
**[http://codex.wordpress.org/Function_Reference/category_description category_description on WordPress Codex]
**[http://codex.wordpress.org/Function_Reference/term_description term_description on WordPress Codex]

===Show Custom Page Title for Same LoopBuddy Layout on Different Pages via Shortcode===

*One awesome example of using Shortcodes with LoopBuddy is to show a custom page title, along with any LoopBuddy Layout content, where different pages use the same LoopBuddy Layout. Our awesome LoopBuddy customer Bruce provided the following info to help you all with that:
**1 : Put the following anywhere (usually near the end of the file) in your theme's custom functions.php file:
<pre class="brush:php">
function return_title() {
return '<h1>'.get_the_title().'</h1>';
}
add_shortcode('pg_title', 'return_title');</pre>
**2 : Add
<code><strong>[pg_title]</strong></code>

anywhere in the LoopBuddy Layout where you want to show the custom page title.

That will show the custom page title just for that specific post/page where the Layout is being shown.
*Related links:
**[http://ithemes.com/forum/index.php?/topic/18046-displaying-the-page-title-on-which-i-am-using-loop-buddy/ LoopBuddy user Bruce asking about and then sharing the code to show custom Page Titles on each Page where the same LoopBuddy Layout is used]

==External Plugins Compatibility==

LoopBuddy is one of those rare plugins which can play well with many external plugins. However, any external plugin compatibility is NOT guaranteed in any manner, since external plugins are not covered nor supported by PluginBuddy in any manner or fashion.

If there is a problem when any other plugin is used with LoopBuddy, it does not mean there is a bug in LoopBuddy. First you should check if there is a problem in the other plugin (since LoopBuddy already currently works without any issues in each and every aspect of its publicized features). Then you have to see if the problem exists when the other plugin is de-activated and LoopBuddy is kept activated. Only after such steps and more analysis can we at PluginBuddy devote any time or resources to see whether or not there is something in LoopBuddy that can be fixed, enhanced or improved to make it work better with the external plugin in question, if that external plugin is not the source of the problem.

===Custom Post Types===
At this time, Custom Post Types UI is the only supported plugin in LoopBuddy for creating custom post types. We recommend you try and use that to create post types.

Otherwise, you should add custom post types directly to your functions.php file in your current theme.

*Related links
**[http://wordpress.org/extend/plugins/custom-post-type-ui/ Custom Post Types UI plugin]
**[http://codex.wordpress.org/Post_Types Creating Post Types in WordPress]

===Page Navigation===

At this time, WP-PageNavi is the only supported plugin in LoopBuddy for having custom page navigation. We strongly recommend you try it for any of your custom page navigation needs.

*Related link
**[http://wordpress.org/extend/plugins/wp-pagenavi/ WP PageNavi WordPress Plugin]

===Customize Excerpts===

At this time, Advanced Excerpt is the only supported plugin in LoopBuddy for allowing custom lengths and formatting for excerpts in WordPress.

*Related link
**[http://wordpress.org/extend/plugins/advanced-excerpt/ Advanced Excerpt WordPress Plugin]

==LoopBuddy FAQ==

Here are some frequently asked or encountered LoopBuddy questions and setups, and their answers.

===Sort Custom Field Values by Meta Value (Character or Numeric)===

*Custom Field values can be sorted by meta value (character or numeric).
*Only ONE meta item can be used to sort at one time.
**Using multiple meta items will assume you would like an advanced meta query, and sorting will be ignored in such a case. '''This is a WordPress limitation.'''
*Sort Custom Field Values via the following steps (assuming you already have several posts with the same custom field):
**1 : Change the Order By parameter to either "'''Meta Value'''" or "'''Numeric Meta Value'''".
**2 : Go to Post Meta Parameters and click "'''Add Meta'''".
**3 : Set the '''Meta Key''' and '''Meta Values''' you would like to search for and sort by.
**4 : Save the query.
**5 : Assign the query to a post or section and observe the results.

===LoopBuddy does not work on static Posts page===

*LoopBuddy will NOT work on pages set as Static Posts Page in '''WordPress --> Settings --> Reading --> Front Page Displays --> Posts Page''' section. There is a good reason for it and a great workaround.
** Reason
***The Reading Screen in the WordPress Settings [http://codex.wordpress.org/Settings_Reading_Screen Settings --> Reading Screen Settings] is necessary when you want to tell WordPress that your blog content doesn't reside on the home page.
***For example, you have selected a Front Page, which will tell WordPress, "Use this page instead of showing a default blog layout."
***Since there is technically no longer a blog layout, WordPress wants to know, "Where can I find your blog content?"
***This is how WordPress works, and not a LoopBuddy bug. There is a great flawless way to get exactly what you want with the below workarounds, though.
**Workaround (any one of this will work - we recommend the PREFERRED LoopBuddy way to do it!)
*** Not have a section on your site with your blog content (readers will only be able to access your posts via category and date archives).
*** Create a page to point WordPress to, and WordPress will take care of the rest and display the appropriate blog content.
*** '''PREFERRED:''' With LoopBuddy, however, you don't have to specify a "Blog" section in WordPress.
**** You can create a regular page.
**** Allow LoopBuddy to create a blog section for you either via '''LoopBuddy --> Settings''' option OR by choosing the '''LoopBuddy options in the Post/Page Editor page''' for the page you just created.
**** WordPress doesn't need to know about it in this particular case, and it won't hurt your site in the least. You do NOT have to change the '''WordPress --> Settings --> Reading --> Front Page Displays --> Posts Page''' settings for this option to work perfectly.
*Threads and pages with more detailed info of the setup and info related to the above exact solutions
**http://ithemes.com/forum/index.php?/topic/17845-unable-to-get-loopbuddy-working/
**http://codex.wordpress.org/Settings_Reading_Screen

===Make a Custom Field (or almost anything) Clickable===
With the power of different tags in LoopBuddy Layout, you can make almost anything clickable without editing a single file. This is extremely useful when you want to make something like a Custom Field, which is text by default, clickable automatically in any or every loop.
*Steps to perform in your LoopBuddy Layout:
**1 : Start with a Text tag (first Text tag) which has the content: <code><a href="</code>
**2 : Next comes anything, including a Custom Field tag. This is the link.
**3 : Now comes another Text tag (second Text tag) which has the content: <code>"></code>
**4 : Now comes anything to show the link. It can be the same Custom Field tag again as #2 above, another custom field, or any text or image you wish.
**5 : Another Text tag (3rd Text tag) with the following content: <code></a></code>
That's it!
*Related thread
**http://ithemes.com/forum/index.php?/topic/16971-text-before-single-custom-field-and-url/

===Search within a LoopBuddy Query===

You can have search widgets which actually search specific LoopBuddy queries for the parameters you specify. There are many different ways of achieving this with LoopBuddy.

Check out the forum thread [http://ithemes.com/forum/index.php?/topic/16606-searching-within-a-loopbuddy-query/ Searching Within a LoopBuddy Query] for more details.

==Video Tutorials and Tips==
These different video tutorials and tips can help you figure out more things about LoopBuddy. Remember, these videos show LoopBuddy and related things that were the most recent/updated as of the date of that video. Things may have changed in actual LoopBuddy since then.
# [http://ithemes.com/forum/index.php?/topic/18160-loop-buddy-placement/#p85184 Show custom static homepage content and 3 latest blog excerpts under it]

==Additional Resources==
# [http://pluginbuddy.com/purchase/backupbuddy/ Purchase BackupBuddy]
# [http://pluginbuddy.com/tutorials/ PluginBuddy Tutorials]
# [http://pluginbuddy.com/ PluginBuddy.com]
# [http://pluginbuddy.com/support/ Support Forums]

[[Category:PluginBuddy]]

BackupBuddy: Error Codes

2011-11-03T18:13:04Z

Bes: Added /* 5445589 */ error code info

==3382==
<strong>Backup FAILED. Unable to successfully generate ZIP archive. Error #3382.12:20:04: Failed function backup_zip_files. Backup terminated.</strong>

* The 3382 error literally means that both command line zip AND pclzip were unable to create a .zip file and failed for some reason.
* Possible causes:
** Command line zip is being actively killed. (Cheapest packages at Godaddy kill off exec() within about 10 seconds, throwing the user into compatibility mode which cannot handle larger sites).
** Permissions may be blocking backup file creation. Make sure permissions are set to 755 for the /wp-content/uploads/ directory recursively.
** Your hosting account may not have enough free space to create the backup file.
* Possible solutions:
*** Verify permissions are set correctly for /wp-content/uploads/ recursively to 755.
*** Verify allowed disk usage isn't close or exceeded. (ie Your hosting account is limited to 5GB and you've used 4.95GB.)
*** Reducing backup size often helps. (directory exclusion, etc)
*** Turning Zip Compression on or off may help.
* Related link:
** http://ithemes.com/forum/index.php?/topic/17953-backup-failure/#p85314

==9001==
'''Unable to read database table wp_redirection_logs. Your backup will not include data from this table (you may ignore this warning if you do not need this specific data). This is due to the following error: MySQL client ran out of memory in /www/wp-content/plugins/backupbuddy/backupbuddy.php on line 1757'''

* '''MySQL client ran out of memory'''
** This is typically caused by your PHP memory limit being low, resulting in part of the data returned being clipped. If you do not need the data from this specific table of the database to be backed up then you may safely ignore this. Some tables, such as wp_redirection_logs, contain logs that you most likely do not need.
** BackupBuddy attempts to increase the PHP memory limit on runtime but many hosts block this.
** Add/modify this line in your php.ini with a higher number than the default, such as: php_value memory_limit 128M
** PHP memory is separate from mysql memory. Your host has to up the mysql memory as it is not possible for you the client to do so at all.
* '''Unable to save result set'''
** This is typically caused by a corrupt database/table. [http://textpattern.com/faq/36/warning-unable-to-save-result-set/ Citation of problem.]
** Repair the database/table using a tool such as phpMyAdmin or the free plugin [http://wordpress.org/extend/plugins/wp-dbmanager/ WP-dbManager]
** Add this line to wp-config.php to allow WordPress to repair tables: define('WP_ALLOW_REPAIR', true)
* '''MySQL server has gone away'''
** MySQL server is dying, this is mostly a host issue. Probably need to contact host to get them to fix the issue.
* WordPress Revisions may also be clogging up the system
** Disabling WordPress' automatic revisions, or at least limiting how many to keep, can help with this error
** http://codex.wordpress.org/Editing_wp-config.php#Post_Revisions

==9002==
'''Unable to create temporary storage directory ((/www/wp-content/uploads/temp_xxxxxxxxxx)'''

*This error means that BackupBuddy was unable to create a temporary storage directory at the location listed in the error message. BackupBuddy must temporarily create this directory to place temporary files to be backed up into the ZIP file.
* Adjust permissions to allow write & directory creation access to your uploads folder. ie: /www/wp-content/uploads/

==9003==

'''BackupBuddy data file (backupbuddy_dat.php) missing or unreadable. There may be a problem with the backup file, the files could not be extracted (you may manually extract the zip file in this directory to manually do this portion of restore), or the files were deleted before this portion of the restore was reached. Start the import process over or try manually extracting (unzipping) the files then starting over. Restore will not continue to protect integrity of any existing data.'''

* This error is often caused by the importbuddy.php script being replaced by an older version during the unzip step. See [http://ithemes.com/codex/page/BackupBuddy:_Frequent_Support_Issues#Old_importbuddy_overwriting_on_unzip|Old importbuddy overwriting on unzip]
* This error is often caused by the server timing out before zip file extraction could complete.
** Manually extract files using either cPanel or extracting (unzipping) the files locally then uploading them & selecting the importbuddy.php advanced option to skip file extraction.
** Ask your server host to extend the maximum script execution time.
** Create a custom php.ini file if your host allows for this.
*** Tutorial: Create custom php.ini & enable in cPanel: http://pluginbuddy.com/tutorials/custom_php_ini/
*** Dreamhost users may use this tool if they do not want to use the above method: http://sxi.sabrextreme.com/dh-phpini
*** Increase php.ini max_execution_time
** Change hosts & let your current host know why you changed.
* Additional potential causes (very rare):
** File permissions not allowing reading of the backupbuddy_dat.php file.
** Incomplete backup. Verify the backup is marked as Good on the source site.

==9004==

'''Error! The unzip process reported success but the backup data file, backupbuddy_dat.php was not found in the extracted files. The unzip process either failed (most likely) or the zip file is not a proper BackupBuddy backup.''' (importbuddy.php)

* Manually extract backup ZIP. This usually resolves this issue.
* Force compatibility mode to see if it able to unzip to completion.
* Contact the host to see if they can verify that the Linux command line ZIP is set up properly.

==9005==

'''File extraction process did not complete successfully. Unable to continue to next step. Manually extract the backup ZIP file and choose to "Skip File Extraction" from the advanced options on Step 1.''' (importbuddy.php)
* This ZIP file was unable to be extracted for some reason.
** Unzipping may have taken too long and the PHP process halted.
** Server memory usage may have been exceeded.
** Server configuration may be blocking extracting of ZIP files.

* Attempt manual extraction & disable File Extraction from the advanced debugging options of Step 1.

==9006==
'''ERROR: Unable to connect to database server and/or log in. Verify the database server name, username, and password.''' (importbuddy.php)
* Verify the server address, your username, and your password. One of these settings is wrong.
* cPanel sometimes prefixes your username with a prefix. Check if this exists.

==9007==
'''Unable to select your specified database. Verify the database name and that you have set up proper permissions for your specified username to access it.''' (importbuddy.php)
* Verify the database name exists.
* Verify the mysql username has been granted ALL permissions to this database.

==9008==
'''ERROR: A database prefix is required for importing.''' (importbuddy.php)
* You must specify a WordPress database table prefix. Default is "wp_" without quotes.

==9009==
'''ERROR: Unable to find any database backup data in the selected backup.''' (importbuddy.php)
* Database file is missing from the backup.

==9010==
'''ERROR: Unable to import SQL query:''' (importbuddy.php)
* Something went wrong attempting to import this row into the database.
* If it says duplicate table or row then the user is importing/migrating into a database that has an existing WordPress installation with the same prefix. This could cause problems if it's a different install or a lot has changed.

==9011==
'''ERROR #9011. FTP/FTPs login failed on scheduled FTP. Credentials: username:password@server.com.'''
* Unable to log in to FTP or FTPs server due to a problem with the login credentials. Verify your username and password.

==9012==
'''FTP/FTPs file upload failed. Check file permissions & disk quota. Details: [additional details here]'''
* BackupBuddy was able to connect to the FTP server but was not able to upload the file.
* Verify file permissions allow writing and that enough disk space is available.

==9013==
'''Sorry! PHP version x.x or newer is required for BackupBuddy to properly run. You are running PHP version x.x.x.'''
* BackupBuddy currently requires PHP 5.x. See the Sales page or [[BackupBuddy]] codex page for the latest version requirements.
* Most hosts allow you to change the PHP version from their control panel.

==9014==
'''Fatal error. The database already contains a WordPress installation with this prefix (27 tables). Restore has been stopped to prevent overwriting existing data. Please go back and enter a new database name and/or prefix OR clear our your database prior to restoring again.'''
* WordPress already exists in the database/prefix combo entered.
* Choose a new prefix, database, or delete the existing WordPress tables from the database.

==9015==
'''Temp data directory is not writable. Check your permissions. (#directory#)'''
* Verify user permissions for this directory. Make sure the user can create & write files.
* Use SUPHP so PHP will run as your user. This insures it will have proper file/directory permissions.

==9016==
'''Archive file is not writable. is not writable. Check your permissions. (#directory#)'''
* Verify user permissions for this directory. Make sure the user can create & write files.
* Use SUPHP so PHP will run as your user. This insures it will have proper file/directory permissions.

==9017==
'''Temp data file is not creatable/writable. Check your permissions. (#directory#)'''
* Verify user permissions for this directory. Make sure the user can create & write files.
* Use SUPHP so PHP will run as your user. This insures it will have proper file/directory permissions.

==9018==
'''Database file is not creatable/writable. Check your permissions. (#directory#)'''
* Verify user permissions for this directory. Make sure the user can create & write files.
* Use SUPHP so PHP will run as your user. This insures it will have proper file/directory permissions.

==9019==
'''Invalid or corrupt AJAX data. (#DATA#)'''
* The backup data sent by the browser was invalid. Refresh and try again.
* Make sure you are using a modern browser on a stable internet connection.

==9020==
'''Unable to write to file [.htaccess/wp-config.php]. Permissions are preventing this file from being modified.'''
* Verify write permissions are properly configured for this file. Suggestion: 755.
* For .htaccess: Another option is to delete the .htaccess file & in the WordPress admin navigate to Settings: Permalinks & click the Save button to regenerate the file.

==9021==
'''PHP Timeout or Fatal Error Occurred'''
* "The page did not finish loading as expected. The most common cause for this is the PHP process taking more time than it has been allowed by your host (php.ini setting max_execution_time). If a PHP error is displayed above this can also cause this error. "
* Increase the maximum allowed PHP runtime by contacting your host or creating a php.ini file to override host settings (if allowed).
* If on the unzip step, manually extract the ZIP file on your local PC then upload or use another server-based software such as cpanel.

==9022==
'''Error: Unable to create backup storage directory `/www/wp-content/uploads/backupbuddy_backups/`. Please verify that proper write permissions are enabled to create this directory. You may also manually create this directory. If you do so make sure to give permissions to allow writing backups into this directory.'''

*This error means that BackupBuddy was unable to create a storage directory at the location listed in the error message. BackupBuddy must create this directory to place backup files into.
* Adjust permissions to allow write & directory creation access to your uploads folder. ie: /www/wp-content/uploads/

==5445589==
'''Error #5445589 – Invalid b/u serial Verify b/u directory writer permission'''
*This basically means there was a mismatch where the unique backup serial that ajax passed was not found server-side. There are 3 known reasons and fixes for this.
**1 : Fix the file and folder permissions on all your BackupBuddy folders and the wp-content/uploads folder.
**2 : Increase the available disk space.
**3 : Upgrade to the latest version of BackupBuddy. There have been updates to BackupBuddy to address this error more efficiently.

*Related forum threads
**[http://ithemes.com/forum/index.php?/topic/13796-error-5445589-invalid-backup-serial/ File permissions causing 5445589 error]
**[http://ithemes.com/forum/index.php?/topic/14834-error-5445589-invalid-backup-serial-0i64w23keq-fatal-error/ Increase the available disk space]

==Additional Resources==
# [[BackupBuddy: Advanced Debugging]]
# [http://pluginbuddy.com/purchase/backupbuddy/ Purchase BackupBuddy]
# [http://pluginbuddy.com/tutorials/ PluginBuddy Tutorials]
# [http://pluginbuddy.com/ PluginBuddy.com]
# [http://pluginbuddy.com/support/ Support Forums]

[[Category:PluginBuddy]]

PluginBuddy

2011-11-02T20:45:16Z

Bes: Added info about other caching related plugins, and explained more clearly that such plugins need to be deactivated TEMPORARILY only/* Plugin Conflicts */

Welcome to the PluginBuddy Knowledge Base - Tutorials, Technical Information, Debugging Information, and more.

=Premium Plugins=
* [[Ajax-Edit-Comments]]
* [[BackupBuddy]]
* DisplayBuddy
** [[Accordion]]
** [[Billboard]]
** [[Carousel]]
** [[CopiousComments]]
** [[FeaturedPosts]]
** [[Rotating Images]]
** [[RotatingText]]
** [[Slideshow]]
** [[Tipsy]]
** [[VideoShowcase]]
* [[EmailBuddy]]
* [[LoopBuddy]]
* [[Mobile]]
* [[TailoredLogin]]
* [[ThumbsUp]]
* [[VidEmbed]]

=Free Plugins (active)=
* [[Featured Text]]
* [[PB-Tweet]]
* [[ServerBuddy]]
* [[Tabber Widget]]
* [[ThemeMan]]
* [[S3 URLS]]
* [[YOURLS]]
* [[ContactBuddy]]

=Free Plugins (inactive)=
* [[WP Easy Uploader]]
* [[WP Developer Assistant]]
* [[Easy Theme and Plugin Updater]]
* [[Current Date & Time Widget]]

''[[:Category:PluginBuddy|View all PluginBuddy Wiki Pages]]''

=Misc. Documentation=
==Frequently Asked (Plugin) Questions==
*[[General Plugins FAQ]]

==License Manager Tutorial and Information==
*[[License Manager]]
==PHP Development & Advanced==
*[[.htaccess]]
*[[PHP]]
*[[Arrays]]

[[Category:PluginBuddy]]

=Translations (localization / internationalization)=

Many PluginBuddy plugins come with translation capability. That means such PluginBuddy plugins can be translated (aka localized) to other languages.

===How Translations Work===

PluginBuddy provides the capability to have a translation in such plugins. Anyone wanting to enhance PluginBuddy with specific language translations can do so voluntarily via Translation Files. Translation Files are simply language files created fully and solely by the volunteer community which use the already built in translation-capable features in many of the PluginBuddy plugins to allow such plugins to show text or outputs in different languages. Making PluginBuddy translation-capable is done by PluginBuddy. Creating, updating and sending in any language specific translation files to PluginBuddy is done by the volunteer community.

Anyone can create translation files, package them into the proper format and give PluginBuddy the final translated files that we will try to include in the next update for the plugin in question. We call such awesome people, who create or update the translation files and send us the full translation package files, '''Awesome Translator Volunteers''', and we are really thankful that they take the time to do such an awesome thing.

If you want to help us, you can translate any existing PluginBuddy plugin which supports internationalization (another way of saying localization or translation-capable) and then, once you're fully done, simply let us know in the forums the link to the final language files that we can directly save and simply try to include in any future updates for the plugin(s) in question.

===Tips on how to localize any PluginBuddy Plugin to any non-English language===

The following 9 tips can help you figure out how to approach translations, how to create translations, and how to send us the final translated file for any translation-capable PluginBuddy plugin:

*1 : Many of the PluginBuddy plugins are internationalized, meaning they have the capability to be translated, via actual external translation files, by any non-iThemes-staff Awesome Translator Volunteer who wishes such plugins to be translated to their language.
*2 : If a PluginBuddy plugin is currently not internationalized or you're not sure if it is, you can ask us in the [http://ithemes.com/forum Support Forums] and we'll let you know, or we'll have it included as a future translation feature request. After the translation capability is added to such a plugin, you can submit the actual translation file. Please remember though: we cannot help with creating, understanding or making any language translation files. Our Awesome Translator Volunteers do that voluntarily (you can too! keep on reading) and fully on their own.
*3 : There are MANY resources which teach you how to create and work with WordPress language files. Following are the official 3 directly by the WordPress community:
**1 : [http://codex.wordpress.org/WordPress_in_Your_Language WordPress in Your Language]
**2 : [http://codex.wordpress.org/Translating_WordPress Translating WordPress]
**3 : [http://codex.wordpress.org/I18n_for_WordPress_Developers What WordPress Localization in Plugins is mainly about]
*4 : Translations are sent in from volunteers from all over the world. As a courtesy, we sometimes package the actual language translation files (provided directly by the Awesome Translator Volunteers) in with the final product. If some translation is not included in the actual plugin even when the plugin has the capability to be translated, you can submit the final translation to us for consideration in the next update by posting on our forums OR you can include the translation in your own live or local WordPress install directly for your own use. More info on how to include your own language specific file for your own WordPress sites is in the resources listed in #3 above.
*5 : A translation included in with the final product does not guarantee the accuracy or quality of the translation. These files are from the Awesome Translator Volunteers, and correction of these files is also done by those Awesome Translator Volunteers.
*6 : If a translation is very inaccurate or incomplete, we can put out a request for a new translation from the volunteer community, or remove the translation from the packaged and final product. You can also let us know of any inaccuracies in any existing translation files by the Awesome Volunteers by providing us with the corrected final files. Please remember: we only accept final and full translation files that you yourself have already created or packaged properly. If you let us know only of the actual inaccuracies without providing the final correct files, we cannot make such changes ourselves to the translation files.
*7 : Unfortunately, PluginBuddy cannot work on, help with, create, nor make any updates to any specific translation files you may have, or may be working on, or want to work on. Our Awesome Volunteers do that and simply give us the final files for inclusion or consideration.
*8 : If you have corrections for any existing translation in form of final proper format translation files for an existing language, OR want to provide the final and proper translation files for a new language, please post a new thread in the appropriate product category in the [http://ithemes.com/forum/ PluginBuddy Support Forums] with the final translations files. If you have any support questions on how to create or make language specific translation files, or how translation files work, you can do so on the [http://wordpress.org/support/ WordPress forums], as such support questions are outside the scope of what PluginBuddy support guarantees with your iThemes membership.
*9 : Any final translation file provided by you (or any other Awesome Volunteer) on the support forums will then be saved and filed as a future enhancement request for the future updates of the plugin(s) in question. In your support forum thread, where you share the final complete translation files you inclusion, you can upload your files directly to the forums OR upload them somewhere and link to them in your support forum thread. We will then download and save such files. Remember please: we cannot guarantee looking inside such files or verifying that they are correct in any manner (because of so many languages in the world and so many possible language files everywhere).

Thank you SO MUCH for being interested in providing translation files for our PluginBuddy plugins. We hope you will become one of our Awesome Translator Volunteers, in addition to being our AWESOME CUSTOMER, and create/update any language-specific translation file package and provide it to us so that we can consider including it in future updates.

===Resources for understanding, creating, updating and submitting final translation files===
*Here are the 3 official resources again which you can use to create, update, start work on and finish translation on any of the translation-capable PluginBuddy plugins:
**1 : [http://codex.wordpress.org/WordPress_in_Your_Language WordPress in Your Language]
**2 : [http://codex.wordpress.org/Translating_WordPress Translating WordPress]
**3 : [http://codex.wordpress.org/I18n_for_WordPress_Developers What WordPress Localization in Plugins is mainly about]

=Extra Customizations=
While any extra customization of any PluginBuddy Plugin is beyond the scope of the official support, we do from time to time offer different tips and tutorials on editing the awesome PluginBuddy plugins to better fit your individual needs. All such edits are, however, beyond what is officially supported and provided in the actual plugin admin panel and officially stated features on the individual plugin pages. No official support is provided nor guaranteed in, before, during, after or related to anything resulting from any such edits/customizations.

No support is provided on any of these extra customizations. Any of the steps mentioned in any of these extra custom edits may change at any time depending on newer versions of the plugins being released. Any use or customization of anything, beyond what is provided by default inside the plugin admin menu, means you are proceeding at your own risk and that you accept 100% responsibility and liability for everything you change or modify in any manner in the plugin. Your purchase and use of any PluginBuddy plugin implies and shows that you are buying and using PluginBuddy plugin(s) the way it(they) came in their original unmodified form, with no exceptions.

*Remember:
**[http://pluginbuddy.com/purchase/backupbuddy/ Make a backup of your entire site with BackupBuddy] before making any edits!
** PluginBuddy only supports the official unedited, unmodified versions of all PluginBuddy plugins.
** Use a good text editor to make any file changes. Again, maintain backups!
** Any changes you make to files WILL MOST PROBABLY be lost when the plugin is upgraded to any newer version.
** You are 100% responsible and liable for anything resulting from any of these changes.
** No support is provided nor guaranteed on any of these extra changes in any form or shape, whatsoever, regardless of who suggested these custom edits or suggestions.
** Any extra customization info or suggestion is added voluntarily by PluginBuddy staff to help users as much as possible, even if such customization is outside the scope of any membership support.
** Whether a PluginBuddy staff or representative offered or suggested the edit/customization, another customer or anyone else, PluginBuddy does not officially support nor provide any official support on any such edits.
** We cannot guarantee providing any support on any edits or customization tips we provide.
** Absolutely no support is guaranteed in any manner on any of our free plugins, whether or not there is any customization/edit involved.

=External Plugins Compatibility=

PluginBuddy does not promise, guarantee or provide support for any compatibility with any external plugin. If any PluginBuddy Plugin works without any problems when used with any external plugin in question, that means the PluginBuddy Plugin is most probably working without any issues overall. PluginBuddy is not responsible for making PluginBuddy plugins work in any manner, whether custom, fully, fixed or other, with any external non-PluginBuddy plugins. PluginBuddy is also not responsible for providing any support whatsoever for any external plugin, whether or not such an external plugin is used along with any PluginBuddy plugin.

=Free Plugins=

Free plugins are provided as is. There is no guaranteed support that comes with them. Guaranteed support is limited only and mainly for our premium unmodified plugins.

=Bugs, Features and ETA on new updates=

With every new release of any plugin, there may be a new bug or two. You may also want to have new features added to specific plugins. All existing versions of all plugins can have bugs reported OR new features suggested. All of this is done via the [http://ithemes.com/forum official forums].

New updates are also usually released regularly and at the same time, at very different paces, depending on the current number of bugs, features, new plans and tasks at hand. Therefore it is the official policy that there is NO pre-defined ETA on any bug fix, feature imeplemention OR new update OR new plugin roll-out UNLESS otherwise specified specifically in writing somewhere by an official iThemes employee.

==Bugs, bug reports and bug fixes==

Bug reports are filed and noted as they are encountered (thanks for reporting them to us!). There is never any ETA on any bug fixes unless otherwise noted.

==Feature Requests==

Feature requests and feature suggestions are basically future suggested features that users can suggest, and/or future features PluginBuddy may consider adding to the future versions of the plugin(s) in question (again, thanks for suggesting new features!).

There is no guaranteed ETA on when such feature requests will be implemented, unless otherwise noted. All suggested features are just that: suggestions. They remain suggestions until they're confirmed as officially in the works and to be included. Even then, unless a feature is actually rolled out publicly, there is no guarantee any feature suggestion will be implemented. We do our best to try and accommodate as many feature suggestions as possible.

Also, there is no guarantee that any feature request suggested will be implemented, unless otherwise noted.

==ETA on new updates==

Just like bug fixes and new features, there is never a guaranteed date nor a guaranteed time frame on when new updates will roll out. We work every single day of the week, all the time, on our plugins and thus every day there is something new and improved happening in almost all our plugins daily. Whenever we are ready to release any new updates publicly, you'll find out by seeing the plugin update notice in your WordPress OR in your [http://ithemes.com/member/member.php Member's area].

=What does BETA mean?=

Some of PluginBuddy plugins may be in Beta status OR may have Beta features. BETA simply means that some feature or specific part of the plugin is currently still in testing mode, and can cause issues if not used properly. All BETA plugins/features are not yet 100% stable, and thus should NOT be relied on to be working properly OR working at all. Throughout the iThemes Codex, any time the word "Beta" is used in any form, it refers to Beta plugins, Beta features, Beta status and/or anything related to the Beta nature that is officially announced or mentioned as such by any iThemes staff or on any of the Plugin pages, or in this Codex.

Beta implies that any new features or plugins are very close to being released as 100% working very soon, and that there may still be some issues to fix or test more before removing the Beta status. Since no single software of any kind can be tested under every system and site configuration in the world, the Beta status enables the Beta features to be tested out by as many people on as many different websites and configurations as possible.

*Some points to keep in mind when using any BETA plugin/feature:
**1 : Make [http://pluginbuddy.com/purchase/backupbuddy/ FULL WordPress backups] before using ANY beta feature.
**2 : Beta means that the current software feature is NOT complete, and that you are NOT forced to use such a feature at all. You are advised to WAIT until the BETA status is removed.
**3 : Using any Beta feature of any kind, whether it is an entire plugin or something inside a plugin, means and shows that you are fully accepting any liability for any risks involved.
**4 : Using any Beta feature of any kind, whether it is an entire plugin or something inside a plugin, means and shows that you are fully aware that there are all different kinds of risks involved with such features.
**5 : If you are concerned about your important data or anything bad that might happen as a result of using any Beta feature, do NOT use such Beta features.
**6 : ALWAYS make full [http://pluginbuddy.com/purchase/backupbuddy/ BackupBuddy Backups of all your important data] before using any Beta software, whether that Beta software is from PluginBuddy or from any other place.
**7 : If any issues are found in Beta, they are usually added to the list of bug fixes to be released as a whole, or for the next big update, instead of being updated OR fixed individually on a case by case basis.
**8 : Beta features are recommended to test and play with on test sites/servers and configurations with any dummy data, as long as you have [http://pluginbuddy.com/purchase/backupbuddy/ full backups of all important data] still.
**9 : iThemes is not liable nor cannot be held accountable for any unwanted results resulting from the use of BETA features.
**10 : The very name and nature of BETA shows clearly, without any doubt, that there will most probably be issues and problems involved when such labeled features are used anywhere.
**11 : Support for Beta features may be very limited. We usually simply collect all reports related to Beta features and collect them all for one big update in the future.
**12 : If you lose any important data or settings anywhere, or encounter damaged data or settings anywhere, because of any Beta feature, we will not be able to help you and will simply tell you to revert to your previous [http://pluginbuddy.com/purchase/backupbuddy/ backups]. We will also tell you to always wait for BETA status to be removed before using any such features.

If you do not fully understand what Beta means, OR are not willing to fully accept and be fully liable for any risks involved because of using such Beta software, you should NOT use the Beta software in any manner. In such a case, you should simply wait until the Beta status is removed.

*[http://pluginbuddy.com/what-does-beta-mean/ Blog post announcing what BETA means]

=PluginBuddy Licenses=

==Plugin Conflicts==

Some times, external plugins may cause issues in detaching, deleting, generating OR saving license keys. Such plugins may also cause issues when you want to manually or automatically upgrade plugins when you try to solve licensing issues.

Following is a list of currently known plugins which cause license detaching, deleting, generating OR saving issues. Please disable the following plugins, even temporarily, while you perform all the steps of manually OR automatically upgrading the PluginBuddy plugins in question, and detaching, deleting, generating and saving license keys for them. Keep such plugins disabled UNTIL all license key issues are gone OR at least while you perform these steps.

*Plugins causing PluginBuddy licensing issues
**'''W3 Total Cache :''' If you are using any caching plugin like W3 Total Cache, please disable it temporarily and then carry out any required steps You can re-enable the plugin in the end after everything works in terms of the licenses.
***Fix: Follow the above steps to fix this issue. [http://ithemes.com/forum/index.php?/topic/19436-backupbuddy-license-issue/#p92171 Steps also explained by BackupBuddy customer Laura (thanks!)]
**'''Any other CACHING or related plugin:''' Try disabling such plugins, performing the required steps, and then re-activating the Caching or related plugins in question.

*Related Links
**1 : [http://ithemes.com/forum/index.php?/topic/19079-wont-let-me-set-a-license-key/#p91663 W3 Total Cache plugin conflict and solution]
**2 : [http://ithemes.com/forum/index.php?/topic/19436-backupbuddy-license-issue/#p92171 W3 Total Cache plugin conflict and solution]

==September, 2011 Licensing Issues==

'''This issue is now resolved and the update already out.''' Upgrade manually to the latest versions of the plugins and such issues will go away.

Some users reported (in mid-September, 2011) that they were having issues with their license inside the Licenses area of different PluginBuddy plugins, including BackupBuddy.

Remember: All your PluginBuddy plugins, including BackupBuddy, will CONTINUE WORKING PERFECTLY even with these licensing issues. You can keep using the plugins exactly how you want them even during these licensing issues. Your plugins are NOT affected by this licensing situation in any manner.

Your membership is also completely fine and you have NOT lost any license(s). The issue is happening to some customers who simply need to upgrade manually to the latest version of their plugin, if the automatic upgrade does not work.

*Plugins with the update versions which remove this issue completely
**ALL PluginBuddy Products

*You can upgrade via one of the following:
**Automatically upgrade to the latest version
**Manually update by downloading the latest zip version of your PluginBuddy plugin from your Member's panel and then
***Overwrite your existing plugin directory via FTP with the new files.
***De-activate the existing plugin, delete it via your '''WordPress --> Plugins''' area and then upload the newly downloaded zip file. Then re-activate the plugin.
**That will remove the issue completely.
*DETACH the key and then RE-ATTACH the license key for the specific site in question IF licensing still shows issues AFTER manually upgrading (for example, manually upgrading to at least BackupBuddy 2.2.24 - other plugins have their own new version numbers - check your Member's area for the latest version download)
*Also make sure to DETACH the key, DELETE that same AND any other keys related to that specific site from the entire licenses area, and then GENERATE a new key for that site IF detaching and re-attaching the license key does not work AFTER manually upgrading (for example, manually upgrading to at least BackupBuddy 2.2.24 - other plugins have their own new version numbers - check your Member's area for the latest version download)

[http://ithemes.com/forum/index.php?/topic/6691-read-this-first-pluginbuddy-licensing-issues/page-2/#p85977 First reports]

Carousel

2011-11-01T19:08:34Z

Bes: Added /* Can I have email links INSTEAD of url links for Carousel? */

{{#ev:youtube|P41kZYE9Vg8|400|right}}
'''Series:''' [[DisplayBuddy]]
==Description==
Carousel lets you display a rotating set of images anywhere on your site with customizable content and effects. Multiple groups of images may be created for use anywhere on your site. Each group can be fully customized.

==Groups==
Carousel has the ability to save multiple groups that can each have different images and settings. The only information required to create a group is a group name.

==Adding Images==
In order to add images you will need to select a group then adjust the "Slide Image Dimensions" width and height so that the Carousel plugin will know what dimensions it will need to resize the images to. After saving the desired image dimensions then you can add an image by clicking the "+Add image" button. Carousel uses WordPress's built in media up-loader. This will allow you to either upload new images or select images that you have already added to the media library. In order to select an image to add from the list of images click the "show" link for that image and then click the "select this image" button as shown in the image below.

[[File:Displaybuddyselectimage.png|408px]]

==Settings==
Here is a list of all of the Carousel settings and a description of what each setting controls.

'''Group Title''' - This setting will allow you to change the title of the group at any time.

'''Carousel orientation and direction''' - This will change which direction the images slide.

'''Horizontal Alignment''' - This controls the horizontal alignment of Carousel on a page.

'''Entity width''' - This option is used to set the width of the entire Carousel container.

'''Images to show at once''' - This sets the amount of images to display at one time. If the entity isn't wide enough to show all of the images then it will hide any images that extend outside that width.

'''Scroll duration''' - This determines how long the scroll transition will last in milliseconds.

'''Pause duration''' - This is the amount of time that Carousel will pause in between each automatic transition.

'''Start delay''' - The amount of time after the page loads before a transition will happen.

'''Pause on hover''' - Option to pause transitions if a visitor hovers their mouse over Carousel.

'''Randomize image order each page load''' - Option to randomize the order that the images are displayed in each time the page loads.

'''Circular loop''' - When the carousel transitions to the end of the images it automatically transitions back to the beginning image.

'''Inifinite''' - Set whether carousel infinitely loops through the images continuously transitioning through them.

'''Display navigation''' - Option to display buttons that allow visitors to manually control the transitions.

'''Display pagination''' - Option to display pagination for each of the transitions below the Carousel.

==FAQ==
===How can I move the arrows from overlapping the Carousel?===

The CSS styling below can be added to your theme's style.css. Adjust the -60 and -70 pixel values as needed.

To apply the change to all Carousels:
<pre class="brush:html">
a.pb_carousel_default_prev {
left: -60px !important;
}
a.pb_carousel_default_next {
right: -70px !important;
}
</pre>

To apply the change to an individual Carousel (replace the 1 with the specific entity you want to style):
<pre class="brush:html">
#pb_carousel_prev-1 {
left: -60px !important;
}
#pb_carousel_next-1 {
right: -70px !important;
}
</pre>

===The Carousel container is too large until the page finishes loading. How do I fix this?===

The CSS styling below will cap the height of the Carousel so that overflowing content will not show before the page is done loading. Change the 75 to your desired height:
<pre class="brush:html">
#pb_carousel-1 {
height: 75px;
overflow: hidden;
}
</pre>

===Is it possible to open linked full sized images in a lightbox?===

Yes. Use [http://www.semiologic.com/software/auto-thickbox/ Auto Thickbox] plugin.

Source: http://ithemes.com/forum/index.php?/topic/14059-expand-image-on-carousel/#p67840

===Can I have email links INSTEAD of url links for Carousel?===

You may want your Carousel images (or certain groups/images) to be email links, so that people can send emails. That is easily done by putting the following (changing '''email@email.com''' to YOUR email) in the '''LINK''' field for the Carousel image in question:

<pre code="html">mailto:email@email.com</pre>

That's it! Now your Carousel image will be an email '''mailto''' link.

*Related forum thread
**http://ithemes.com/forum/index.php?/topic/19762-linking-images-in-carousel/

==Customize Carousel==

====Extra Customizations Policies====
[http://ithemes.com/codex/page/PluginBuddy#Extra_Customizations Check out the official policy and details on any Extra Customizations]

====Customize Carousel Dimensions and Placements via CSS====
Sometimes, Carousel shows everything properly BUT your image dimensions may result in more or fewer images being shown. This can be fixed by selecting the proper size or number of images.

You can also customize the entire Carousel Display via CSS. The following CSS code template can be used to customized to your own needs. You need to add this css to your theme's css file at the very end.

*Remember: the following will change the styling for ALL Carousels on your site EXCEPT the first <code>#pb_carousel-1</code> part, which (only that part) will work only on the 1st Carousel (Carousel whose shortcode is 1).

<pre brush"css">
#pb_carousel-1 { /* Controls the actual Carousel in question. In this example, it is Carousel 1. You can find the Carousel number in the shortcode in your Carousel admin panel */
left: 90px ! important;
width: 960px ! important;
}

.pb_carousel_default { /* Controls the width of the actual Carousel - this is usually always changed, if you want, with the actual Carousel */
width: 960px ! important;
}

.caroufredsel_wrapper #pb_carousel-1 { /* controls the entire Carousel wrapper */
width: 960px ! important;
}

#pb_carousel_prev-1 { /* controls the Carousel's previous left button */
left: 30px;
top: 65px;
}

#pb_carousel_next-1 { /* controls the Carousel's next right button */
right: 30px;
top: 65px;
}
#pb_carousel_pag-1 { /* controls the Carousel's bottom navigational buttons */
margin-top: 10px !important;
}
</pre>

*Related link
**http://ithemes.com/forum/index.php?/topic/18392-images-part-revealed/#p86475

====Replace navigation images with custom images====

You can replace the navigational images with any custom image by changing the Sprite image in the '''carousel\layouts\default''' folder.

*Related links:
**[http://www.w3schools.com/css/css_image_sprites.asp Definition and explanation of what a Sprite image is]
**http://ithemes.com/forum/index.php?/topic/18078-navigation-arrows/

====Align Images between Navigation Arrows====

You can align the images between the navigation arrows by adding the following CSS styling, customized to your needs, at the very end of your theme's css file:

<pre brush="css">
#post-102 .caroufredsel_wrapper
/* the #post-102 part makes it apply this setting ONLY to the Carousel on the post whose id is 102. Change it to meet your needs OR remove it completely.
Play with the "left" value of 11 also. This tells the Carousel to push the images 11 pixels to the right (from the left). */
{
left: 11px;
}
</pre>

*Related link
*http://ithemes.com/forum/index.php?/topic/18078-navigation-arrows/#p86042

==Additional Resources==
# [http://pluginbuddy.com/free-wordpress-plugins/ Free Plugins by PluginBuddy]

# [http://pluginbuddy.com/tutorials/ PluginBuddy Tutorials]
# [http://pluginbuddy.com/ PluginBuddy.com]
# [http://pluginbuddy.com/support/ Support Forums]

[[Category:PluginBuddy]]

BackupBuddy: Frequent Support Issues

2011-10-31T23:52:27Z

Bes: Added info about home url field not being editable when the url is hard-coded into wp-config.php /* Defined URL in wp-config.php */

=Backing Up=

==HTTP Loopback Connections Disabled==
* Also known as '''Endless Ping'''.
* This usually happens before the second Scheduled Cron in your backup is run. You can see the number of times "Scheduled Cron" is mentioned in the Advanced Logs shown on the backup page to see if this is the case.
* If your Server Information page reports that HTTP Loopback Connections are disabled or the following occurs (see below), you need to either enable HTTP Loopback Connections or enter the WordPress Alternate Cron setting in your wp-config.php file. This is caused if your host is blocking loopback connections within their firewall. You will need to request that your host change this (this is very standard to have this available), enable the alternate cron method in your wp-config.php (as Solution below - often the '''only''' solution for those in a shared environment), or move to a new host.
** If your backup progress (as detailed in the Advanced Details area) consistently '''never''' progresses beyond this point except for the continuous "pings":

<pre>
Backing up with BackupBuddy v2.1.8...
20:35:15: Setting greedy script limits.
20:35:15: Set memory limit to 256M. Previous value < 256M.
20:35:15: Finished greedy script limits.
20:35:15: Full backup mode.
20:35:15: Performing pre-backup procedures.
20:35:15: Backup serial: pyisomo736
20:35:15: Creating import data file.
20:35:15: Finished creating import data file.
20:35:15: Finished pre-backup procedures.
20:35:15: Scheduling Cron for pyisomo736.
1307910918|ping
</pre>
* Solution:
** Add define('ALTERNATE_WP_CRON', true); to your wp-config.php
*** Open your wp-config.php in a text editor. This file is located in the root of your site.
*** Add the line somewhere between the first ( <?php ) and last line of the file (but before the line that says /* That's all, stop editing! Happy blogging. */)
*** <pre>define('ALTERNATE_WP_CRON', true);</pre>
** Deactivate all other plugins and see if it works then, if so then make sure you don't have a plugin that may apply a maintenance mode
*** This is because maintenance mode plugins rarely, if ever, take into account WordPress scheduling crons
* See also
**[http://ithemes.com/codex/page/BackupBuddy:_Frequent_Support_Issues#Endless_Ping_on_second_Scheduling_Cron Endless Ping on Second Scheduling Cron in BackupBuddy Codex]
**[http://codex.wordpress.org/Editing_wp-config.php#Alternative_Cron WordPress Codex / Alternative Cron on WordPress.org]

* Related threads with same/similar solutions:
** http://ithemes.com/forum/index.php?/topic/17385-backupbuddy-doesnt-backup-at-all-infinite-ping/
** http://ithemes.com/forum/backupbuddy/endless-pinging-v2-2-14

==Compatibility Mode==
* If your server does not support command line Zip then BackupBuddy will fall back into a compatibility mode to help aid you in creating a backup. This mode is significantly slower and less reliable. It is not intended for persistent use and is provided to aid you in backing up in poor hosting environments, for instance to move to another host.
* Directory exclusion is not available in this mode. Even existing backups will be backed up, resulting in rapidly growing backup file sizes.
* If you are running on a Windows server you will need to install the [http://pluginbuddy.com/wp-content/uploads/2010/05/backupbuddy_windows_unzip.zip Windows zip.exe executable] (we do not provide support for setting this up, though the readme.txt in the file does help).
* Solutions:
** If your server is configured to disable access to the PHP exec() function and if you have access to configure your server then remove any blocking of the PHP exec() function in php.ini and configure permissions to allow running the Linux command line function `zip`.
** If your server is operating in safe_mode then either turn safe_mode off (if you can) or make sure that the safe_mode_exec_dir configuration parameter includes the directory which contains the `zip` command (please consult your host support for this information)
** Ask your host to enable access to the Linux command line Zip command via PHP's exec() function.
*** Example message to send to your host:
<pre>
Dear Sir/Madam,

I am attempting to use the highly popular WordPress backup software, BackupBuddy by PluginBuddy.com.
BackupBuddy requires the ability to use the Linux command line Zip command via PHP's exec() function.
BackupBuddy is reporting that it is unable to access this functionality on my server hosting environment.
Please enable this functionality for me so that I may use this backup solution in combination with your hosting.
These are commonly available features of many popular hosting providers such as HostGator.com so it is
not unreasonable to request it nor is it a security risk IF it is properly configured.

Please verify access to the following features:
1) PHP's exec() function.
2) Permission to run Linux's `zip` command.
3) The directory containing the `zip` command is included in the PATH environment variable
available to the process executing the command passed to the exec() function

Thank you for your time and consideration.
</pre>

** Move to a new host that does or will provide this capability
** Also possible that even though that zip via exec() is enable it still may not work if host does not have zip's path location currently as a part of PATH. The below code will add the directory of the zip executable to PATH after you ask your host where it is being kept:
*** <pre>putenv( "PATH=" . getenv( 'PATH' ) . ":directory zip exe is" );</pre>
*** The line has to be added anywhere in the wp-config.php file after the first line ( <?php ) but at least before the line that says /* That's all, stop editing! Happy Blogging */

==Warning: exec() has been disabled for security reasons in /www/wp-content/plugins/backupbuddy/lib/zip/zip.php on line ###==
* exec() is disabled somewhere in PHP configuration. Ask the host to correct this or use cPanel to edit PHP settings to enable it if possible. See 'Fallback to Compatibility Mode' above.

==Warning: mysql_query() [function.mysql-query]: Unable to save result set in /www/wp-content/plugins/backupbuddy/backupbuddy.php on line 1673==
* See [http://ithemes.com/codex/page/BackupBuddy:_Error_Codes#9001 BackupBuddy Error Code 9001]

==Godaddy Related==
* The bottom tier of Godaddy hosting services are known for not being able to complete backups within the maximum PHP runtime configured on their servers (usually 30 seconds), causing backups to fail.
* Solutions:
** Choose another quality hosting provider such as Hostgator.com (recommended)
** Upgrade to a higher tier of Godaddy hosting (not recommended as even better Godaddy servers are poor performers)

==.htaccess 404 / Addhandler Warning==
* Some hosts use a line at the top of the .htaccess file in the root of the site to configure some server settings such as enabling PHP support for that site. When used on a host that does not need this it can break PHP or other functionality. When migrating to a new site this can break the migration process. This often causes URLs to give 404 Not Found errors after migrating/restoring.
* Solution:
** Remove the Addhandler line from the .htaccess file before backup or open the backup ZIP archive and remove the line within the file within the ZIP.

==Backup marked as bad==
* Backups are verified by verifying the following criteria:
** The ZIP file is not corrupt and is openable.
** The database (.sql) file exists.
** The wp-config.php file.
** The backupbuddy_dat.php file.
* Potential causes:
** The backup timed out and did not complete within the PHP maximum runtime (usually 30 seconds)
*** Solution: Reduce the backup size by deleting files or excluding one or more directories. You may use the `Server Information` page's Directory Size browser to find large directories/files.
** Your hosting account does not have enough free space available.
** You may have the backupbuddy_temp directory excluded.

==Database backup succeeds, full fails==
* This is almost exclusively due any single step of the backup process not completing within the maximum PHP runtime (usually 30 seconds).
* If you are in compatibility mode then backups are significantly slower and less likely to complete in time.
* Solution:
** Ask your host to enable command line ZIP via exec() if you are in compatibility mode.
** Reduce the size of your backups by deleting files or excluding large directories.

==Directories not being excluded==
* Directories are not excluded if BackupBuddy is being forced to fall into compatibility mode. This is expected behaviour. This happens if command line Zip is unavailable via the PHP exec() function.
* Solutions:
** Contact your host and ask them if they can enable command line ZIP via exec() if using Linux. For Windows servers a zip.exe file is available by downloading it from the `Getting Started` page of BackupBuddy when running on a Windows host.
** Continue using compatibility mode. If you do this you will not be able to exclude directories, including the backups directory. Because of this even backups will be backed up. We recommend not storing any backups locally in this case as your backup file sizes will increase exponentially.

==Tempory files in directories/root==
* BackupBuddy creates several temporary files within the directory `/wp-content/uploads/backupbuddy_temp/` while generating a backup. Some of these may remain temporarily after backups complete though most are cleaned up immeditately. BackupBuddy will automatically clean up any remaining temporary files within 12 hours. This is an automated process.
* While in compatibility mode large sites can create temporary .gz files in the site root. Sometimes these may be left behind and require manual cleanup at this time. This is uncommon and is a result of not having command line ZIP via exec() available. Ask your host to enable this.
* Solution:
** Wait ~12 hours or delete the file(s) manually.

==Backups Time Out / Marked as Bad==
* Backup file size is too large so it takes too long to finish & server kills it. The maximum PHP runtime is typically 30 seconds so backups must finish within this time period. Try reducing backup size, excluding directories, disabling compression to speed up zip file generation, or getting host to enable native zip compression if not already enabled.

==Remote Transfers Fail==
* Login credentials are wrong. Test them to be sure that they have not changed. This is exceedingly common.
* The path entered is incorrect or the directory has not been created. BackupBuddy requires the path/bucket to already exist in some cases.
* Some hosts block outgoing connections. Try another remote destination if possible. Most remote destinations transfer over the HTTP port 80.
** Amazon S3: port 80
** Dropbox: port 80
** Rackspace Cloud: port 80
** FTP: port 21 (unless overridden)
** Email: port 25 (if using external mail server)

==Scheduled Events Fail to Trigger==
* The scheduled date is wrong and has not passed.
* Not enough visitors are visiting to trigger the schedule. Someone must visit any page on the WordPress site on or after the scheduled time for the event to occur. If no one visits during the time-frame then the event may be missed or occur at an unscheduled time.
** Can force a cron job to run in Cpanel by adding this line of code to a cron job if really need to: <pre> wget -q -O - http://DOMAIN/wp-cron.php 2&>1 /dev/null </pre>
*** Source: http://www.siteground.com/tutorials/cpanel/cron_jobs.htm
* The backup is failing. Test manual backups.

==Files not being sent remotely==
* Files may fail remote sending for two possible reasons:
** Files are too large to be transferred during the alotted PHP maximum runtime (usually 30 seconds). This is defined by your host.
** Your host's firewall is blocking outgoing HTTP connections / transfers.
** The backup itself isn't completing - verify that they work manually.
* Solutions:
** Reduce backup file size by deleting files or excluding directories.
** Contact your host to increase PHP's maximum allowed runtime.
** Contact your host to unblock their firewall to allow outgoing HTTP connections.

==Error 3382==
Check out [http://ithemes.com/codex/page/BackupBuddy:_Error_Codes#3382 Error 3382 Details]

==Backup failure running function `` in email==
* Usually due to sending remote backups/databases failed due to permissions/path if ftp.
** If sending the files by email, then files are probably too large for email(typically up to 10mb by email allowed by most places)

==Endless Ping on second Scheduling Cron==
* Database may be too large, lot of times this would be the wp_posts table.
** See if can lower size of database. The database size may be too big for your site/host/server to handle properly.
** Use Server Info inside BackupBuddy ( '''BackupBuddy --> Server Info.''' ) to check where the most disk space is being used.
** Increase available runtime. Your server may be timing out too quickly or having other issues related to not being allowed enough time to run scripts or specific commands.
** What revision retention policy do you operate on the posts? It may be that you have a lot of revisions stored in the database that you could safely remove. The WordPress Codex gives some information on controlling revisions (http://codex.wordpress.org/Editing_wp-config.php#Post_Revisions) but I don't think this acts retrospectively so you might need to find a method to prune any revisions you currently have.
** Many plugins tend to leave a lot of data behind even after they have been de-activated and deleted in WordPress. This can result in very large BackupBuddy backups.
***Example: A famous example of this is Statpress, which has been publicly known to leave massive amounts of data behind in the WordPress database tables even after the plugin was deactivated and deleted.
***Solutions:
**** Use Server Info inside BackupBuddy ( '''BackupBuddy --> Server Info.''' ) to check where the most disk space is being used in different WordPress database tables.
**** Another way to see if such plugins may be affecting and causing your Backup to fail is to look through the database and see where the most db space is being used. If any table with a lot of data exists and is related to a plugin you no longer use, you can drop or empty that table with something like phpMyAdmin.
***Make full Database backup with BackupBuddy before making any Database changes. :D
*Related links:
**[http://ithemes.com/forum/index.php?/topic/18066-backup-not-working-keepings-pinging/#p85085 Database size causing endless pings on second scheduling cron]

==Fatal Error: Call to undefined function home_url()==
* Full error will be Fatal Error: Call to undefined function home_url() in /wp-content/plugins/backupbuddy/classes/backup.php on line x
** BackupBuddy requires at least WordPress version 3.0, make sure you don't have an older version of WordPress.

==Parse Error, unexpected T_VARIABLE in .../backupbuddy.php on line xxx==
* Usually will come up during activation of BackupBuddy
** Make sure you are using PHP5 and not PHP4.
** If you are installing by downloading BackupBuddy, unzipping, and then using FTP the directory in the site plugins directory sometimes the configuration of the FTP transfer mode can cause issues. You can try deleting the existing plugin files with the plugin admin and then install through WordPress admin by going through Plugins -> Add New -> Upload -> and use the backupbuddy.zip file. Be sure to do this with a copy of backupbuddy.zip that has not been unzipped.

==Backed up files link shows 404 error==

* This error is shown when you click on the generated backed up files. There is no error shown on the Backup page or in the logs, yet clicking the backup links show a 404 error or result in you not being able to download them because the files don't exist. This could be caused by several things. Mainly, this has been known to be caused by the following:
** There is an Archive limit set on the BackupBuddy --> Settings page. If this is being exceeded, the extra archives will be deleted. Try setting this to something higher.
** Set the total size limit ( max file size ) to a higher setting.
** See if any other plugin may be causing the issue. Disable other plugins and try starting the backup process again.
** Make sure you have the necessary permissions to the downloads folder where the file is being saved.
** Make sure the Advanced Log file in BackupBuddy is not showing any errors. If it is, post on the [http://ithemes.com/forum/backupbuddy/ forums] so that the error can be looked at.

* Other threads with solutions listed above:
** http://ithemes.com/forum/index.php?/topic/17196-full-backup-completes-but-does-not-go-to-backup-archives/
** http://ithemes.com/forum/index.php?/topic/17624-backupbuddy-full-backup-is-deleting-backup-file-after-creating-it/
** http://ithemes.com/forum/index.php?/topic/15013-download-error-message/

==Change backups folder/file permissions or verify it is writable==
BackupBuddy needs the backups folder in your '''wp-content/uploads''' directory on your site to be writable so that BackupBuddy can easily create and modify backup and related files in that directory. If those permissions are not setup properly, either automatically or manually, you'll run into the "'''Unable to create backup storage directory'''" or similar errors.
*To verify and change any file or folder permissions:
**Easily and quickly learn what permissions are and how to change them in the official [http://codex.wordpress.org/Changing_File_Permissions WordPress File Permissions page]
**Ask your host to verify or do it for you.
**Make sure your backups folder directory in '''wp-content/uploads''' is set to 755 (permission).
**Make sure your '''wp-content/uploads''' folder and everything under/in it is set to 755 also (called recursive permissions OR changing permissions recursively).
*Support thread with detailed info
** http://ithemes.com/forum/index.php?/topic/5270-backupbuddy-setting-permissions-and-security-implications/#p24242

==Big backup files with both "Force Compatibility Mode" and PHP exec() function enabled==
*If PHP exec() function is enabled on your server AND you have "Force Compatibility Mode" setting enabled, you may run into backup file size issues. The compatibility mode does NOT support folder exclusions, and thus your backups may be very big.
*Solution:
**If your server has '''PHP exec() enabled''', go into '''BackupBuddy --> Settings''' and '''disable "Force Compatibility Mode"''' option.
*Related links with solution:
**http://ithemes.com/forum/index.php?/topic/18007-utterly-botched-wordpress-migration/

==Dropbox Backups Not Arriving==
Sometimes, backups sent to Dropbox never arrive (meaning they never show up) in Dropbox.
*'''Possible reasons:'''
**Due to the Dropbox API limits, each backup file has to be loaded into your server's memory and then sent to Dropbox. Dropbox requires PHP oAuth. Because of that, your server may run out of the required memory to do other things at the same time. When your server does not have enough memory to do multiple things at once, it may take longer than usual to complete each task, and the Dropbox process may take longer than the allowed time in PHP maximum_execution_time. This will simply result in the Dropbox process to time out and cancel. Since the limitation is because Dropbox requires PHP oAuth, there is no current workaround other than more memory.
**Your server or site has file transfer or PHP script processing limits which is resulting in the transfer not finishing.
**Your Dropbox connection settings are wrong.
**Your server may not have enough memory to perform this transfer.
**Your backup is around or larger than 300mb. Dropbox has a 300mb file size limitation when uploading files online via a file.
*'''Solutions to try:'''
**Make sure your Dropbox connection settings are right.
**Delete your current Dropbox connection and then re-create the Dropbox connection. See if that works.
**Most important and basic thing to try: wait 10 to 15 minutes for the backup to arrive before giving up. Dropbox uploads can be slow due to Dropbox itself. Dropbox has been known to show files even 30 minutes after a backup file was sent.
**Ask your host to increase the PHP maximum_execution_time. This is usually 30 seconds. Try increasing it to something much higher temporarily to see if that makes any difference.
**Ask your host if your server can get more allotted memory.
**Ask your host to enable PHP error logging to a file that you can access.
***What this does is create an entry, in a txt file on your server that your host can tell you the location of, every time there is a PHP related error or warning. When DropBox times out, this file can most probably give you an exact error message that you can tell your host to address or fix.
**Try sending a smaller backup file OR simply a database backup file to Dropbox. You can also use the Exclude option to exclude folders and files you do not need or to test things. See if such smaller files arrive. If they do, your issue is definitely with the larger file sizes.
**Try excluding certain folders from the backups via '''BackupBuddy --> Settings''' and then see if the smaller-than-before backup files get to Dropbox.
*'''Related links:'''
**http://ithemes.com/forum/index.php?/topic/18099-dropbox-not-working/#p85173
**http://ithemes.com/forum/index.php?/topic/17812-no-downloads-to-dropbox/#p83619

==Database SQL (MySql) file inside full backups==
In full backups, the actual database is backed up also. To find this file, look for the following folder in your backup file after you have extracted/unzipped the backup zip file:

wp-content/uploads/backupbuddy_temp/'''NAMEOFBACKUP'''

The '''NAMEOFBACKUP''' part in the above link will be the exact same as the last set of characters, after the date, in your backup file name.

For example, if your backup file name is:

'''backup-domain_com-2012_05_29-''ukitenaifg'''''

then the folder inside a full backup where your database file is saved is

wp-content/uploads/backupbuddy_temp/'''ukitenaifg'''

==BackupBuddy Tab Missing in WordPress==
*If the BackupBuddy Tab is missing in your WordPress Admin area, there could be a few reasons for it:
**'''MULTISITES:''' If you are activating BackupBuddy on a single site inside a Multisite instead of using the NETWORK ACTIVATE option, BackupBuddy options will be hidden on purpose for security reasons. You must use [http://ithemes.com/codex/page/Installing_BackupBuddy#Multisite Network NETWORK ACTIVATE] instead.
**Try disabling other plugins which may be causing a conflict OR not allowing BackupBuddy tab to show up in WordPress admin area, even if direct links to such areas work.

*Related links
**[http://ithemes.com/codex/page/Installing_BackupBuddy#Multisite Network Active BackupBuddy on Multisites]
**[http://ithemes.com/forum/index.php?/topic/18395-backupbuddy-installed-and-working-but-missing-from-wordpress-left-panel/ Plugin conflicts causing BackupBuddy to disappear in WordPress Admin panel]

=Restoring/Migrating=

==Step 3 in import results in importbuddy.php file being downloaded when "Next Step" is clicked==
This problem happens because the .htaccess file being imported conflicts with the way your new host/server/site, where you are importing to, runs and processes php files.

* To fix it, try any of the following (keep going through the steps till you solve the problem - the Second step below should solve the problem completely)
** First, make sure you have the latest version of BackupBuddy's importbuddy.php (found in the latest BackupBuddy version OR latest download link available on the BackupBuddy main Backup page.)
** Second, read this exact issue explained in detail on PluginBuddy http://pluginbuddy.com/site-migration-heaven-one/ That has detailed steps on how to solve this.
** Third, AFTER you encounter the problem, since the importbuddy.php file already has extracted the files:
*** Rename the .htaccess file in the newly extracted folder/area to anything like .htaccess_backup
*** Restart the import process again.
*** This time, in the Advanced Tab, select the option to "Skip File Unzip", since the files have already been extracted.
*** After the site has been restored, go into your Settings --> Permalinks area to simply save that page, without making any changes. That will recreate the necessary .htaccess file again for the newly imported file.
** Make sure all file, folder and any other permissions are set properly before and after the backup and restore.
* This is probably the SAME as the other issue of [http://ithemes.com/codex/page/BackupBuddy:_Frequent_Support_Issues#Importbuddy.php_shows_ACTUAL_file_contents_instead_of_the_next_step Importbuddy showing actual file contents instead of the next step]

You should now be able to pass Step 3 without any issues.

* Similar pages/threads with solutions:
** http://pluginbuddy.com/site-migration-heaven-one/
** http://ithemes.com/forum/index.php?/topic/17933-backupbuddy-after-step-3-downloads-importbuddyphp/
** http://ithemes.com/forum/index.php?/topic/13350-step-3-click-next-step-downloads-a-file-does-not-go-to-step-4/
** http://ithemes.com/forum/index.php?/topic/15420-impurtbuddy-step-3-problem/
** http://ithemes.com/forum/index.php?/topic/16443-cant-get-past-step-3-asks-to-download-importbuddyphp-over-and-over/
** http://ithemes.com/forum/index.php?/topic/13375-rackspace-server-cant-migrate-to-it-using-importbuddy/
** http://ithemes.com/forum/index.php?/topic/13660-help-with-migration/
** http://ithemes.com/forum/index.php?/topic/14350-cannot-move-past-step-3-in-migration/
** [http://ithemes.com/codex/page/BackupBuddy:_Frequent_Support_Issues#Importbuddy.php_shows_ACTUAL_file_contents_instead_of_the_next_step Importbuddy showing actual file contents instead of the next step]

=='''Parse error''': syntax error, unexpected T_STRING, expecting T_OLD_FUNCTION or T_FUNCTION or T_VAR or '}' in /.../importbuddy.php on line 7974 (or any line)==
This error usually means that your site/server, where you are importing to, is running PHP4. BackupBuddy and importbuddy.php require at least PHP5 to function properly.
*It's usually easily fixable:
** Make sure you are using PHP5 and not PHP4.
** Change your PHP settings yourself to run PHP5.
** Ask your host to make sure you're running PHP5.
*Related customer thread with solution
**http://ithemes.com/forum/index.php?/topic/18009-parse-error/

==Extraction of zip files (unzipping) does not work==

Sometimes your host or site setup may prevent importbuddy.php from extracting (unzipping) the backup file.

Here are 2 manual solutions, one via FTP and one via cPanel, on unzipping the files manually and then continuing the importbuddy.php process. Try either of the following:

* http://pluginbuddy.com/restoring-an-unzipped-backup-with-backupbuddy/
* http://pluginbuddy.com/tutorials/unzip-backup-zip-file-in-cpanel/

IMPORTANT: Make sure you choose "Skip zip file extraction", under the "Advanced Configuration Options" tab on Step 1, to tell importbuddy.php to SKIP the extraction process. The import should work fine then while skipping the extraction process.

==Old importbuddy overwriting on unzip==
* Possible Symptoms:
** importbuddy behaves differently or stops functioning properly after the extraction step.
** Weird errors are seen after the extraction step.
** The importbuddy version at the bottom of importbuddy changes after the extraction step.
** Error: "Error! The unzip process reported success but the backup data file, backupbuddy_dat.php was not found in the extracted files. The unzip process either failed (most likely) or the zip file is not a proper BackupBuddy backup."
** Error 9003.
* Possible Solutions:
** Open the backup ZIP and delete the importbuddy.php file within it.
** Replace the importbuddy.php on your server after the extraction step but before moving forward further.

==After import: The source site is now redirecting to the destination site (or vice versa):==
* This occurs if the new database settings were not entered during Step 4 of importbuddy.php. Because of this, both sites are now sharing the same database so one of them (usually source) is redirecting to the other (usually destination). importbuddy.php needs to be re-run inputting the source URL on Step 4 and using the source database settings. This will reconfigure the source database to use its proper URL. Next importbuddy.php needs to be run again inputting the destination URL on Step 4 with the NEW database settings for the new database. This way both sites will have their own database for their respective URLs.
* importbuddy no longer overwrites existing WordPress databases by default so this issue is not as common as it used to be.

==After import: WordPress Error: `You do not have sufficient permissions to access this page`==
One or more of your database table prefixes did not get changed during migration. A fix is available here: http://www.tech-evangelist.com/2010/02/06/wordpress-error-sufficient-permissions/

==Cannot Log-in and Keep Getting Redirected Back to Log-In Page==
The migration completed successfully and the site is browse-able but when you try to log in you keep getting redirected back to the log-in page and the URL looks something like this:
<pre>http://wptest.local/wp-login.php?redirect_to=http%3A%2F%2Fwptest.local%2Fwp-admin%2F&reauth=1</pre>

This is a common WordPress related issue and not a result of BackupBuddy backup or restore/import. It is easily fixable, though, and happens mainly because of some plugin or custom edit somewhere in WordPress causing WordPress to keep redirecting to a specific url for admin login.

* Solutions (try any of these to see if they work - make a backup of everything Or keep you BackupBuddy backup in case something goes wrong or you want to undo some changes you make below):
** Edit W3 Total Cache settings to fix this, if you are using or have used W3 Total Cache. Please check in your wp-config.php for a line such as this:<pre>define('COOKIE_DOMAIN', 'www.domain.com'); // Added by W3 Total Cache</pre> In order to be able to log-in please either delete the line; or comment out the line; or change the string 'www.domain.com' to false - note that false is not enclosed by quotes, e.g.,: <pre>define('COOKIE_DOMAIN', false); // Added by W3 Total Cache</pre> You will now be able to log-in and can then attend to updating this definition as required by your new site configuration. To read more about COOKIE_DOMAIN please visit: [http://codex.wordpress.org/Editing_wp-config.php#Set_Cookie_Domain WordPress Codex - Cooke Domain]
** Make sure your wp-config.php files does NOT have any hard-coded SITE or WordPress URI that may be causing this issue.
** Make sure there is no duplicate .htaccess file.
** Make sure the existing .htaccess file does not contain anything related to the Site or WordPress URL that is causing the redirect.
** Make sure the wp_options table does not have any OLD url's which were NOT updated prior to the move.
** Make sure you use the latest versions of BackupBuddy and importbuddy.php (even try importbuddy.php beta to see if that makes a difference)
** Disable conflicting/all plugins by renaming the folder names of the individual plugins to something different.

* Some good posts with good/alternate solutions/info on this:
** http://ithemes.com/forum/index.php?/topic/14324-getting-redirected-when-trying-to-login/
** http://ithemes.com/forum/index.php?/topic/14102-new-site-wp-admin-redirect-back-to-original-sites-wp-admin/
** http://ithemes.com/forum/index.php?/topic/13581-access-admin-backend/
** http://ithemes.com/forum/index.php?/topic/17383-wp-content-files-on-subdomain-redirect-to-root/
** http://codex.wordpress.org/Login_Trouble
** http://wordpress.org/support/topic/keeps-redirecting-when-logging-in
** http://codex.wordpress.org/Editing_wp-config.php#Set_Cookie_Domain
** [http://wordpress.org/support/topic/domain-redirection-keeps-forwarding-to-signup-page Multisite Redirects]

==Blank OR strange homepage/frontpage BUT admin area works perfectly==
This usually happens when there is an existing and unwanted index.html, default.html or some other server default file already in the root of WordPress directory of your new restore/migrated site.
*Solution:
**Make sure you delete any extra index.html, default.html or any other server default file that is already in the root of the WordPress directory of your newly restored/migrated site.
**Make sure your WordPress's index.php file is correct. If not, you can always download the latest version from WordPress.org and use the index.php file from that download (with any changes you may have made to the existing index.php file) to replace the index.php already present in your site.
**Make sure your theme's index.php and other theme files contents and permissions are correct.
**Make sure your theme settings in the WordPress admin section are correct.
**Make sure your .htaccess file is not causing the issue.
*Related customer thread with easy solution:
**http://ithemes.com/forum/index.php?/topic/17989-update-in-progress-after-migrate/

==Where can I get the latest BETA of importbuddy.php?==
Starting with version 2.2.14, BackupBuddy now also includes a way to download the latest BETA version of importbuddy.php which will have the latest bleeding edge features. The link is in your BackupBuddy admin area.
* To download the latest BETA version of importbuddy.php
** Click the BackupBuddy tab OR the downward arrow in front of it to expand it.
** Click the Backup & Restore link under that tab.
** Look at the 3 images on that page, specifically the right most image called "Restore/Migrate."
** Right under it will be a link text "'''''Try the latest <ins>beta version here</ins>'''''" - that is your download link.
** Click that link to download the latest BETA version of importbuddy.php to your computer.
** Upload and use that file anywhere you want to restore/migrate your BackupBuddy backups.
* Here is the image of your '''BackupBuddy --> Backup & Restore''' area, where the latest BETA importbuddy.php download link is:
**[[File:Backupbuddy-importbuddy-beta.jpg|Image of where the latest BETA importbuddy.php download link is]]

==Links (permalinks) return 404 errors==
* The [[.htaccess]] file was not configured properly or was not writable so importbuddy didn't update it.
* To fix log in to the admin dashboard and navigate to: Settings -> Permalinks and click 'Save Changes'.
* To manually fix, edit the [[.htaccess]] file in a text editor following the format on the [[.htaccess]] page.
* If getting this after a migration in which it redirected you to home page during the migration's step 5
** Cause: .htaccess file is causing redirections
** Solution:
*** 1) Redo import and stop after Step 2 (file extraction)
*** 2) After step 2 delete the .htaccess file in the root of the site
*** 3) Continue the import to completion
*** 4) Regenerate the .htaccess file in WordPress by going to Settings -> Permalinks -> and click to "Save Changes"

====500 Server Errors:====
* [[.htaccess]] (click for details) file is causing URLs to be redirected improperly or is malformed. Sometimes the front end simply won't load.
** Regnerating the .htaccess file can solve. To do this login to your admin dashboard and go to Settings -> Permalinks -> and click the "Save Changes" button.
*** Note: You don't have to actually make any changes on the page to regenerate the .htaccess in this manner by clicking to "Save Changes".
* PHP is not functioning or enabled for the site. Check with basic [[phpinfo()]].
* A 404 error is occurring but the server is not set up correctly to return a 404. Do sanity check with .htm file.
* Manually edit the [[.htaccess]] file in a text editor following the format on the [[.htaccess]] page.
* Delete or manually remove your OLD .htaccess file from the extracted folders after it passes the step of extracting files, from the backup file (and then zip it again) OR before you do a backup.
* Edit your OLD .htaccess file to be basic without any extra comments that may be interfering on the new server.
* Make sure your new OR old .htaccess does NOT have any directive that is resulting in any website file, including the index, to be blocked.
* See `.htaccess being overwritten on unzip` below if it happens on Step 2 of import.
* Ask your host to look at the .htaccess file and to fix any errors with it, OR to delete the EXISTING AND/OR GENERATED .htaccess file OR to generate a new .htaccess file for you.

*Related links:
** http://ithemes.com/forum/index.php?/topic/18089-migration-failure-with-500-internal-server-error/
** [http://ithemes.com/forum/index.php?/topic/18445-restored-site-now-wont-load-and-cant-log-in/#p86642 Remove extra .htaccess lines which may be preventing the site from loading]
** [http://ithemes.com/forum/index.php?/topic/18607-internal-server-error-hostgator-rocks/ How HostGator helped a customer fix this error by simply fixing the bad .htaccess file]

==.htaccess being overwritten on unzip==
* Symptoms:
** PHP stops properly functions in importbuddy.php after the extraction step.
** Weird errors are seen after the extraction step.
* Solution:
** Open the backup ZIP and delete the .htaccess file within it, can be done before migrating.
*** Can also delete the .htaccess file in directory after step 2

==The backup zip file is not found==
* The zip file has been renamed to a non-BackupBuddy format.
* The zip file permissions are wrong. Ex: Not readable.
* The zip file is not in the same directory as importbuddy.php.
* The zip file has not finished uploading or was interrupted in transit. If BackupBuddy was used to send it try manually uploading.

==backupbuddy_dat.php OR db_1.sql was not found after extraction==
* You may be using an older version of importbuddy.php not compatible with your backup version. Try upgrading your importbuddy.php to the version in the latest BackupBuddy.
* You may have renamed your backup ZIP file. BackupBuddy depends on the naming format to determine where some data in the backup ZIP is stored. Rename your backup back to its original name.
* Your backup may be corrupt. Try manually unzipping to verify it extracts properly.

==SQL error near WH==
* It is because the table does not have a mysql primary key or unique index

==Restoring database times out==
* You can try reducing the size of that database.
** Checking for extra large tables you don't need (such as deleted plugins leaving data behind).
** What revision retention policy do you operate on the posts? It may be that you have a lot of revisions stored in the database that you could safely remove. The WordPress Codex gives some information on controlling revisions (http://codex.wordpress.org/Editing_wp-config.php#Post_Revisions) but I don't think this acts retrospectively so you might need to find a method to prune any revisions you currently have.
* Seeing if host will increase memory limit and runtime can help as well.

==Extracting ZIP times out / hangs==
* Unzipping was not able to complete due to the unzipping process taking longer than the maximum PHP allowed runtime (usually 30 seconds).
* Solutions:
** Manual Unzip Process:
*** Manually extract the ZIP file on your computer then upload the files to the server.
*** Restart the importbuddy.php Import process, selecting `Skip Zip Extraction` from the advanced options slide-down.
** Or ask your host to increase the maximum PHP runtime beyond its current limit.

==Defined URL in wp-config.php==
* Symptoms:
** URL does not appear to update after migration.
** Links 404 after migration and you verified that you entered the correct URL to migrate to.
** Links can also redirect to old site at the defined URL, though usually they 404
** Cannot update url's in the admin area. Such fields are usually disabled, as WordPress disallows their editing if the home URL is in the wp-config.php file

==URLs redirecting to old site==
* Verify that you properly entered the old and new URLs of your site during the importbuddy.php Import Process.
* Solution:
** Re-run importbuddy.php entering the correct URLs.
** Also make sure import is finishing correctly, may be timing out without realizing it.

==URL needs manually updated==
* Note that this does not update serialized data. In short, some plugins, such as PluginBuddy plugins may not have internal URLs updated. This is more of a last-choice solution.
* SQL to update URL in posts manually:
<pre class="brush:html">update wp_posts set post_content = replace(post_content, 'http://OLD_URL', 'http://NEW_URL');</pre>
* Command line zip test to check if exec is enabled and zip can create a file. Download: [[Media:Zip_test.zip]]

==The unzip process reported success but the backup data file...==
"Error! The unzip process reported success but the backup data file,
backupbuddy_dat.php was not found in the extracted files. The unzip
process either failed (most likely) or the zip file is not a proper
BackupBuddy backup."
* Most common cause: See [http://ithemes.com/codex/page/BackupBuddy:_Frequent_Support_Issues#Old_importbuddy_overwriting_on_unzip]
* The backup did not finish extracting (timed out).
* Verify the backup is not damaged.

==Importbuddy.php shows ACTUAL file contents instead of the next step==
There is one report that on Step 4, importbuddy.php started showing the actual importbuddy.php file contents. The reason for this was that the EXTRACTED .htaccess file from the OLD server/site was causing the issue.

This is VERY similar OR the same as [http://ithemes.com/codex/page/BackupBuddy:_Frequent_Support_Issues#Step_3_in_import_results_in_importbuddy.php_file_being_downloaded_when_.22Next_Step.22_is_clicked Step 3 downloading importbuddy.php file issue] which also contains possible reasons and solutions.

*Solutions
**Check your .htaccess file on the OLD server/site and fix any issues with it. THEN do the backup.
**After Step 3 has finished, and BEFORE proceeding to Step 4 (or any such step where this problem happens), open a new window OR your FTP program, go and find the EXTRACTED .htaccess file, EDIT it to remove any UNWANTED directives, and then switch back to the importbuddy.php window to continue onto the next step.
**On the OLD site, ALSO try saving your Permalinks again in WordPress --> Permalinks . Simply click "Save" on that page and then do a backup and retry the import/restore/migration.
**Thanks to our customer Chris Malone for finding the issue and finding a solution right away too.
**As mentioned above, this is VERY similar OR the same as [http://ithemes.com/codex/page/BackupBuddy:_Frequent_Support_Issues#Step_3_in_import_results_in_importbuddy.php_file_being_downloaded_when_.22Next_Step.22_is_clicked Step 3 downloading importbuddy.php file issue] which also contains possible reasons and solutions.

*Related link
**[http://ithemes.com/forum/index.php?/topic/18621-wont-continue-past-step-3-when-running-importbuddy/ User reporting the issue and the solution]
**[http://ithemes.com/codex/page/BackupBuddy:_Frequent_Support_Issues#Step_3_in_import_results_in_importbuddy.php_file_being_downloaded_when_.22Next_Step.22_is_clicked Step 3 downloading importbuddy.php file issue]

=BackupBuddy Classic=
BackupBuddy Classic is available to download in case you have an older system OR older system specs like older PHP, MySql and other things. BackupBuddy Classic does not have any of the new features of BackupBuddy.

If your system or host forces you to use BackupBuddy Classic, you should start considering switching to another host or server ( we recommend [http://ithemes.com/hostgator HostGator] ) which is not old or not updated regularly.

BackupBuddy Classic can be found in your Member's area and is labeled "'''BackupBuddy Classic'''."

*Related Link
** http://ithemes.com/forum/index.php?/topic/18448-download-legacy-versions-of-backupbuddy/#p86657

=Additional Resources=
# [http://pluginbuddy.com/purchase/backupbuddy/ Purchase BackupBuddy]
# [http://pluginbuddy.com/tutorials/ PluginBuddy Tutorials]
# [http://pluginbuddy.com/ PluginBuddy.com]
# [http://pluginbuddy.com/support/ Support Forums]

[[Category:PluginBuddy]]

General Plugins FAQ

2011-10-31T20:24:51Z

Bes: Clarified the older versions info a bit more, and added Related Threads. /* Downloading OLDER Versions */

=Plugin Display Issue=
==My Plugin Won't Show Up! I'm using more than one jQuery on my site==

When more than one jQuery is used on the same site or the same page/post, sometimes older jQuery versions or incompatibilities can cause any plugin, including PluginBuddy plugins, from appearing on your live site.

*There are several ways to check if this may be the cause of the problem. Here is the most effective method:
**Check the source code of the page where the problem is happening. jQuery usually (or always) shows its version number in any place where it is called. Make sure that number is consistent or at least among the latest versions in all such urls/calls.

*There are several ways to get this fixed:
**Try to use only a single jQuery throughout the whole site.
**Update all jQuery related plugins, OR any plugins using jQuery, to the latest versions.
**Ensure that your theme is not calling an older, incompatible or modified version of jQuery that may be interfering with your PluginBuddy plugins. If your theme is calling a jQuery, ensure that it is the latest version. Contact your theme developer to see if you can get the latest jQuery added to your theme while keeping any customization you made to the theme intact.

*Some related thread(s) about this that can shed some more light:
** http://ithemes.com/forum/index.php?/topic/17855-rotating-text-not-displaying-on-home-page/#p83957

==Remove Bullets in OLDER IE Browsers==
*In many older IE versions, including when viewing in the new IE Compatibility Mode, you may notice bullets, images, arrows or similar things before each UL or LI (list). This can happen in many plugins, including the ContactBuddy plugin.
*'''[http://msdn.microsoft.com/en-us/library/cc351024(v=vs.85).aspx THIS IS A KNOWN OLD-IE-VERSIONS ISSUE ACKNOWLEDGED BY MICROSOFT.]'''
*The "fix" for this is as follows:
**Add the following code to your theme's css file at the very end:
<pre brush="css">ul li
{
list-style-image:none !important;
list-style: none !important;
list-style-type: none !important;
}</pre>
*That will remove any form of extra styling to lists which is added automatically by older IE or other browsers. The above code addresses list-style-image, list-style and list-style-type CSS properties to make sure older/compatibility versions of IE do not apply any automatic styling to any lists.
*Related links:
**http://ithemes.com/forum/index.php?/topic/18347-another-css-issue/
**http://msdn.microsoft.com/en-us/library/cc351024(v=vs.85).aspx
**[http://www.ie6countdown.com/join-us.aspx Microsoft retiring IE6 - you can tell your clients to upgrade via this code - change the '''if lt IE 7''' on that page to say something like '''if lt IE 9''' since even IE7 is old and not up to standards]

==Unable to use special characters in Widget titles OR Widget Title shows forward slash \ ==

Sometimes, you may have trouble inserting characters in Widget titles, OR the Widget titles may show a forward slash \ before such special characters.

For example, the widget title '''Cartoon's''' turns into '''Cartoon\'s'''

This can happen in many plugins, including some PluginBuddy plugins. The reasons can vary from the plugin version being outdated on a specific install to being a bug in the plugin (if you find any, let us know! :) ).

There is a workaround. When using any special character that is causing such issues, use the HTML code for it instead.

For example, '''Cartoon's''' can be written as

<pre>Cartoon& # 3 9 ;s</pre> (remove the spaces)

the <code>& # 3 9 ;</code> (remove the spaces) code shows the apostrophe' character. The above will then show the '''Cartoon's''' word properly.

*Resources
**[http://www.w3schools.com/tags/ref_entities.asp HTML character reference]
**[http://ithemes.com/forum/index.php?/topic/18586-forward-slash-in-title-added-incorrectly/ Forum Thread with question and detailed answer]

=Downloading OLDER Versions=

If you want ANY older version of ANY plugin, please go ahead and [http://ithemes.com/forum/ post on our forums please] in the appropriate category with your request and a reason why you want the older version. We will do our best to accommodate such a request (though we can't guarantee it, since we officially support only the latest version of each plugin), and your reasoning helps us figure out whether we should give you an alternate/latest version, a workaround, or if we should suggest something else.

Sometimes, a version of a plugin may not show up in the [http://ithemes.com/member/member.php iThemes Member's area]. In that case, please post in the appropriate category to let us know about it and we will get the right version link up and running as soon as possible.

Regardless of your reasoning, we will offer you something that will do what you want to do if it's a stable feature in one of our previous OR existing stable versions for your exact setup.

Remember, though: support is guaranteed only for the latest, officially supported stable versions of our plugins.

*Related threads
**http://ithemes.com/forum/index.php?/topic/18916-fatal-error-call-to-undefined-function-is-multisite/#p93019
**http://ithemes.com/forum/index.php?/topic/18448-download-legacy-versions-of-backupbuddy/#p86712

Mobile

2011-10-27T21:40:38Z

Bes: Added /* Plugin Conflicts */ section

Advanced technical support for Mobile:

* [[Mobile: Error Codes]]
* [[Mobile: Advanced Debugging]]

=Documentation=

===Theme Creation===
Live themes are stored in /files/pluginbuddy_mobile/THEMENAME/
Non-live original theme files are stored in /wp-content/plugins/mobile/themes/THEMENAME/

If you would like to edit an existing theme you may do so by editing the live theme files. If you do this we suggest unchecking the option in Settings for automatically upgrading theme files on automatic upgrades to prevent your changes from being lost. Style manager edits create a CSS file within /files/pluginbuddy_mobile/THEMENAME.css so that these changes will not be lost on upgrades.

To create a new theme you can just clone an existing theme to /wp-content/uploads/pluginbuddy_mobile/NEWTHEMENAME/

'''Additional Head HTML (includes Apple icon definitions)'''
<pre>
if ( defined('MOBILEBUDDY_HEAD_CONTENT') ) {
echo MOBILEBUDDY_HEAD_CONTENT;
}
</pre>

'''Link to Full Site'''
<pre>
if ( defined('MOBILEBUDDY_FULL_SITE_LINK') ) {
echo '<a href="' . add_query_arg( 'nomobile', '' ) . '">View Full Site</a>';
}
</pre>

=Customize Mobile=

===Extra Customizations Policies===
[http://ithemes.com/codex/page/PluginBuddy#Extra_Customizations Check out the official policy and details on any Extra Customizations]

===Remove Footer Link===
You can remove or change the footer text and/or link that is shown to all mobile users by default.

*1 : To remove OR change that footer, edit the footer.php file in the appropriate theme folder, depending on which Mobile theme you are using. That file will be in one of the theme directories in either of the following directories:
**wp-content/uploads/pluginbuddy_mobile
**OR (on Multisites) wp-content/blogs.dir/X/files/pluginbuddy_mobile (change the X to the appropriate site number)
*2 : Find line 12 of the footer.php to what you want. It currently says <pre brush="html">Mobile Site By <a href="http://pluginbuddy.com/">PluginBuddy</a><br /></pre>
*3 : Change the above to anything you wish to be shown OR hidden from the mobile users in question who will be viewing that theme.

*Related thread:
**http://ithemes.com/forum/index.php?/topic/14450-removing-the-pluginbuddy-link-from-the-footer/

=Plugin Conflicts=
The following plugins are known to cause conflicts with OR in Mobile. You can either disable the following plugins, upgrade them to their latest versions OR let their development team know about this. Mobile works perfectly when such plugins (or some certain versions of them) are not active.

*SexyBookmarks (by Shareaholic) - Version 4.0.6.2
**Dropdown menu has been confirmed to not work properly with this version
***http://ithemes.com/forum/index.php?/topic/19455-mobile-theme-not-working/

=Additional Resources=
* [http://pluginbuddy.com/purchase/mobile/ Purchase Mobile]
* [http://pluginbuddy.com/tutorials/ PluginBuddy Tutorials]
* [http://pluginbuddy.com/ PluginBuddy.com]
* [http://pluginbuddy.com/support/ Support Forums]

[[Category:PluginBuddy]]

PluginBuddy

2011-10-25T17:49:32Z

Bes: Added "Fix" info for W3 Total Cache plugin conflict /* Plugin Conflicts */

Welcome to the PluginBuddy Knowledge Base - Tutorials, Technical Information, Debugging Information, and more.

=Premium Plugins=
* [[Ajax-Edit-Comments]]
* [[BackupBuddy]]
* DisplayBuddy
** [[Accordion]]
** [[Billboard]]
** [[Carousel]]
** [[CopiousComments]]
** [[FeaturedPosts]]
** [[Rotating Images]]
** [[RotatingText]]
** [[Slideshow]]
** [[Tipsy]]
** [[VideoShowcase]]
* [[EmailBuddy]]
* [[LoopBuddy]]
* [[Mobile]]
* [[TailoredLogin]]
* [[ThumbsUp]]
* [[VidEmbed]]

=Free Plugins (active)=
* [[Featured Text]]
* [[PB-Tweet]]
* [[ServerBuddy]]
* [[Tabber Widget]]
* [[ThemeMan]]
* [[S3 URLS]]
* [[YOURLS]]
* [[ContactBuddy]]

=Free Plugins (inactive)=
* [[WP Easy Uploader]]
* [[WP Developer Assistant]]
* [[Easy Theme and Plugin Updater]]
* [[Current Date & Time Widget]]

''[[:Category:PluginBuddy|View all PluginBuddy Wiki Pages]]''

=Misc. Documentation=
==Frequently Asked (Plugin) Questions==
*[[General Plugins FAQ]]

==License Manager Tutorial and Information==
*[[License Manager]]
==PHP Development & Advanced==
*[[.htaccess]]
*[[PHP]]
*[[Arrays]]

[[Category:PluginBuddy]]

=Translations (localization / internationalization)=

Many PluginBuddy plugins come with translation capability. That means such PluginBuddy plugins can be translated (aka localized) to other languages.

===How Translations Work===

PluginBuddy provides the capability to have a translation in such plugins. Anyone wanting to enhance PluginBuddy with specific language translations can do so voluntarily via Translation Files. Translation Files are simply language files created fully and solely by the volunteer community which use the already built in translation-capable features in many of the PluginBuddy plugins to allow such plugins to show text or outputs in different languages. Making PluginBuddy translation-capable is done by PluginBuddy. Creating, updating and sending in any language specific translation files to PluginBuddy is done by the volunteer community.

Anyone can create translation files, package them into the proper format and give PluginBuddy the final translated files that we will try to include in the next update for the plugin in question. We call such awesome people, who create or update the translation files and send us the full translation package files, '''Awesome Translator Volunteers''', and we are really thankful that they take the time to do such an awesome thing.

If you want to help us, you can translate any existing PluginBuddy plugin which supports internationalization (another way of saying localization or translation-capable) and then, once you're fully done, simply let us know in the forums the link to the final language files that we can directly save and simply try to include in any future updates for the plugin(s) in question.

===Tips on how to localize any PluginBuddy Plugin to any non-English language===

The following 9 tips can help you figure out how to approach translations, how to create translations, and how to send us the final translated file for any translation-capable PluginBuddy plugin:

*1 : Many of the PluginBuddy plugins are internationalized, meaning they have the capability to be translated, via actual external translation files, by any non-iThemes-staff Awesome Translator Volunteer who wishes such plugins to be translated to their language.
*2 : If a PluginBuddy plugin is currently not internationalized or you're not sure if it is, you can ask us in the [http://ithemes.com/forum Support Forums] and we'll let you know, or we'll have it included as a future translation feature request. After the translation capability is added to such a plugin, you can submit the actual translation file. Please remember though: we cannot help with creating, understanding or making any language translation files. Our Awesome Translator Volunteers do that voluntarily (you can too! keep on reading) and fully on their own.
*3 : There are MANY resources which teach you how to create and work with WordPress language files. Following are the official 3 directly by the WordPress community:
**1 : [http://codex.wordpress.org/WordPress_in_Your_Language WordPress in Your Language]
**2 : [http://codex.wordpress.org/Translating_WordPress Translating WordPress]
**3 : [http://codex.wordpress.org/I18n_for_WordPress_Developers What WordPress Localization in Plugins is mainly about]
*4 : Translations are sent in from volunteers from all over the world. As a courtesy, we sometimes package the actual language translation files (provided directly by the Awesome Translator Volunteers) in with the final product. If some translation is not included in the actual plugin even when the plugin has the capability to be translated, you can submit the final translation to us for consideration in the next update by posting on our forums OR you can include the translation in your own live or local WordPress install directly for your own use. More info on how to include your own language specific file for your own WordPress sites is in the resources listed in #3 above.
*5 : A translation included in with the final product does not guarantee the accuracy or quality of the translation. These files are from the Awesome Translator Volunteers, and correction of these files is also done by those Awesome Translator Volunteers.
*6 : If a translation is very inaccurate or incomplete, we can put out a request for a new translation from the volunteer community, or remove the translation from the packaged and final product. You can also let us know of any inaccuracies in any existing translation files by the Awesome Volunteers by providing us with the corrected final files. Please remember: we only accept final and full translation files that you yourself have already created or packaged properly. If you let us know only of the actual inaccuracies without providing the final correct files, we cannot make such changes ourselves to the translation files.
*7 : Unfortunately, PluginBuddy cannot work on, help with, create, nor make any updates to any specific translation files you may have, or may be working on, or want to work on. Our Awesome Volunteers do that and simply give us the final files for inclusion or consideration.
*8 : If you have corrections for any existing translation in form of final proper format translation files for an existing language, OR want to provide the final and proper translation files for a new language, please post a new thread in the appropriate product category in the [http://ithemes.com/forum/ PluginBuddy Support Forums] with the final translations files. If you have any support questions on how to create or make language specific translation files, or how translation files work, you can do so on the [http://wordpress.org/support/ WordPress forums], as such support questions are outside the scope of what PluginBuddy support guarantees with your iThemes membership.
*9 : Any final translation file provided by you (or any other Awesome Volunteer) on the support forums will then be saved and filed as a future enhancement request for the future updates of the plugin(s) in question. In your support forum thread, where you share the final complete translation files you inclusion, you can upload your files directly to the forums OR upload them somewhere and link to them in your support forum thread. We will then download and save such files. Remember please: we cannot guarantee looking inside such files or verifying that they are correct in any manner (because of so many languages in the world and so many possible language files everywhere).

Thank you SO MUCH for being interested in providing translation files for our PluginBuddy plugins. We hope you will become one of our Awesome Translator Volunteers, in addition to being our AWESOME CUSTOMER, and create/update any language-specific translation file package and provide it to us so that we can consider including it in future updates.

===Resources for understanding, creating, updating and submitting final translation files===
*Here are the 3 official resources again which you can use to create, update, start work on and finish translation on any of the translation-capable PluginBuddy plugins:
**1 : [http://codex.wordpress.org/WordPress_in_Your_Language WordPress in Your Language]
**2 : [http://codex.wordpress.org/Translating_WordPress Translating WordPress]
**3 : [http://codex.wordpress.org/I18n_for_WordPress_Developers What WordPress Localization in Plugins is mainly about]

=Extra Customizations=
While any extra customization of any PluginBuddy Plugin is beyond the scope of the official support, we do from time to time offer different tips and tutorials on editing the awesome PluginBuddy plugins to better fit your individual needs. All such edits are, however, beyond what is officially supported and provided in the actual plugin admin panel and officially stated features on the individual plugin pages. No official support is provided nor guaranteed in, before, during, after or related to anything resulting from any such edits/customizations.

No support is provided on any of these extra customizations. Any of the steps mentioned in any of these extra custom edits may change at any time depending on newer versions of the plugins being released. Any use or customization of anything, beyond what is provided by default inside the plugin admin menu, means you are proceeding at your own risk and that you accept 100% responsibility and liability for everything you change or modify in any manner in the plugin. Your purchase and use of any PluginBuddy plugin implies and shows that you are buying and using PluginBuddy plugin(s) the way it(they) came in their original unmodified form, with no exceptions.

*Remember:
**[http://pluginbuddy.com/purchase/backupbuddy/ Make a backup of your entire site with BackupBuddy] before making any edits!
** PluginBuddy only supports the official unedited, unmodified versions of all PluginBuddy plugins.
** Use a good text editor to make any file changes. Again, maintain backups!
** Any changes you make to files WILL MOST PROBABLY be lost when the plugin is upgraded to any newer version.
** You are 100% responsible and liable for anything resulting from any of these changes.
** No support is provided nor guaranteed on any of these extra changes in any form or shape, whatsoever, regardless of who suggested these custom edits or suggestions.
** Any extra customization info or suggestion is added voluntarily by PluginBuddy staff to help users as much as possible, even if such customization is outside the scope of any membership support.
** Whether a PluginBuddy staff or representative offered or suggested the edit/customization, another customer or anyone else, PluginBuddy does not officially support nor provide any official support on any such edits.
** We cannot guarantee providing any support on any edits or customization tips we provide.
** Absolutely no support is guaranteed in any manner on any of our free plugins, whether or not there is any customization/edit involved.

=External Plugins Compatibility=

PluginBuddy does not promise, guarantee or provide support for any compatibility with any external plugin. If any PluginBuddy Plugin works without any problems when used with any external plugin in question, that means the PluginBuddy Plugin is most probably working without any issues overall. PluginBuddy is not responsible for making PluginBuddy plugins work in any manner, whether custom, fully, fixed or other, with any external non-PluginBuddy plugins. PluginBuddy is also not responsible for providing any support whatsoever for any external plugin, whether or not such an external plugin is used along with any PluginBuddy plugin.

=Free Plugins=

Free plugins are provided as is. There is no guaranteed support that comes with them. Guaranteed support is limited only and mainly for our premium unmodified plugins.

=Bugs, Features and ETA on new updates=

With every new release of any plugin, there may be a new bug or two. You may also want to have new features added to specific plugins. All existing versions of all plugins can have bugs reported OR new features suggested. All of this is done via the [http://ithemes.com/forum official forums].

New updates are also usually released regularly and at the same time, at very different paces, depending on the current number of bugs, features, new plans and tasks at hand. Therefore it is the official policy that there is NO pre-defined ETA on any bug fix, feature imeplemention OR new update OR new plugin roll-out UNLESS otherwise specified specifically in writing somewhere by an official iThemes employee.

==Bugs, bug reports and bug fixes==

Bug reports are filed and noted as they are encountered (thanks for reporting them to us!). There is never any ETA on any bug fixes unless otherwise noted.

==Feature Requests==

Feature requests and feature suggestions are basically future suggested features that users can suggest, and/or future features PluginBuddy may consider adding to the future versions of the plugin(s) in question (again, thanks for suggesting new features!).

There is no guaranteed ETA on when such feature requests will be implemented, unless otherwise noted. All suggested features are just that: suggestions. They remain suggestions until they're confirmed as officially in the works and to be included. Even then, unless a feature is actually rolled out publicly, there is no guarantee any feature suggestion will be implemented. We do our best to try and accommodate as many feature suggestions as possible.

Also, there is no guarantee that any feature request suggested will be implemented, unless otherwise noted.

==ETA on new updates==

Just like bug fixes and new features, there is never a guaranteed date nor a guaranteed time frame on when new updates will roll out. We work every single day of the week, all the time, on our plugins and thus every day there is something new and improved happening in almost all our plugins daily. Whenever we are ready to release any new updates publicly, you'll find out by seeing the plugin update notice in your WordPress OR in your [http://ithemes.com/member/member.php Member's area].

=What does BETA mean?=

Some of PluginBuddy plugins may be in Beta status OR may have Beta features. BETA simply means that some feature or specific part of the plugin is currently still in testing mode, and can cause issues if not used properly. All BETA plugins/features are not yet 100% stable, and thus should NOT be relied on to be working properly OR working at all. Throughout the iThemes Codex, any time the word "Beta" is used in any form, it refers to Beta plugins, Beta features, Beta status and/or anything related to the Beta nature that is officially announced or mentioned as such by any iThemes staff or on any of the Plugin pages, or in this Codex.

Beta implies that any new features or plugins are very close to being released as 100% working very soon, and that there may still be some issues to fix or test more before removing the Beta status. Since no single software of any kind can be tested under every system and site configuration in the world, the Beta status enables the Beta features to be tested out by as many people on as many different websites and configurations as possible.

*Some points to keep in mind when using any BETA plugin/feature:
**1 : Make [http://pluginbuddy.com/purchase/backupbuddy/ FULL WordPress backups] before using ANY beta feature.
**2 : Beta means that the current software feature is NOT complete, and that you are NOT forced to use such a feature at all. You are advised to WAIT until the BETA status is removed.
**3 : Using any Beta feature of any kind, whether it is an entire plugin or something inside a plugin, means and shows that you are fully accepting any liability for any risks involved.
**4 : Using any Beta feature of any kind, whether it is an entire plugin or something inside a plugin, means and shows that you are fully aware that there are all different kinds of risks involved with such features.
**5 : If you are concerned about your important data or anything bad that might happen as a result of using any Beta feature, do NOT use such Beta features.
**6 : ALWAYS make full [http://pluginbuddy.com/purchase/backupbuddy/ BackupBuddy Backups of all your important data] before using any Beta software, whether that Beta software is from PluginBuddy or from any other place.
**7 : If any issues are found in Beta, they are usually added to the list of bug fixes to be released as a whole, or for the next big update, instead of being updated OR fixed individually on a case by case basis.
**8 : Beta features are recommended to test and play with on test sites/servers and configurations with any dummy data, as long as you have [http://pluginbuddy.com/purchase/backupbuddy/ full backups of all important data] still.
**9 : iThemes is not liable nor cannot be held accountable for any unwanted results resulting from the use of BETA features.
**10 : The very name and nature of BETA shows clearly, without any doubt, that there will most probably be issues and problems involved when such labeled features are used anywhere.
**11 : Support for Beta features may be very limited. We usually simply collect all reports related to Beta features and collect them all for one big update in the future.
**12 : If you lose any important data or settings anywhere, or encounter damaged data or settings anywhere, because of any Beta feature, we will not be able to help you and will simply tell you to revert to your previous [http://pluginbuddy.com/purchase/backupbuddy/ backups]. We will also tell you to always wait for BETA status to be removed before using any such features.

If you do not fully understand what Beta means, OR are not willing to fully accept and be fully liable for any risks involved because of using such Beta software, you should NOT use the Beta software in any manner. In such a case, you should simply wait until the Beta status is removed.

*[http://pluginbuddy.com/what-does-beta-mean/ Blog post announcing what BETA means]

=PluginBuddy Licenses=

==Plugin Conflicts==

Some times, external plugins may cause issues in detaching, deleting, generating OR saving license keys. Such plugins may also cause issues when you want to manually or automatically upgrade plugins when you try to solve licensing issues.

Following is a list of currently known plugins which cause license detaching, deleting, generating OR saving issues. Please disable the following plugins, even temporarily, while you perform all the steps of manually OR automatically upgrading the PluginBuddy plugins in question, and detaching, deleting, generating and saving license keys for them. Keep such plugins disabled UNTIL all license key issues are gone OR at least while you perform these steps.

*Plugins causing PluginBuddy licensing issues
**'''W3 Total Cache :''' If you are using any caching plugin like W3 Total Cache, please disable it and then carry out any required steps.
***Fix: Follow the above steps to fix this issue. [http://ithemes.com/forum/index.php?/topic/19436-backupbuddy-license-issue/#p92171 Steps also explained by BackupBuddy customer Laura (thanks!)]

*Related Links
**1 : [http://ithemes.com/forum/index.php?/topic/19079-wont-let-me-set-a-license-key/#p91663 W3 Total Cache plugin conflict and solution]
**2 : [http://ithemes.com/forum/index.php?/topic/19436-backupbuddy-license-issue/#p92171 W3 Total Cache plugin conflict and solution]

==September, 2011 Licensing Issues==

'''This issue is now resolved and the update already out.''' Upgrade manually to the latest versions of the plugins and such issues will go away.

Some users reported (in mid-September, 2011) that they were having issues with their license inside the Licenses area of different PluginBuddy plugins, including BackupBuddy.

Remember: All your PluginBuddy plugins, including BackupBuddy, will CONTINUE WORKING PERFECTLY even with these licensing issues. You can keep using the plugins exactly how you want them even during these licensing issues. Your plugins are NOT affected by this licensing situation in any manner.

Your membership is also completely fine and you have NOT lost any license(s). The issue is happening to some customers who simply need to upgrade manually to the latest version of their plugin, if the automatic upgrade does not work.

*Plugins with the update versions which remove this issue completely
**ALL PluginBuddy Products

*You can upgrade via one of the following:
**Automatically upgrade to the latest version
**Manually update by downloading the latest zip version of your PluginBuddy plugin from your Member's panel and then
***Overwrite your existing plugin directory via FTP with the new files.
***De-activate the existing plugin, delete it via your '''WordPress --> Plugins''' area and then upload the newly downloaded zip file. Then re-activate the plugin.
**That will remove the issue completely.
*DETACH the key and then RE-ATTACH the license key for the specific site in question IF licensing still shows issues AFTER manually upgrading (for example, manually upgrading to at least BackupBuddy 2.2.24 - other plugins have their own new version numbers - check your Member's area for the latest version download)
*Also make sure to DETACH the key, DELETE that same AND any other keys related to that specific site from the entire licenses area, and then GENERATE a new key for that site IF detaching and re-attaching the license key does not work AFTER manually upgrading (for example, manually upgrading to at least BackupBuddy 2.2.24 - other plugins have their own new version numbers - check your Member's area for the latest version download)

[http://ithemes.com/forum/index.php?/topic/6691-read-this-first-pluginbuddy-licensing-issues/page-2/#p85977 First reports]

PluginBuddy

2011-10-25T17:47:29Z

Bes: Added another W3 Total Cache plugin conflict and solution forum link to "Related Links" section /* Plugin Conflicts */

Welcome to the PluginBuddy Knowledge Base - Tutorials, Technical Information, Debugging Information, and more.

=Premium Plugins=
* [[Ajax-Edit-Comments]]
* [[BackupBuddy]]
* DisplayBuddy
** [[Accordion]]
** [[Billboard]]
** [[Carousel]]
** [[CopiousComments]]
** [[FeaturedPosts]]
** [[Rotating Images]]
** [[RotatingText]]
** [[Slideshow]]
** [[Tipsy]]
** [[VideoShowcase]]
* [[EmailBuddy]]
* [[LoopBuddy]]
* [[Mobile]]
* [[TailoredLogin]]
* [[ThumbsUp]]
* [[VidEmbed]]

=Free Plugins (active)=
* [[Featured Text]]
* [[PB-Tweet]]
* [[ServerBuddy]]
* [[Tabber Widget]]
* [[ThemeMan]]
* [[S3 URLS]]
* [[YOURLS]]
* [[ContactBuddy]]

=Free Plugins (inactive)=
* [[WP Easy Uploader]]
* [[WP Developer Assistant]]
* [[Easy Theme and Plugin Updater]]
* [[Current Date & Time Widget]]

''[[:Category:PluginBuddy|View all PluginBuddy Wiki Pages]]''

=Misc. Documentation=
==Frequently Asked (Plugin) Questions==
*[[General Plugins FAQ]]

==License Manager Tutorial and Information==
*[[License Manager]]
==PHP Development & Advanced==
*[[.htaccess]]
*[[PHP]]
*[[Arrays]]

[[Category:PluginBuddy]]

=Translations (localization / internationalization)=

Many PluginBuddy plugins come with translation capability. That means such PluginBuddy plugins can be translated (aka localized) to other languages.

===How Translations Work===

PluginBuddy provides the capability to have a translation in such plugins. Anyone wanting to enhance PluginBuddy with specific language translations can do so voluntarily via Translation Files. Translation Files are simply language files created fully and solely by the volunteer community which use the already built in translation-capable features in many of the PluginBuddy plugins to allow such plugins to show text or outputs in different languages. Making PluginBuddy translation-capable is done by PluginBuddy. Creating, updating and sending in any language specific translation files to PluginBuddy is done by the volunteer community.

Anyone can create translation files, package them into the proper format and give PluginBuddy the final translated files that we will try to include in the next update for the plugin in question. We call such awesome people, who create or update the translation files and send us the full translation package files, '''Awesome Translator Volunteers''', and we are really thankful that they take the time to do such an awesome thing.

If you want to help us, you can translate any existing PluginBuddy plugin which supports internationalization (another way of saying localization or translation-capable) and then, once you're fully done, simply let us know in the forums the link to the final language files that we can directly save and simply try to include in any future updates for the plugin(s) in question.

===Tips on how to localize any PluginBuddy Plugin to any non-English language===

The following 9 tips can help you figure out how to approach translations, how to create translations, and how to send us the final translated file for any translation-capable PluginBuddy plugin:

*1 : Many of the PluginBuddy plugins are internationalized, meaning they have the capability to be translated, via actual external translation files, by any non-iThemes-staff Awesome Translator Volunteer who wishes such plugins to be translated to their language.
*2 : If a PluginBuddy plugin is currently not internationalized or you're not sure if it is, you can ask us in the [http://ithemes.com/forum Support Forums] and we'll let you know, or we'll have it included as a future translation feature request. After the translation capability is added to such a plugin, you can submit the actual translation file. Please remember though: we cannot help with creating, understanding or making any language translation files. Our Awesome Translator Volunteers do that voluntarily (you can too! keep on reading) and fully on their own.
*3 : There are MANY resources which teach you how to create and work with WordPress language files. Following are the official 3 directly by the WordPress community:
**1 : [http://codex.wordpress.org/WordPress_in_Your_Language WordPress in Your Language]
**2 : [http://codex.wordpress.org/Translating_WordPress Translating WordPress]
**3 : [http://codex.wordpress.org/I18n_for_WordPress_Developers What WordPress Localization in Plugins is mainly about]
*4 : Translations are sent in from volunteers from all over the world. As a courtesy, we sometimes package the actual language translation files (provided directly by the Awesome Translator Volunteers) in with the final product. If some translation is not included in the actual plugin even when the plugin has the capability to be translated, you can submit the final translation to us for consideration in the next update by posting on our forums OR you can include the translation in your own live or local WordPress install directly for your own use. More info on how to include your own language specific file for your own WordPress sites is in the resources listed in #3 above.
*5 : A translation included in with the final product does not guarantee the accuracy or quality of the translation. These files are from the Awesome Translator Volunteers, and correction of these files is also done by those Awesome Translator Volunteers.
*6 : If a translation is very inaccurate or incomplete, we can put out a request for a new translation from the volunteer community, or remove the translation from the packaged and final product. You can also let us know of any inaccuracies in any existing translation files by the Awesome Volunteers by providing us with the corrected final files. Please remember: we only accept final and full translation files that you yourself have already created or packaged properly. If you let us know only of the actual inaccuracies without providing the final correct files, we cannot make such changes ourselves to the translation files.
*7 : Unfortunately, PluginBuddy cannot work on, help with, create, nor make any updates to any specific translation files you may have, or may be working on, or want to work on. Our Awesome Volunteers do that and simply give us the final files for inclusion or consideration.
*8 : If you have corrections for any existing translation in form of final proper format translation files for an existing language, OR want to provide the final and proper translation files for a new language, please post a new thread in the appropriate product category in the [http://ithemes.com/forum/ PluginBuddy Support Forums] with the final translations files. If you have any support questions on how to create or make language specific translation files, or how translation files work, you can do so on the [http://wordpress.org/support/ WordPress forums], as such support questions are outside the scope of what PluginBuddy support guarantees with your iThemes membership.
*9 : Any final translation file provided by you (or any other Awesome Volunteer) on the support forums will then be saved and filed as a future enhancement request for the future updates of the plugin(s) in question. In your support forum thread, where you share the final complete translation files you inclusion, you can upload your files directly to the forums OR upload them somewhere and link to them in your support forum thread. We will then download and save such files. Remember please: we cannot guarantee looking inside such files or verifying that they are correct in any manner (because of so many languages in the world and so many possible language files everywhere).

Thank you SO MUCH for being interested in providing translation files for our PluginBuddy plugins. We hope you will become one of our Awesome Translator Volunteers, in addition to being our AWESOME CUSTOMER, and create/update any language-specific translation file package and provide it to us so that we can consider including it in future updates.

===Resources for understanding, creating, updating and submitting final translation files===
*Here are the 3 official resources again which you can use to create, update, start work on and finish translation on any of the translation-capable PluginBuddy plugins:
**1 : [http://codex.wordpress.org/WordPress_in_Your_Language WordPress in Your Language]
**2 : [http://codex.wordpress.org/Translating_WordPress Translating WordPress]
**3 : [http://codex.wordpress.org/I18n_for_WordPress_Developers What WordPress Localization in Plugins is mainly about]

=Extra Customizations=
While any extra customization of any PluginBuddy Plugin is beyond the scope of the official support, we do from time to time offer different tips and tutorials on editing the awesome PluginBuddy plugins to better fit your individual needs. All such edits are, however, beyond what is officially supported and provided in the actual plugin admin panel and officially stated features on the individual plugin pages. No official support is provided nor guaranteed in, before, during, after or related to anything resulting from any such edits/customizations.

No support is provided on any of these extra customizations. Any of the steps mentioned in any of these extra custom edits may change at any time depending on newer versions of the plugins being released. Any use or customization of anything, beyond what is provided by default inside the plugin admin menu, means you are proceeding at your own risk and that you accept 100% responsibility and liability for everything you change or modify in any manner in the plugin. Your purchase and use of any PluginBuddy plugin implies and shows that you are buying and using PluginBuddy plugin(s) the way it(they) came in their original unmodified form, with no exceptions.

*Remember:
**[http://pluginbuddy.com/purchase/backupbuddy/ Make a backup of your entire site with BackupBuddy] before making any edits!
** PluginBuddy only supports the official unedited, unmodified versions of all PluginBuddy plugins.
** Use a good text editor to make any file changes. Again, maintain backups!
** Any changes you make to files WILL MOST PROBABLY be lost when the plugin is upgraded to any newer version.
** You are 100% responsible and liable for anything resulting from any of these changes.
** No support is provided nor guaranteed on any of these extra changes in any form or shape, whatsoever, regardless of who suggested these custom edits or suggestions.
** Any extra customization info or suggestion is added voluntarily by PluginBuddy staff to help users as much as possible, even if such customization is outside the scope of any membership support.
** Whether a PluginBuddy staff or representative offered or suggested the edit/customization, another customer or anyone else, PluginBuddy does not officially support nor provide any official support on any such edits.
** We cannot guarantee providing any support on any edits or customization tips we provide.
** Absolutely no support is guaranteed in any manner on any of our free plugins, whether or not there is any customization/edit involved.

=External Plugins Compatibility=

PluginBuddy does not promise, guarantee or provide support for any compatibility with any external plugin. If any PluginBuddy Plugin works without any problems when used with any external plugin in question, that means the PluginBuddy Plugin is most probably working without any issues overall. PluginBuddy is not responsible for making PluginBuddy plugins work in any manner, whether custom, fully, fixed or other, with any external non-PluginBuddy plugins. PluginBuddy is also not responsible for providing any support whatsoever for any external plugin, whether or not such an external plugin is used along with any PluginBuddy plugin.

=Free Plugins=

Free plugins are provided as is. There is no guaranteed support that comes with them. Guaranteed support is limited only and mainly for our premium unmodified plugins.

=Bugs, Features and ETA on new updates=

With every new release of any plugin, there may be a new bug or two. You may also want to have new features added to specific plugins. All existing versions of all plugins can have bugs reported OR new features suggested. All of this is done via the [http://ithemes.com/forum official forums].

New updates are also usually released regularly and at the same time, at very different paces, depending on the current number of bugs, features, new plans and tasks at hand. Therefore it is the official policy that there is NO pre-defined ETA on any bug fix, feature imeplemention OR new update OR new plugin roll-out UNLESS otherwise specified specifically in writing somewhere by an official iThemes employee.

==Bugs, bug reports and bug fixes==

Bug reports are filed and noted as they are encountered (thanks for reporting them to us!). There is never any ETA on any bug fixes unless otherwise noted.

==Feature Requests==

Feature requests and feature suggestions are basically future suggested features that users can suggest, and/or future features PluginBuddy may consider adding to the future versions of the plugin(s) in question (again, thanks for suggesting new features!).

There is no guaranteed ETA on when such feature requests will be implemented, unless otherwise noted. All suggested features are just that: suggestions. They remain suggestions until they're confirmed as officially in the works and to be included. Even then, unless a feature is actually rolled out publicly, there is no guarantee any feature suggestion will be implemented. We do our best to try and accommodate as many feature suggestions as possible.

Also, there is no guarantee that any feature request suggested will be implemented, unless otherwise noted.

==ETA on new updates==

Just like bug fixes and new features, there is never a guaranteed date nor a guaranteed time frame on when new updates will roll out. We work every single day of the week, all the time, on our plugins and thus every day there is something new and improved happening in almost all our plugins daily. Whenever we are ready to release any new updates publicly, you'll find out by seeing the plugin update notice in your WordPress OR in your [http://ithemes.com/member/member.php Member's area].

=What does BETA mean?=

Some of PluginBuddy plugins may be in Beta status OR may have Beta features. BETA simply means that some feature or specific part of the plugin is currently still in testing mode, and can cause issues if not used properly. All BETA plugins/features are not yet 100% stable, and thus should NOT be relied on to be working properly OR working at all. Throughout the iThemes Codex, any time the word "Beta" is used in any form, it refers to Beta plugins, Beta features, Beta status and/or anything related to the Beta nature that is officially announced or mentioned as such by any iThemes staff or on any of the Plugin pages, or in this Codex.

Beta implies that any new features or plugins are very close to being released as 100% working very soon, and that there may still be some issues to fix or test more before removing the Beta status. Since no single software of any kind can be tested under every system and site configuration in the world, the Beta status enables the Beta features to be tested out by as many people on as many different websites and configurations as possible.

*Some points to keep in mind when using any BETA plugin/feature:
**1 : Make [http://pluginbuddy.com/purchase/backupbuddy/ FULL WordPress backups] before using ANY beta feature.
**2 : Beta means that the current software feature is NOT complete, and that you are NOT forced to use such a feature at all. You are advised to WAIT until the BETA status is removed.
**3 : Using any Beta feature of any kind, whether it is an entire plugin or something inside a plugin, means and shows that you are fully accepting any liability for any risks involved.
**4 : Using any Beta feature of any kind, whether it is an entire plugin or something inside a plugin, means and shows that you are fully aware that there are all different kinds of risks involved with such features.
**5 : If you are concerned about your important data or anything bad that might happen as a result of using any Beta feature, do NOT use such Beta features.
**6 : ALWAYS make full [http://pluginbuddy.com/purchase/backupbuddy/ BackupBuddy Backups of all your important data] before using any Beta software, whether that Beta software is from PluginBuddy or from any other place.
**7 : If any issues are found in Beta, they are usually added to the list of bug fixes to be released as a whole, or for the next big update, instead of being updated OR fixed individually on a case by case basis.
**8 : Beta features are recommended to test and play with on test sites/servers and configurations with any dummy data, as long as you have [http://pluginbuddy.com/purchase/backupbuddy/ full backups of all important data] still.
**9 : iThemes is not liable nor cannot be held accountable for any unwanted results resulting from the use of BETA features.
**10 : The very name and nature of BETA shows clearly, without any doubt, that there will most probably be issues and problems involved when such labeled features are used anywhere.
**11 : Support for Beta features may be very limited. We usually simply collect all reports related to Beta features and collect them all for one big update in the future.
**12 : If you lose any important data or settings anywhere, or encounter damaged data or settings anywhere, because of any Beta feature, we will not be able to help you and will simply tell you to revert to your previous [http://pluginbuddy.com/purchase/backupbuddy/ backups]. We will also tell you to always wait for BETA status to be removed before using any such features.

If you do not fully understand what Beta means, OR are not willing to fully accept and be fully liable for any risks involved because of using such Beta software, you should NOT use the Beta software in any manner. In such a case, you should simply wait until the Beta status is removed.

*[http://pluginbuddy.com/what-does-beta-mean/ Blog post announcing what BETA means]

=PluginBuddy Licenses=

==Plugin Conflicts==

Some times, external plugins may cause issues in detaching, deleting, generating OR saving license keys. Such plugins may also cause issues when you want to manually or automatically upgrade plugins when you try to solve licensing issues.

Following is a list of currently known plugins which cause license detaching, deleting, generating OR saving issues. Please disable the following plugins, even temporarily, while you perform all the steps of manually OR automatically upgrading the PluginBuddy plugins in question, and detaching, deleting, generating and saving license keys for them. Keep such plugins disabled UNTIL all license key issues are gone OR at least while you perform these steps.

*Plugins causing PluginBuddy licensing issues
**'''W3 Total Cache :''' If you are using any caching plugin like W3 Total Cache, please disable it and then carry out any required steps.

*Related Links
**1 : [http://ithemes.com/forum/index.php?/topic/19079-wont-let-me-set-a-license-key/#p91663 W3 Total Cache plugin conflict and solution]
**2 : [http://ithemes.com/forum/index.php?/topic/19436-backupbuddy-license-issue/#p92171 W3 Total Cache plugin conflict and solution]

==September, 2011 Licensing Issues==

'''This issue is now resolved and the update already out.''' Upgrade manually to the latest versions of the plugins and such issues will go away.

Some users reported (in mid-September, 2011) that they were having issues with their license inside the Licenses area of different PluginBuddy plugins, including BackupBuddy.

Remember: All your PluginBuddy plugins, including BackupBuddy, will CONTINUE WORKING PERFECTLY even with these licensing issues. You can keep using the plugins exactly how you want them even during these licensing issues. Your plugins are NOT affected by this licensing situation in any manner.

Your membership is also completely fine and you have NOT lost any license(s). The issue is happening to some customers who simply need to upgrade manually to the latest version of their plugin, if the automatic upgrade does not work.

*Plugins with the update versions which remove this issue completely
**ALL PluginBuddy Products

*You can upgrade via one of the following:
**Automatically upgrade to the latest version
**Manually update by downloading the latest zip version of your PluginBuddy plugin from your Member's panel and then
***Overwrite your existing plugin directory via FTP with the new files.
***De-activate the existing plugin, delete it via your '''WordPress --> Plugins''' area and then upload the newly downloaded zip file. Then re-activate the plugin.
**That will remove the issue completely.
*DETACH the key and then RE-ATTACH the license key for the specific site in question IF licensing still shows issues AFTER manually upgrading (for example, manually upgrading to at least BackupBuddy 2.2.24 - other plugins have their own new version numbers - check your Member's area for the latest version download)
*Also make sure to DETACH the key, DELETE that same AND any other keys related to that specific site from the entire licenses area, and then GENERATE a new key for that site IF detaching and re-attaching the license key does not work AFTER manually upgrading (for example, manually upgrading to at least BackupBuddy 2.2.24 - other plugins have their own new version numbers - check your Member's area for the latest version download)

[http://ithemes.com/forum/index.php?/topic/6691-read-this-first-pluginbuddy-licensing-issues/page-2/#p85977 First reports]

Slideshow

2011-10-21T21:56:09Z

Bes: Added /* Change or Remove Slideshow Shadows */ sub-section

{{#ev:youtube|lxlqcjiR9zw|400|right}}
'''Series:''' [[DisplayBuddy]]
==Description==
This plugin add the ability to display image slideshows anywhere on your site with fully customizable animated transitions and advanced effects. Slideshow has two different sliders that you can choose from, Slider and Cycle. Each slider has different animation effects and customizations.

==Slider==
The transitions for this mode focus on slicing up the image into multiple pieces and using those pieces for different transition effects.Since this mode focuses on slicing up the image for transition effects the settings for this mode also allow you to choose how many slices the image is divided into. This mode also offers the ability to display small thumbnail versions of the images in the group as pagination buttons that allow visitors to your site to easily control which image the slider is showing.

'''Animation transition effects'''
* Randomly use different effects
* Slice down
* Slice down left
* Slice up
* Slice up left
* Fold
* Fade

==Cycle==
The transitions for this mode focuses on shuffling images around. This mode has many different effects to choose from, providing more options so that you can pick the effect that you like the best.

'''Animation transition effects'''

blindX, blindY, blindZ, cover, curtainX, curtainY, fade, fadeZoom, growX, growY, scrollUp, scrollDown, scrollLeft, scrollRight, scrollHorz, scrollVert, shuffle, slideX, slideY, toss, turnUp, turnDown, turnLeft, turnRight, uncover, wipe, and zoom.

==Groups==
Carousel has the ability to save multiple groups that can each have different images and settings. The only information required to create a group is a group name.

==Adding Images==
In order to add images you will need to select a group then adjust the "Slide Image Dimensions" width and height so that the Carousel plugin will know what dimensions it will need to resize the images to. After saving the desired image dimensions then you can add an image by clicking the "+Add image" button. Carousel uses WordPress's built in media up-loader. This will allow you to either upload new images or select images that you have already added to the media library. In order to select an image to add from the list of images click the "show" link for that image and then click the "select this image" button as shown in the image below.

[[File:Displaybuddyselectimage.png|408px]]

==Displaying Slideshow on your site==
Slideshow can be added to your site using two different methods, widgets or shortcode.
====Widget====
Navigate to the Widgets area under Appearance in the WordPress Admin area. Drag the Slideshow widget into the widget area that you would like for it to display in and select the group from the drop-down menu that you would like to display.
====Shortcode====
The groups table in slideshow will display a shortcode for each different group that you have created. If you would like to add a Slideshow group to a post or page all you have to do is copy that shortcode and paste it the content of the page or post you would like for it to display in.

==Customize Slideshow==

====Extra Customizations Policies====
[http://ithemes.com/codex/page/PluginBuddy#Extra_Customizations Check out the official policy and details on any Extra Customizations]

====Change Background Color of Caption Text====
Put the following in your theme's CSS file at the very end, changing the color code example used here, #fd4507 which is red, to anything you wish:

<pre brush="css">
.nivo-caption {
background-color: #fd4507 !important;
}
</pre>
*Related links:
**http://ithemes.com/forum/index.php?/topic/18152-background-color/

====Show Image OR Text OVER Slideshow====
You can also show images or texts ON TOP OF (over) a Slideshow so that the slides and the image/text blend in together.

Use the following template to add the necessary code to your theme's css file at the very end.
<pre brush="css">
#builder-module-4e738d2279b5e .builder-module-block { /* Shows any top area TEXT, that is in a widget ABOVE the Slideshow WIDGET< on top of the Slideshow. Change the module # to your own current module # */
position: absolute;
z-index: 2 ! important;
}

#builder-module-4e738d2279b21 img { /* Positions the image in question from a certain Widget module right above the Slideshow. Change this module # to your own widget's module # */
padding-top: 30px ! important;
position: absolute;
z-index: 1 ! important;
}
#pb_slideshow_slider-1 .nivo-slice { /* Prevents the Slideshow transitions from hiding the overlapping text or image. This means NO MORE TRANSITIONS. This will also mean that the styling is applied to Slideshow numbered 1 (one) in your Slideshow admin area. The Slideshow shortcode will show you what number it is. */
display: none;
}
</pre>

*Related link
**http://ithemes.com/forum/index.php?/topic/18317-is-it-possible-to-have-slideshow-run-images-behind-header-title/#p86185

====Change/Remove Empty Space Under Slideshow OR Change Slideshow Height====

If you want, you can customize the height of your Slideshow so that it can also change or remove the empty space under Slideshows.

Use the following css styling template in your theme's css file:
<pre brush="css">
#builder-module-4e74d5b55108d .builder-module-block-outer-wrapper { /* This will change the entire Builder widget, in which the Slideshow is, to a height of 250px. Be sure to change the module # to your own current module # in question. You can change the 250px height to anything you want. */
height: 250px !important;
}
</pre>

*Related link
**http://ithemes.com/forum/index.php?/topic/18317-is-it-possible-to-have-slideshow-run-images-behind-header-title/#p86698

====Change or Remove Slideshow Shadows====

You can change OR remove the slideshow shadows, regardless of the Shadow settings in your Slideshow groups.

To remove the shadow completely, put the following in your theme's css file:

<pre brush="css">
.nivoSlider {
-moz-box-shadow:0px 0px 0px #333 !important;
-webkit-box-shadow:0px 0px 0px #333 !important;
box-shadow:0px 0px 0px #333 !important;
}
</pre>

To change the color or size of the shadows instead of removing them, change the #333 to any other color, and the "0" to any number you want for the size of the shadow.

*Related links
**[http://www.webmonkey.com/2010/02/color_charts/ Color hex codes]
**[http://ithemes.com/forum/index.php?/topic/19434-cannot-remove-shadow-around-slideshow/ Client shadow question and answer]

==FAQ==

====Absolute Links====
Currently, you must use absolute links in Slideshow is order for them to be processed and to be shown.

For example, using <code>/support</code> will NOT work. However, <code>http://www.ithemes.com/support</code> will work.

==Additional Resources==
# [http://pluginbuddy.com/free-wordpress-plugins/ Free Plugins by PluginBuddy]
# [http://pluginbuddy.com/tutorials/ PluginBuddy Tutorials]
# [http://pluginbuddy.com/ PluginBuddy.com]
# [http://pluginbuddy.com/support/ Support Forums]

[[Category:PluginBuddy]]