thumb
Please note: This is the MBSCore Edition and requires the MBSCore kit
If you have already bought the MBSCore kit or any of the kits that contain it then you can buy this cheaper version of the WordPress Login kit. With the exception of being cheaper because it excludes the code you already have in your project, this is the same product as the standalone WordPress Login kit

Key features

  1. Login using existing website credentials
  2. Create an account on your website directly from within your game
  3. Share login details across all your games
  4. Automatically receive ANY user data stored in the usermeta table as soon as login succeeded
  5. All functions and data are stored statically and can thus be accessed at any time from any script in any scene without having to link anything to anything else
  6. Includes a fully functional and 100% skin-able UGUI prefab to get started ASAP
  7. GUI and functionality are kept separate. This makes the kit 100% GUI agnostic. Create your own GUI using any system you wish. No need to modify the code to make it work with your chosen GUI system
  8. Install the kit once and use it with all your current and future games
  9. Supports the "Remember me" option and auto login if enabled
  10. Temporarily kick or permanently ban users from specific games
  11. Features password resetting in case you can't log in
  12. Allows password changing for logged in users
  13. Update basic personal info: real names, email, website details
  14. Use your existing Gravatar image as your in-game avatar
  15. Select Gravatar type to generate for users who don't have a Gravatar account
  16. Fetch the appropriate age restricted Gravatar for your game
  17. Auto detects additional installed assets and provide settings for them in the inspector also for a one stop location to edit all settings for all installed kits
  18. Includes a security feature to prevent outside tampering with your site or games
  19. Incredibly easy to add new, custom functionality to the kit. (See the FAQ tab for details)
  20. Features a number of callbacks to hook into for all server responses
  21. Every call to the server results in either a success or failure response, offering you full control over what to do after contacting the server for any reason...

Implementation into your own games

  1. Install the plugin on your website if you haven't done so already
  2. In your DashBoard click on All Games to create a new game just like a normal WordPress post. This will generated the Game ID
  3. In Unity, give the prefab your website url and the game ID
  4. Drag the prefab into a scene
  5. Hit play, your game is now configured to run from your site!

Website features

WULogin includes a full featured dashboard from which to configure everything related to this and other kits in the series. The dashboard displays all additional installed plugins and their respective settings in one convenient location giving you a one stop location to manage everything related to all WUSS plugins. Dashboard settings restricted to admin access only

Includes ShortCodes and widgets to help you in creating your website

  1. Create a default game layout and have the kit auto generate game pages for you. You create the page content when you generate the game and WordPress Login will generate pages for all your games using your shared layout and custom page content
  2. Create a page that automatically generates banners to point to your game's pages
  3. Generate vertical or horizontal banners
  4. Generate a poster image with rounded corners and customizable styles
  5. Display user's status for the current game (Good, kicked, banned)
  6. Learn more about the WUSS PORTAL here..!

Display WebGL games on your website

  1. Include a placeholder graphic so games don't load automatically (Save user's bandwidth)
  2. ...or load games automatically without placeholder images. Your choice.

5 reviews for WordPress Login: MBSCore

  1. Rated 5 out of 5

    e_m_jacobsen on 2018-09-22 03:44:05

    Great customer service - Linking Unity and Wordpress is a great concept and I'm very happy to have found this plugin. I am new to game design but the seller of this plugin is incredibly helpful!

  2. Rated 5 out of 5

    obstudio on 2018-06-26 20:09:15

    Awesome asset and developer - Power of wordpress in games starts here! Awesome asset with very low entry threshold, but also expanded. With demo scene you can log into your WP in 2-3 minutes, just like that. Support just awesome. In my case not everything was working out of the box. After very long and constructive discussion with developer we found that the problem my hosting. Without this help probably I would drop my plans for using WP in my gamedev. If you're not sure for buying it contact the dev and see for your self. Warning: it's so easy that you will want all plugins from this ecosystem :D

  3. Rated 5 out of 5

    rexcheung on 2018-02-09 15:43:28

    Great Response - The developer is responsive with in-depth discussion. It is the easiest way to integrate my user data with web service.

  4. Rated 5 out of 5

    Parrot-Wing on 2017-08-05 16:32:41

    Responsive developer - Initially I had some issues getting the kit working but the developer responded to my questions promptly and helped me sort out the problem. Overall I'm very satisfied with the kit and support.

  5. Rated 5 out of 5

    Vygar on 2017-06-05 13:53:39

    Excellent - This package is very well constructed and documented.

