Jump to content


  • Content count

  • Joined

  • Last visited

  • Days Won


Michael last won the day on August 6

Michael had the most liked content!

Community Reputation

160 Excellent


About Michael

  • Rank
    Head Developer

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

7,207 profile views
  1. People with iPads do not see the menu

    could you send me your theme? feel free to PM me, as my friend can't duplicate it on the default skin.
  2. People with iPads do not see the menu

    having a friend with a mac take a look, and grab me any relevant data he might see with what is happening there. i am however not sure how to fix the IE issue, as it seems to be a problem with how IE 11 processes JS.
  3. People with iPads do not see the menu

    can you send me the link to your site? i can't reproduce this on the default theme in safari, edge doesn't seem to have any issues with it (IE 11 is almost 4 years old, it is bound to have issues considering how fast the web evolves, what it looks like it is doing, is it executing cjmenu's more effect, before the page is fully rendered, i'll see what i can do about it, but no promises).
  4. The purpose of this guy is to get you started with the babble chat service. after purchase, please go to here find your chat service purchase and click on it. it will display the license key for the chat service. now install babble inside the ACP. next go to Babble->Configuration->General, click on the "Node Settings" tab. you will find 3 fields here, the first field is Node URL, this should already be https://codingjungle.net if not, please set it to this. the second one is "License Key", enter the license key you got from above here. the finale field is "License Key Email" this is the email address of the account that purchased babble. click on save, there will be no warnings or errors if everything went thru fine. if you get an error about activating the key, please fill out a support report for babble chat service and i can further assist you there. Note: it can take up to 2 hours after activating the key, that the service is fully activated. so please give at least 2 hours of time after activation, before reporting or contacting me about connection issues. if it has been longer than 2 hours, then something is wrong.
  5. People with iPads do not see the menu

    tested it on my ipad, in landscape and portrait mode on safari, i couldn't reproduce the original issue. it might be theme/css related. i changed the way it determines if it needs to drop into more. its a little bit faster so hopefully it fixes it.
  6. People with iPads do not see the menu

    Changed Status from Work in Progress to Closed Changed Fixed In to Next Version
  7. People with iPads do not see the menu

    i only have an ipad to test on, when i test it was working on chrome but i didn't test on safari. hopefully if i've fixed it for the ipad's safari, it will also be fixed for max os x safari, as i don't own a mac.
  8. People with iPads do not see the menu

    Changed Status from Pending to Work in Progress
  9. Search bar

    Changed Status from Waiting More Information to Closed Changed Fixed In to Next Version
  10. EX1366 (Creating Rooms)

    Changed Status from Pending to Closed Changed Fixed In to Next Version
  11. EX1366 (Creating Rooms)

    it will be fixed in the next version none the less, the field was missing the "required" and the default value.
  12. EX1366 (Creating Rooms)

    Changed Status from Pending to Closed Changed Fixed In to Next Version
  13. Embed Club-Chat on an html block

    i'm assuming you mean you have this: https://invisioncommunity.com/files/file/8604-clubs-enhancements/ I have a lot going on this weekend, i'll see if i can get a copy of enhancements from adriano, and i'll start thinking of ways to do this. maybe a second widget that will only display if the club has its own room, and/or a way to "hide" the tab for it, if the widget is enabled.
  14. If you run a linux distro such as ubuntu/centos7/fedora/arch linux/etc, it is more than likely it will use systemd as the init system. if your server is running any type of panel, like cpanel or plesk, you might want to contact your host. as sometimes they have their own way of doing things. your host will be able to tell you if your server's OS uses systemd (and if they can't tell you what init system it uses, i would highly recommend it is time to find a new host ). This guide will assume you are familiar with linux command line, and the applications it uses. if you are not, do not proceed any further. you can cause serious harm to your server if you simply do not know what you are doing. I also do not provide any warranty with this guide and i do not offer any support on it. i would highly recommend contacting your host and/or hiring a system admin at this point to proceed any further. again, i can not be held responsible for any damage you may do to your server by following this guide. with that out of the way, we can now continue. Requirements: an good understand of the linux command line what init system your OS is running super user privileges ssh access (in windows this can be access via an app called putty which is a free download, in mac os x and linux, use your terminal emulator to connect via ssh). if you don't understand one or any of the above mentioned things in requirements, turn back NOW! you will need super user privileges to proceed, if you are logged in as root, you can use the commands as is, if not, you will need to prefix them with sudo or su. we will need to create a service file: touch /etc/systemd/system/babble-startup.service once the file has been created, we will need to open it in a editor, i will use nano here as vi drives me insane. nano /etc/systemd/system/babble-startup.service once it is open, copy the following content in and replace the red text with the right information: ctrl+o will save it, ctrl+x will exit out of nano. NOTE: have the port match what is in the babble.js/ACP for port. enable the service: systemctl enable babble-startup.service start the service: systemctl start babble-startup.service check the status: systemctl status babble-startup.service the init script should now be running, and if babble.js crashes or the server is restarted, it should now start the babble.js on its own. again this guide is without warranty and support and use at your own risk.
  15. Babble Self Hosted Install Guide 2.4+

    This guide is intended to help you install babble 2.4+. this guide is only applicable to the self hosted version, if you have the chat service, check this out. requirements for this guide: nodejs and npm to be installed. (forever is optional) a terminal application such as putty to be able to connect to your server via SSH. optional: text editor (such as notepad++) if you will be using SSL you will need the full paths for the location of your SSL's .key and .crt file (if you have a ca.cert file, you will need its full path too, this is not always required). this guide will assume you have a understanding of how to use a terminal application and connecting to your server via SSH. I do offer a installation service for babble (just babble and configuring the babble.js, i will not install nor configure node.js itself or do anything related to server maintenance, etc). this service is $75 for the first hour, then an additional $50 per hour after this, i will require the $75 to paid before i will begin. the installation will also need to be scheduled, please contact me via PM (Michael) if you are interested in this service and/or to schedule an installation. Notice: the installation of Nodejs/forever/npm are not covered here. nodejs and npm are requirements to install and run babble. the installation/configuration/maintenance of nodejs/npm are not covered in support for this application. these are server level software like apache/nginx/php/mysql, you will need to contact your host for assistance with these programs. in your zip file, you will find babble.tar, extract it it from the zip. Babble will install in the ACP of IPS like any other IPS application. if you have read/write restrictions, you will need to extract the contents of the babble.tar and upload them to your server via FTP or you will need to disable said restrictions to be able to install babble. after installing you will see babble in the left hand menu: Go to Configuration->General and click on the "Node Settings" Tab: fill in the Node url (this could be your servers URL without the trailing slash, a server IP, etc) it will need to be a full URL, so it will need to include https:// or http://. (note: the URL field might already be populated here with the URL and port number, if this is the case remove the port number from the URL.) fill in the port number you will wish to use. by default this is 3000. you will need to check with your host to see which ports are available. you don't need to do anything with the node private key setting, it should already be populated if not, it will populate after save. save, once saved navigate back to the Node Settings Tab. you will notice a new section has appeared. it will contain a download link for babble.js and package.json, both are required to finish the installation of babble. once you have downloaded the babble.js, and if you do not require SSL to be configured, skip to step 14 if not open up babble.js in a plain text editor such as notepad++ (notepad in windows will also work, but not wordpad). once opened, please locate these two variabls in babble.js: var sslPrivateKey = ''; var sslCertificate = ''; and place the full path to the location of your SSL key and crt. they should look something like this when done: var sslPrivateKey = '/etc/ssl/certs/mysite_com.key'; var sslCertificate = '/etc/ssl/certs/mysite_com.crt'; if you have a ca.cert, you can add it to the (this is not always required as some cert companies do not issue them, auto-ssl in cpanel will not contain a ca.cert/bundle): var sslBundle = ''; now upload babble.js and package.json to your server, to any folder you like. i would suggest making this folder not accessible via the browser, and if it is, you are responsible for taking steps to making sure the contents of babble.js are not viewable and/or downloadable. connect to your server via ssh. navigate to the folder where you uploaded babble.js and package.json. once you have done that, we will need to install the node modules that babble.js uses. execute this command: npm install this could take a few minutes as it has to retrieve and install the modules that are required for babble.js to run. once they are done installing (ignore the error about babble.js not having a licenses or repo field). once they have been installed, we can start up babble.js. there are a few ways to do this, i suggest using forever or creating a init script for your servers OS (each OS is different, most linux distro's will use systemd, i will provide a tutorial on how to create one, but i will offer no support on it, as each linux distro has their own way of doing things and i am frankly not a sysadmin). you can install forever with this command (the following will require super user privileges, so if you are not logged into SSH with an account with super user privileges please switch accounts to install this): npm install forever -g on some versions of NPM, will throw an error about out of date or depecrated dependencies, this can be safely ignored. once it is install you can start the babble.js with the following command: forever start babble.js to restart babble.js: forever restart babble.js to stop or stop all scripts started with forever: forever stopall this is the end of this guide. if you started babble.js with forever or a init script, it will continue to run after ssh has been disconnected. if the server is restarted and you only started babble.js with forever, you will need to start it again after the server has been rebooted. if you used the init script, it will start with the server.