SocialEngine PHP comes with a Package Manager that allows you to easily install your plugins straight from your SocialEngine admin panel. Packages are a group of files that can be modules, plugins, widgets, themes, or even language packs. Through this Package Manager, you will be able to install new packages without ever having to worry about which files go where. To install a new package, please follow the steps below. If you are looking to upgrade your plugins, please refer to the Performing Upgrades article.
If you are installing SocialEngine plugins, log in to the client area ( ) and download any plugins you have purchased from the client area. If you are installing a third-party package, please ensure that the file you've been provided has the extension "tar".
This error is one commonly encountered while installing and updating plugins. One way around this problem is to upload the file directly to SocialEngine using an FTP client. Log into your website over FTP and locate the "/temporary/package/archives/" directory in your SocialEngine path. Upload the tar file to this directory, and set the permissions of the file to 777. Then, proceed to the Manage > Packages & Plugins page. SocialEngine should be able to detect the file and extract its contents, allowing you to proceed with the rest of the installation.
This plugin provides robust, secure JSON REST API for SocialEngine. REST API provides a standardised programmatic interface between your SocialEngine based website and outside applications, thus enabling all types of integrations with external applications and development environments. With this plugin, your website's SocialEngine installation can also be used as a backend for native mobile apps.
Supported Modules / Plugins: This API directly supports all SocialEngine core features, all SocialEngine official plugins, and selected SocialApps.tech plugins. [See "Supported Modules" tab]
3rd-Party Plugins' API: A big plus point of this API system is that it can easily be extended to other 3rd-party modules / plugins by following 5 well defined steps in the administration of this plugin.
OAuth: API uses the popular OAuth open standard for authorization for client as well as user authorization. Every user is assigned a unique, client-specific OAuth Token for identification.
API Consumer Key and Consumer Secret: Every API Client is assigned a unique Consumer Key and a unique Consumer Secret. All API requests from a client should be signed with their respective credentials.
From small pages & integrations to large applications, this API opens up truly exciting possibilities for your SocialEngine based website. It allows you to authorize applications and services to securely connect to your website and use your content in new ways and offer new functionality:
This API directly supports all SocialEngine core features, all SocialEngine official plugins, and selected SocialApps.tech plugins. We're developing APIs for more SocialApps.tech plugins and will be releasing them in subsequent upgrades. A big plus point of this API system is that it can easily be extended to other 3rd-party modules / plugins by following 5 well defined steps outlined the administration of this plugin.
SocialEngine 4 includes a Package Manager that allows you to easily install your plugins straight from your SocialEngine admin panel. Packages are a group of files that can be modules, plugins, widgets, themes, or even language packs. Through the Package Manager, you will be able to install new packages without ever having to worry about which files go where. To install a new package, please follow the steps below. If you are looking to upgrade your plugins, please refer to the Performing Upgrades article.
The SDK, or Software Development Kit, helps SocialEngine developers by building skeleton packages and allowing them to package existing ones for distribution. You can also refer to sdk.html in the download for installation instructions. For a technical overview of SocialEngine and a sample plugin, refer to our Technical Overview article.
"Create a Package" will create a skeleton package for you, with the proper file system structure and manifest files. You can either install this using the Package Manager or extract it to your SocialEngine installation to start working on it.
"Build Package" will scan your system for packages that can be installed and distributed. You can select a package, and the SDK will re-build the package manifest and condense it into a TAR archive, which will show up under "Manage Package Files".
If you would like to view more information about the package before attempting to re-build the package, you can click on the "More info" link next to the package for more details such as where the package is currently located and its description.
You can remove packages from this page by carrying out the same process as Combining Packages but instead of clicking "Combine" you would click on "Delete" to delete all the packages you have selected at one time.
If you are currently running a Social Engine version 3 site and would like to upgrade to version 4 (you can then upgrade to version 5 or 6), or have a phpFox or Ning site, there are some import tools built into the SocialEngine software to help assist you with the move.
SocialEngine 3 Import: transfer your data from a SocialEngine 3 installation to a new SocialEngine 4 installation. For instructions on migrating from Social Engine 3 to Social Engine 4, please see our article on SocialEngine 3 Migration to SocialEngine 4. This will bring up the import instructions page.
Ning Import: Transfer your data from a Ning Export to a new SocialEngine 4 installation. For instructions on performing a Ning Import, please see our article on the Ning Archive Importer.
phpFox Import: Transfer your data from a phpFox site to a new SocialEngine 4 installation. For instructions on performing a phpFox Import, please see our article on the phpFox Importer.
Search for Modified Files - Lists files that have been modified since installation. You can view a side-by-side diff of the files if you upload the original package. You have the options to upload package to diff and to flush diff cache.
SocialEngine has made my dream come true! I have my own network! The SocialEngine software is the one and only that I recommend, 100%. Now SocialEngine Solutions has complemented the full solution with their awesome plugins and themes! I also recommend them 100%.
SocialEngine is definitely THE BEST social network platform available on the market!!! It has all the features needed to run a network and its easy to use both for users and admins. One of the best things I like about it is that I can install plugins and themes by myself with just a few clicks without the need for cpanel login etc.
It's extremely impressive how quickly you can get an online community up and running with SocialEngine. I've used Ning in the past, and so far SocialEngine is winning hands down. Looking to the future, the fact that is customisable is a major plus too.
The SE platform has been an excellent way to get from concept to production quickly. The support team has really improved and this time around I could see that the support team really does strive to get answers and provides the level of support needed to resolve and move on. Very happy and I hope they just keep getting better and better.
I'm working on modifying a copy of social engine so that the sign up process includes an initial survey. I've already got a view, drawn my form however I'm not sure where the logic is processed. I know there are methods inside the corresponding controller but I'd like to save the data once the entire of the sign up process has finished.
Just for future reference I've added a blog post that I've created about this subject. It essentially boils down to creating new plugins/views/forms and editing the database in the engine4_user_signup table.
Each plugin saves the data to the session on submit. Once the user finishes going thru the steps, the session should now contain all valid data. A transaction is then created, and all data is saved to the database. Thats basically how it works.
Of course the plugins can get a bit complicated if you are creating one. I created one myself and it took me a few days. Even then I didnt 100% understand the process, but I believe Ive got it down pretty good now.
You might want to add an extra step in the signup process. For this you need to create a new signup plugin. Take a look at this table- engine4_user_signup, you can see the plugin classes listed here. The classes are located in this folder- \application\modules\User\Plugin\Signup, you have to create a new one here. If you go through these classes you'll probably have an idea how to do what you are looking to do.
Exactly 16 years, 4 months and 23 days ago, I arrived in Japan. I was working as a software engineer in the financial industry. Amazed by the variety of scenes and landscapes, I started to photograph Japan as much as I can (check my instagram), and created various sites. Naturally, I created my websites using WordPress.
As a developer, I was blown away by the sheer number of plugins needed to create a great website. But not only that, I was disappointed by the poor quality of the code and the lack of optimization. It felt like an uphill battle to get the results I wanted.
Meow Apps was created by Jordy Meow, a software engineer and photographer based in Tokyo. So many solutions are available for WordPress today, but of uneven quality, often oversized and not well-supported. Meow Apps aims for perfection by providing tools that will change your WordPress life for the best.
The configuration of individual modules depend on its function. The configuration of an Active Directory instead of the LDAP authentication module requires connection information and details about where to search for users. In contrast, the configuration of the HOTP module for OTP authentication requires data about the password length and the mail server or SMS gateway to send the password during authentication.
b1e95dc632