THE TUTORIALS SECTION FOR THIS ITEM IS STILL UNDER CONSTRUCTION

Please check back in soon...

v5.2.2
– You can still fetch the games list from your website like normal or you can now manually enter the Game ID into WPServer

v5.2.1
– Added a new login function to WULogin called AttemptTrustedLogin
– Added a sample function to the prefab to show how it can be used
– Updated the wuss_login plugin to enable this new functionality
– This function allows a person to sign in on your website using only an email and no password
The intended use is to log a person in on your site AFTER you have verified their
identity via Facebook or Twitter or some other means via a 3rd party asset
WARNING: POSSIBLE SECURITY LEAK FOR YOUR WEBSITE!
If you do not intend to use Facebook or Twitter or sites like those to log into your
website from within Unity then you might want to delete or comment out the loginTrustedLogin
function. Alternatively, be sure to set a security string via the Dashboard and in the Unity
prefab. Since all data is protected by an MD5 key and token you should be safe after setting this

v5.2
– Converted WULogin into a static class so you no longer need to derive your classes from it
– All the login preferences that you used to set in the inspector is now placed inside WULoginPrefs.cs
– Updated the documentation to make note of a missing step during setup

v5.1.2
– Updated the wuss_login plugin to accomodate the new search functions in the dashboard. Update your plugin to this version
– Added yet documentation to help new people get started with the kit and hopefully answer more of the commonly asked question

v5.1.1
– Added a new demo scene demonstrating how to use the WULogin kit across different scene loads
– Created a new login prefab from WULoginCanvas which does not contain the WPServer component
– Use this when you are using WPServer as a standalone singleton loaded during bootstrap

v5.1
– Added a new demo scene to demonstrate loggin in and out of an account with absolutely no GUI at all. 100% code based.
– Added a new panel to the existing sample login prefab to be used with WordPress Serials
– Added native support for WordPress Serials meaning:
– new settings will appear in the login prefab if WordPress Serials is installed which
1. Validates whether ornot a product is registered
2. Fetches the registered serial if it exists
3. Determines if a serial is required to exit the login prefab or if the serial is optional
– new static properties
1. HasSerial
2. SerialNumber
3. RequireSerialForLogin
– Updated WordPress Login localisation to include support for WordPress Serials
– Added do_not_destroy_this to WPServer
– Added a prefab that contains ONLY WPServer
– Use this during bootstrap scenes to load only the server access component so that all kits will always have access to the server
even after their respective prefabs were destroyed during scene changes.
NOTE: if you use that prefab, make sure your login prefab does not have an instance of WPServer on it also
– Updated WPServer to remove duplicate instances if detected
NOTE: when in the same scene there is no guarantee which one will remain. Make sure to only have one instance at all times

v5.0.1
– Fixed missing code from the wuss_login plugin
– Added arrow keys navigation to the login sample prefab’s fields

