Website/App - Development & Support -- 2

Current base open source coding is running off of: OS: Ubuntu Server x64 bits - may switch to CentOS 7 ... not sure. WHM/CPanel support PHP any of 7.3 or > MYSQL 5.x APACHE 2.x MOD_REWRITE PHP Function cURL PHP GD Library PHP ZIP Extension PHP settings allow_url_fopen enabled JSON Support XML Support Looking for regular support on a weekly basis, as well be able to develop widgets and components for the site. Needs to be very reasonable as this is a start up project with long term potential if the work and support is great. Show me some work examples ... and would like to see some ideas ... look forward to your proprosals. Weekly retainer and one-off project support/development In order to do an audition, of sorts, I am looking to have someone correct the code that is in a component widget. The widget does not work properly. Instead of posting an advert, it just posts the code as text instead. =============================================================================== How to write a simple component for Ossn Basics Every OSSN component is located in a subdirectory of the /components folder and contains a PHP script called ossn_com.php. The name of your subdirectory will be your component name, so choose it carefully! It should be unique but readable, so that site administrators don't accidentally overwrite it with another component, but they can also understand at a glance what your component does. Example: components/new_component/ [login to view URL] The [login to view URL] file is the control hub of any component. Create [login to view URL] file, example : components/new_component/[login to view URL] Initialization We recommend that you use the following skeleton code in your [login to view URL] file: function my_new_component(){ pages, actions, menus } ossn_register_callback('ossn', 'init', 'my_new_component'); Languages To register languages in your component create a directory /locale in your component folder. The language file name must be like [login to view URL] example components/new_component/locale/[login to view URL] for English translation The language code is ISO 639-1 standard language code. Use following code in language file: $en = array( 'hello:world' => 'Hello World!', ); ossn_register_languages('en', $en); [login to view URL] Create [login to view URL] in components/new_component/ the code should look like : <?xml version="1.0" encoding="UTF-8"?> <component xmlns="[login to view URL]"> <name>This is my componennt</name> <id>new_component</id> <author>Author Name</author> <description>Description of my component.</description> <license>License name</license> <author_url>[login to view URL]</author_url> <license_url>License URL</license_url> <version>Version of component</version> <requires> <type>ossn_version</type> <version>4.0</version> </requires> </component> Here the id is the exact path where components files resides, 'new_component' is the correct path, so the component directory appear as /components/[ID]/[login to view URL] Component ID/directory convention The directory must not contain any special characters Blank spaces are not allowed Pack Create a zip archive of the directory of your component. Make sure that on opening your archive it will appears as new_component/[login to view URL] By using the Component installer you can upload your component to the server and make it part of your Ossn installation after clicking "Enable" in the Components section of your admin panel. Changes After installation you can also change component files manually using ftp See the Hello World component [login to view URL] ============================================================================= This is from the open source code developer. Best Regards, Ben