Wordpress Demo site PluginWorldpress Demo Page Plugin
Creating a WordPress Demo Site
Demo site creation with WordPress Multisite is a fast way to enable your customers to try out your design or plugin in a realistic enviroment...! Configuring a demo site for WordPress plug-ins or topics can be as easy as deploying WordPress and providing a demo for all. As an alternative, you can also use a plugin like Ninja Demo, but we have chosen not to tackle the issue this way.
WordPress MultiSite lets you change, erase or share your demo without having to interact with other demo account by just letting your user build a new demo site. Substitute the WordPress login with a single "Create Demo" pushbutton (custom plugin): In order to see the final version, just visit the Profile Builder demo page.
You will receive a new WordPress demo page on which you can make all changes as an admin. It is also possible to unsubscribe and test the Profile Builder functions as a subscription or as a non-registered member. Multi-site networking is included with every WordPress installation. The only thing you have to do is set up and run WordPress as usual and then activate Multi-site.
In order to activate the Network Setup option, you must first set up MultiSite in the wp-config. php-Datei. Then you can generate a network from your WordPress installation. For more information, see the Codex Network Documentation. In addition to the plugin, we have also included all available add-ons for our Profiles builder demo (as the user cannot set up their own plugin even though they are an administrator on the demo pages), as well as other plug-ins that make Profiles builders such as WooCommerceor members work with.
With the exception of Profile Builder, these plug-ins are not enabled by default, but WordPress demo site visitors can select which functions they want to use in a real-world world. WordPress MultiSite's standard login function is a little too "secure" for our demo site. Whilst the above makes complete sense in the general WordPress Multisite contexts, it is simply not good enough for a WordPress demo page.
Therefore we want to substitute it all with a plain "Create Demo "utton. So if you don't want to go through all the effort of building a customized plugin and copying the source file, just dowload the plugin by pressing the down arrow and installing it location-wide. Then you can insert the link [cds_register] into your primary networking site.
This plugin consists of two parts: Here we rely on the following key functions: The functions we use are and WordPress MultiSite function set i. e. and W. MathCaptcha. php' ;'init','cds_start_session' ; ; ; ; // Generate the short code that outputs the buttons to Create Demo. They will be forwarded in 3 seconds ' ; ; 'demo' . ; " " .
" "The new demo accounted could not be created." ;, ;, ;'@mailinator.com' ;'demo' ;,, ;'The new demo accounted could not be made. You will be forwarded in 5 seconds. ' ;'Demo' ;,,,,'public' ;'The new demo wasn't able to be made.
"The following" "cbs_register" "cbs_register" "submit" "cbs_register" "submit" "Create Demo" "cbs_action" "hidden" "cbs_action" "cbs_action" "cbs_demo" ; ; ; ; ; ; Was wir hier tun, ist : When everything is working (the capcha is right and we could build both the users and the domain), forward the users to the new demo site.
We construct a non-cce here that is basing on the new username and contains the actual UIX times in minute. We do this by using the backend cookie that uses the username we send as a $_GET query parameters as a parameters. uid=2134 in the URI, so we rely on the non-core set-up after a successfull users and demo site build.
If more than 1 second has elapsed since the first generation of the shortkey, we do not log on to the server. Given that none es are one of a kind, it is virtually unthinkable for anyone else to log onto the site by chance. The remainder of the coding is made up of the feature that creates the casual username/domain name and a feature that finds the actual URI so we can reroute it so that the logon cookies take effect and the users are signed in.
There are actually less than 160 rows of overall coding, plus WordPress commentaries and plugin header. Now we have a very beautiful set-up where WordPress demo pages can be created directly by the user without having to type usernames/passwords/e-mails etc. Update: We also suggest you take a look at the Multisite Cloner plugin from Wordpress.org, which works and is under active development.
This is all great, but it would be even bigger if we had a page style that is used every times a new demo site is made. We used the replicator plugin from Ron Renneck. Hasn' been upgraded for quite some now, but it still works well for what we need, like duplicating the preferences, pages, postings, widgets und menu to each new WordPress demo page that has been made.
Not a free plugin, but we already had a licence for it from another site and I knew that it would work well for our Profiles Builders demo site. As an alternative to this plugin, you can set up a light weight pattern in the WordPress MultiSite settings: It' not perfect, but depends on the demo site you create, it might work well.
Eventually we can now fade out some menus like the My Sites administration toolbar shortcut, the toolkit or the comments pages in the user interface if they are not needed for your WordPress demo page. We used the free menuplugin for this purpose. Setting up a WordPress demo page isn't really difficult, but if you want to do it right, a few things have to happen:
There are also a few things that we didn't do, but want to include later, such as: creating a widget for dashboards where we can see certain information like the user name and its e-mail, the demo passphrase, information about using the new WordPress demo page, etc. This is all possible with the Ninja demo plugin, so if you have a busy timetable, you should be honest.
Otherwise, if you want to get a little involved with WordPress MultiSite and see this as a way to get something new, the REAL option is not so difficult. It' s been almost a year since we launched demo pages for our plug-ins, and it seems they served their time.
At such a high utilization level, it is unavoidable to solve the problem of automated website deletion. Otherwise, over the course of the years you will be confronted with an immense number of websites that could run up against the memory limitations of your host. When 24 Stunden have elapsed since the website was created. Provided administrator is not a member of the site.
It ensures that websites built by superadministrators, such as the parent log or any other subpages you want to keep running, are protected from being removed.