v5
– Converted the code to use C#6
– Simplified / shortened the code in the demo scene, GUI and WULogin using C#6 syntax
– Greatly simplified the personal details tab system making it easier to customise
– Fixed a bug which prevented you from creating new games from the multisite admin dashboard screen
– Added support for up to 25 languages per game
– Now ships with localisation for English, Afrikaans, German* and Chinese*
* Special thanks to Michael Borgers for the translations
– Created the WPServerErrorException custom exception
– WPServer.cs now throws exceptions rather than using Goto statements and labels
– Contacting the server now sends data only via GET or POST, no longer duplicating the data “just in case”
– Removed data structure checks when calling the server for platforms that have been removed from Unity’s Build Settings screen
– Broke up the long and confusing CallServer function into smaller functions to clarify what each part does
– Added a ContactServer overload that takes an enum as the action. You are no longer forced to convert the enum to a string first
– Renamed the server state enum from WULServerState to WPServerState
– Added Automatic Reference Counting to WPServer
– WPServer’s state now only changes from Contacting to Done when ALL active server requests have completed
– WPServer now triggers an event upon server state changes
– Game IDs are now set by choosing the game from a drop down list. No need to manually enter the Game ID found in the dashboard any more
– Game IDs are now selected from a dropdown box which means support for manually selecting random values have been removed
– Modified the WULogin functions to use enums, not strings
– Made a number of previously public variables into private variables that cannot be changed at runtime, only set via the inspector
– Examples: the urls to your website, which url to use, the game id, meta data to fetch, the size of your Gravatar etc.
– If WordPress Money is installed:
– The names of the currencies you use are now accessed at runtime using the public CurrencyNames property
– Added a static CurrencyString( string currency_name ) function to format the currency name as used in the usermeta table
– Added a public CurrencyString( int index ) overload to call CurrencyString via the currency’s array index instead
– Added public Cash( int index ) and Cash(string currency_name) functions to fetch the current balance of specific currencies
– Changed previous readonly strings into const strings instead
– WUUGLoginGUI now derives from WUUGLoginLocalisation but your own custom GUIs can still derive directly from WULogin as always
– Added a bunch of new panels to the demo prefab
– A high scores panel. Optionally trigger the WUScoring.FetchScores if the scoring kit is installed
– A panel to show a store in or, alternatively, use this panel’s display function to load a shop scene instead
– A general purpose panel… just in case you have need for one more…
* NOTE: Localisation is not supported in optional panels. You will have to add that yourself if needed
– Removed a bunch of “using” includes in files that didn’t use them
– Force the static data to be set after login before your custom responses are called instead of potentially later that same frame
– Force the static data to be cleared on logout before calling your custom actions
– Removed the need to call InitLoginSystem in the GUI’s Start function
– Automatic fetching of your Gravatar image on login is now an optional toggle
– Prefab updated to now show a spinning graphic and “Please wait” text while busy contacting the server
– WULogin now allows you to fetch game names and their associated id’s at runtime
– WULogin now allows you to create new games on your website directly from within the Unity editor (logged in site admins only)
– Updated the demo scene
– Scans the local list of game definitions for a game called Demo Game
– If required it will fetch the list of games you created on your website
– If “Demo Game” is not found it will create the game on your website
– Fixed a bug on Multisites that prevented you from seeing the WUSS sub menus

v4
– Unity broke the WWW class in 2017.3 meaning this asset stopped working in 2017.3
– V4 replaces the old version that relied on WWW and now uses UnityWebRequest instead
– Since this means some versions of U5 will not be supported:
– I am leaving the WWW version for use by anyone NOT using 2017.3
– Anyone using 2017.3 or later will receive v4 when they download the asset
– Thus, 2017.3 is the new minimum version of Unity to use to receive updates
– The previous version has now reached it’s end of life and will still work just fine, but won’t get further updates
– v4 now includes a callback when you click on the “Return to game” button in the post login menu: onResumeGame
– Removed the IsValidEmailFormat function from WUUGLoginGUI.cs and now use the string extension function instead

v3.3.3
– FIXED: Register account email field was referencing the password reset email field to test if the field was empty

v3.3.2
– FIXED: Remember me was not working before. Replaced the bool with a property linking to the Toggle component
– UPDATE: Encapsulated the masses of public fields that never need changing. This just tidies up the inspector quite a lot

v3.3.1
– UPDATE: Added a new struct called Int2D. An int version of Vector2D
– UPDATE: Most types can convert ToString but not the other way around. I now added a FromString method to a bunch of common types
– FIX: Unity2017 seems to have introduced a breaking change to how I store and use cookies. I have updated teh cookie class to compensate
– FIX: Unity2017 changed how the WWW class’s error value works. This broke the fetching of images from Gravatar. That is now fixed

v3.3
– UPDATE: Server response is now enclosed within and braces to indicate the portion of the server response that is
the actual server response. This cuts out any preceding text and any text sent after the data and thus prevents invalid data errors
– Prevent an error when incorrectly calling ContactServer without an instance thereof existing
– Updated CML to version 3 (WordPress Login Standalone version)
– Added a warning when a web browser rejects the data you send it via a WWWForm (i.e. when using the POST method)
– Fixed a warning in settings.php about accessing the security token if it was not sent
– Updated unity_functions to remove the warnings about the deprecated functions since WordPress 4.5
– modified the flow of the WPServer.CallServer function and moved all error reporting to the end of the function

v3.2.1.2
– Fixed compatibility issue with Unity2017
– Allow for automatic fetching of player’s high score during login if the WordPress Scoring asset is imported
– Added a new static variable through which to access the player’s high score if the Scoring asset is imported: WULogin.highscore
– Added a new prefab that adds WordPress Login to it’s own Canvas instead of you having to make it a child of an existing canvas
– Added an option to WPServer to make the Canvas WPServer is on persist between scenes. Ideal use would be during a bootstrap scene

v3.2.1.1
– Fixed a bug in the wuss_login plugin where it sent back sample data for my use during development only
Please update your plugin with the included version to avoid any errors this bug causes

v3.2.1
– Fixed WordPress Money support by supporting new currency name format
– Added the option to set the size of the Gravatar that is returned
– Now store Gravatar as both Texture2D and Sprite
– Added events to notify you when the Gravatar image has been fetched
– Register to either onGravatarTextureFetched or onGravatarSpriteFetched
– Apple plans to remove all support for HTTP. This causes a warning when fetching the Gravatar
Gravatar is now fetched via HTTPS to avoid this warning and to future proof WULogin
– Updated demo scene from OnGUI to UGUI and use the Gravatar Sprite as the new button to open the PostLogin menu

v3.2
– Added support for the official WUSS virtual currency system
– Checks to see if it is installed or else support is removed
– Fetch currency balance(s) during login so you don’t have to fetch them individually afterwards
– Triggers an event if currency was received outside of the game or while the app was closed
– Added a new shortcode to show WebGL builds on your webpage
– Add gid to the shortcode to show the game’s poster as a link to load the game
– Add “autoload=true” to the shortcode to load the game without the placeholder image
– You can also specify a default placeholder graphic in the WUSS Portal to be used by all players without gid specified
– Should you not specify a default image, one will be provided for you
– Added a new ZIP file called WebGL_BUILDS_Folder. Extract this in the root of your domain and upload all your WebGL builds to there
– Alternatively, specify an alternate designated folder in the Portal where your builds will be uploaded to

v3.1.1
– WPServer now trims the provided URL to remove unwanted spaces in the URL
– (Standalone version) Encoder class trims the returned base64 string before decoding it in case of extra spaces at the end
– Updated outdated documentation
– Added catalogue and discount coupon for renderer.site

v3.1
– Added a new, optional, security field to WPServer, per game.
– If used a corresponding value must be set in WordPress
– If used it will add an MD5 field to all server calls to authenticate the origin as your game
– Introduced the WUSS Portal into the plugin. Plugin now needs to be activated where before it was optional
– All other packages that include settings will register as sub menus of wuss_login in the dashboard
– User account status (Good standing, suspended and banned) are now handled by wuss_login
– The WUSS portal includes numerous WordPress ShortCodes and widgets to display on your web pages
– Future kits will most likely introduce more but will be inside their respective packages
– A number of settings can be set on this page
– Added a new POST type to WordPress called wuss_games.
– Games are now defined in WordPress using the WordPress editor
– Defining a game this way will assign your game a Game Id.
It is highly recommended that you use this and not pick values at random any more
– Since the ShortCodes and widgets are going to increase in number over time, they will be kept up to
date on my website, rather than in the kit: http://mybadstudios.com/wordpress-systems/wuss-portal/
– Introduces a new capability to WordPress: manage_wuss.
– Only administrators are given this capability
– This capability is required to see the WUSS portal in the dashboard
– Multisites: All kits are now updated to work only at the network level.
– Please deactivate all WUSS kits on a per-site level, if any, before installing this new plugin
– This will not affect how the kits function or break any existing projects
All kits were always usable across all sites so per-site activation was unnecessary
– To generate the security table, please be sure to activate this plugin at least once after updating

*** NOTE ***
Use of the ShortCodes and widgets are entirely optional
How to use ShortCodes and widgets and how to edit CSS fall outside the scope of my support

v3.0.2
– Added the option to make the server no longer show on screen error messages at runtime
– Hid the “Attempt to auto login” boolean that was left public by mistake and caused lots of confusion as a result
– Rearranged the WPServer fields in the Inspector. Should be even easier to understand now
– Removed used classes from MBSCore (Standalone version only)
– Removed some outdated code left over from the OnGUI version

v3.0.1
– Added a font for the GUI since the built in Unity font was coming up as empty

v3.0
– Removed the StreamReader and StreamWriter functions along with System.IO from CML.cs when building for WinRT
– Removed the OnGUI Login prefab and related Skin and Textures

v2.1.1
-Fixed a bug that prevented you from sending “About me” info that contained spaces

v2.1
– Removed WULoginProfileImage script as it’s become completely redundant
– User profile image is automatically fetched if the email is fetched during login
– User profile image is now available under WULogin.user_gravatar if fetched or will be null otherwise
– Moved gravatar type seection to WULogin base class
– Added UGUI support and a new prefab to use in place of the OnGUI version (Leaving the OnGUI version as legacy)

v2.03
– Fixed a bug with the WPServer that causes issue with the WUData kit

v2.02
– Enabled custom error handling in the event of the server reporting something going wrong

v2.01
– Fixed a bug to enable Firefox support

v2.0
– This update requires that the wuss_login plugin on the website be replaced with this version
– Introduced an extra step before you can use the login kit. In Start, call InitLoginSystem as early as possible
– Replaced the meta data request CSV string field with a string array for simplicity
– Extracted the server contact routines into a generic, standalone class (WPServer) to be shared by all other WUSS kits
– Removed the functions that trigger the delegate actions and call them from the new WPServer class directly
– Also removed the website URL and online/offline checks from WULogin to WPServer.
– The WULogin prefab is updated to hold the WUServer component by default but WUServer can be placed on another object if desired
– Calling the server now requires a lot more params due to it’s generic nature. All functions updated to include them for you
– Delegate functions now receive server responses as “CML” objects, not as the generic “object” class
– This saves you the initial explicit casting before you can use it
– but also means you need to fetch the data from within the response using response[0] or response.GetFirstNodeOfType(LOGINConstant) as appropriate
– You now also get access to the entire server response, including error messages and debug info, if any
– Added two new constants: login_filepath and LOGINConstant.
– Login_filepath is for internal use only. LOGINConstant matches the return type from the server
– Added a WULActions enum that I use to call the server, instead of using the WULStates enum used for the GUI state machine
– WPServer now sends actions as strings instead of ints
– Sorted the compatibility issue that prevented the kit from working on PS Vita and Firefox browser
– It should now work with everything! Testing continues
– Moved ShowPleaseWait function into WPServer so all kits can fetch it from there instead of creating duplicate code

On the server
– Updated the WordPress plugin to make the login kit’s code more easily readable in existing and future add-on components
– Removed the pre- and post- functions as they didn’t serve any real purpose. If you need it back, please let me know.
– Now uses AJAX functions to trigger the code when appropriate instead of forcing the code to run during the SHUTDOWN action
– AJAX functions also add an extra level of protection against calling code while not logged in
– Renamed the functions in a paranoia driven attempt at website hacking prevention
– Force function name prefixes to prevent my code from being used as an exploit to run arbitrary code on your site

v1.3
– This update requires that the WUPlugin on the website be replaced with this version
– WULogin prefab now allows you to specify what fields to return upon login and also allows you to fetch any piece of info from the usermeta table.
– All the info returned during login is stored in a publicly accessible CMLData variable called fetched_info
– logged_in variable is now set automatically upon login and logout. You no longer need to do this manually in the GUI script
– WULogin now contains a Static WULogin.GameID field that other kits can use to make sure all WU kits use the same game ID
– WUServer now contains a public function to generate the WWW request. All other WU kits will use this function to contact the server
– WUServer has been updated to fix some login issues on iOS
– Fixed the bug where logging in without first logging out caused the previous login’s cookie to be used
– You are now able to test web player projects in the editor
– Updated WULProfileImage to only fetch personal info if the email was not requested during login, thereby saving one extra round trip to the server
– Now adds a WUL define to the project

v1.22
– Modified the method for fetching your gravatar image. You can use it as always or you can now pass in the type of image of
gravatar you want to show. Simply use the new WULGravatarTypes enum as the second param.
– Updated the WULProfileImage script so you can select your gravatar type from the inspector
– Added the WUServer_Instance property to WUServer in preparation for dependent kit updates

v1.21
– Modified the WUCookie script to remove the deprecated warning introduced in Unity 4.5 and thus made it more future proof

v1.2
– Added multisite installation support
– Added wulogin_pre and wulogin_post hooks for custom plugins
– Moved execution from immediately to WordPress’s ‘shutdown’ filter for improved compatability with 3rd party plugins on your website
NOTE: This update will break a previous install if installed on a multisite

v1.11
– Fixed a security issue introduced in v1.1
– Modified this file so the upload would work…

v1.1
– Now includes a new class WULProfileImg.
– After login, player’s preofile image will be available from static WULProfileImg.ProfileImage
– Updated the WordPress plugin to fix a strange bug that occurs in the WUData package

v1.0
– Initial release

  1. How do I get started?
  2. Why do I only see a blank screen after Login?
  3. What data can I fetch during login?
  4. Am I supposed to see the PostLogin screen after login?
  5. Why are the static values in WULogin empty directly after login?
  6. What does the error: “Necessary data rewind not possible” mean?
  7. Can I save data to my WordPress database if I install this kit?
  8. I have a user management plugin installed. Is this kit compatible with that?
  9. If I want to add custom behaviour or integrate this kit with other WP plugins, does this kit allow for that?
  10. How can I use the login prefab across scenes without duplicating the prefabs?
  11. Everything works fine in the editor and when I build the game. Why does the WebGL build give me errors?
  12. When I extract the zip file, why do I get loads of folders with strange names?


Q: How do I get started?
Q: Why do I only see a blank screen after Login?

The WordPress Login kit will authenticate your identity and log you in if your credentials match up. Once it’s done that, it triggers an event to tell you “You are successfully logged in”. It is now up to you to decide what you want to do now. Example: Load the next scene… How you do that is by first registering to the event and then running your own code once the event fires. This means 2 things:

  1. The login kit can be up and running in under 2 minutes and do what it’s supposed to do, but for your game to integrate with it you will need to write an extra script or function of your own
  2. You never need to edit anything in this kit to make it do custom things in your project. Just wait for the event to fire then tell your project to do whatever it is you want to happen when that happens

Example:
Create a new script and add the following:

void Start()
{
    WULogin.onLoggedIn += LoadNextLevel;
}

void LoadNextLevel(CML response)
{
    SceneManager.LoadScene("MainMenu");
}


Q: What data can I fetch during login?

In the inspector you will find a number of checkboxes that you can tick to select what fields you want to return from the WP_users table. Right below that you will find an array where you can specify any field you desire and that is basically the short answer to this question: If the field exists in usermeta then it can be fetched. Just enter it’s name in the array and immediately after successful login that information will be available to your application


Q: Am I supposed to see the PostLogin screen after login?

No. If you show the prefab while not logged in then the main login screen shows to give you the option of logging in or creating an account. If you show the prefab while you are logged in, those options are pointless. Instead, then you show the PostLogin page to give them the option to log out or to go back to playing the game. See the demo scene for an example of how to show the prefab with the PostLogin screen


Q: Why are the static values in WULogin empty directly after login?

I have attempted to fix this issue but some people still sometimes report having this issue pop up so let me explain it in case you ever encounter it. When you login the kit sends the success event to every function that is listening for it. Usually there will be at least 2 functions that respond to it. One is the one that you created to run your own code after login. The other is one of mine that takes the server’s response and stores it statically for your ease of use later. Depending on which function runs first, the static data will be available or it will not.

Just to play it safe I would recommend you use the static fields anywhere in your project EXCEPT in your login success event response function. All the data that will be stored statically are also passed to your function so simply use the data that was passed to your function rather than relying on the static data.

Example:

void AfterLogin(CML response)
{
    string nickname = response[0].String("nickname");
    string email = response[0].String("user_email");
}

Q: What does the error: “Necessary data rewind not possible” mean?

This means that the URL you are giving the WULogin plugin is not a direct link to your site and that it get redirected first. Unity’s WWW class does not support this redirection so you will need to find out where and why and how your URL is getting redirected and figure out the solution from there.

This is mostly related to how your server is setup. Many people don’t realise that www is simply a subdomain like any other subdomain and that some websites are setup to forward any link that starts with www to just / while others work the other way around. Other sites have http redirect to https while others use framed redirects to make www.mysite.com point to www.someothersite.com/users/12345/wordpress for example.

If you are getting that error then it means you need to give my plugin the URL of your website up to the folder that CONTAINS wp-content. I.e. if WordPress is installed at www.mysite.com then wp-content will be located at www.mysite.com/wp-content so you need to give my prefab the url http://www.mysite.com

One customer spent 2 days trying to get past this rewind error. I told her to remove “www.” from her URL and it worked perfectly. It turns out her site was redirecting all www traffic to /.

Another customer struggled for days to get past this error so I told him to change “http” to “https” and it worked perfectly. Turns out his server was setup to forward all http calls to https.

You need to figure out what is causing your URL to be forwarded and then use the final, forwarded url as the url in the prefab.


Q: Can I save data to my WordPress database if I install this kit?

Mostly when people ask that question they mean “any data” and the short answer is no. However, with that being said, the information that WordPress creates for all users when their account is created (username, web site url, AIM, biography etc) that info is available to you via the kit and that information can be freely modified.


Q: I have a user management plugin installed. Is this kit compatible with that?

That is a bit of a tricky one to answer since “compatible” is a very broad term. If there is any information that you need from that other plugin and that information is stored in the usermeta table then, yes, you can fetch that info back, no problem at all. If the plugin contains data that you need but which it stores in custom tables then, no, this kit does not support that right out of the box.

One customer did have this request once and it took something like 3 lines of code to fetch the data he wanted and pass that along with the login information and provide the compatibility he wanted. For further customisation a little more work will be needed but this kit is designed to be super, super easy to modify to add new features of whatever nature you require.


Q: If I want to add custom behaviour or integrate this kit with other WP plugins, does this kit allow for that?

Absolutely yes. There are a number of security precautions in place to prevent tampering with your website (I take care of that so you don’t have to worry about that) but with that said, adding new functions to the kit(s) is extremely, EXTREMELY simple and only has a few steps…

  1. Each kit has a CONST value defined within it inside of Unity. The login kit has the value “LOGIN”, for example. What you need to do is open the file named unity_functions.php and create a function that starts with the CONST value from the kit you wish to extend (but in lower case) followed by whatever name you want to call the function. After that, just add your custom code to that function. That easy.
    Example:

    function loginHalloWorld() {}
  2. Your output from the function must be sent back as a single string or else WindowsRT platforms will throw out errors. Always use only my SendNode and SendField functions to format your response as proper CML. When ready, send the base64 encoded results to Unity using the SendToUnity function. Errors can be reported using the PrintError function.

    Example:

    function loginHalloWorld()
    {
      if (!current_user_can("read"))
      {
         SendToUnity( PrintError("This user doesn't even have read authority") );
         return;
      } 
    
      global $current_user;
      $favorite_color = get_user_meta($current_user->ID, "fav_color", true);
      $response = SendNode("custom data");
      $response .= SendField("five", 5);
      $response .= SendField("favorite_color", $favorite_color);
      SendToUnity($response);
    }
  3. In Unity, duplicate one of the functions in WULogin.cs that call WPServer.ContactServer (or create one yourself. Duplicating it just saves you some typing) and for the action to perform, pass it the name of your function, minus the prefix and that is it. You have now added a custom action to the kit.
    Example:

    public void CallMyFunction(CML onSuccess, cmlData onFailed = null)
    {
    WPServer.ContactServer("HalloWorld", login_filepath, LOGINConstant, null, onSuccess, onFailed);
    }

    Done. You now have a function, complete with error handling, that you can call to trigger your custom function


Q: How can I use the login prefab across scenes without duplicating the prefabs?

WordPress Login, starting from version 5.1.1, now contains a sample project to demonstrate this along with a very detailed readme.txt that explains exactly what is going on in the sample project and why it is done the way that it is done. It also contains an alternate version for cases where the first method is not appropriate. Please see the demo folder in the asset for the detailed answer and example for this question.


Q: Everything works fine in the editor and when I build the game. Why does the WebGL build give me errors?

Unfortunately, since web browsers now enforce CORS for security and Unity themselves don’t have any idea how to setup CORS to allow you to use your WebGL builds across domains, the answer they gave me was simply to “Don’t do it”. WebGL games have the added restriction that other platforms does not have in that WebGL builds need to be uploaded to the domain that is being used in the login prefab. Any testing of the build must be done from that domain. In other words, in the editor it will work just fine but as soon as you build and then try to run the WebGL game from your local machine your web browser (not my code, not your code, not Unity, not your website…but your web browser) will simply deny your project from accessing the website.

If you look in the browser console you will see it shows an errors that plainly says something along the lines of “This code will not be run”. No matter how well you write your game, if the web browser decides what parts of your code it will run and what parts it will simply NOT run, then your project is always going to be at the mercy of your browser. So simply do what the guys from Unity told me and don’t try to run the WebGL game from any domain other than the intended target location (i.e. the domain used in the login prefab). Always upload your build first, then test it.


Q: When I extract the zip file, why do I get loads of folders with strange names?

This seems to be some sort of glitch in some archiving tools. Simply use another app to unzip the file