Nervodx

Nice and clean, like it.

Admin CP > Options > Messages Change Maximum Message Length I hope that helps you. Have a happy Christmas and a good new year as well. ~Nerv

If Burning Board had more support behind it (and the default theme wasn't so ugly), it might be a decent alternative to IPB or xF.

I believe One.com changed this deal. It used to be 1 year free, then at one point it was 3 months free, and now it is a regular monthly plan. Really cheap prices at this current time: However, each of the plans come with a free domain for 1 year. Decent deal. Cheers! While getting a free domain is not a great idea if you are aiming to look professional, it is secure depending on the domain registrar and host. My apologies, I wasn't aware of this.

To be perfectly honest, I'm tired of hearing about how you hate IPB 4. If you hate it, don't use it, please don't keep commenting on everything saying how its unstable, buggy, etc. Most people are well aware of your opinion on IPB 4. Thank you and please do not take this the wrong way.

http://www.serveria.com http://www.katzglobal.com http://vpsgonewild.com http://www.offshoreracks.com http://www.internoc24.com http://webcare360.com Those are the best ones I can find. Based on their ToS, they are completely, 100% anonymous.

thank you but arent those on-shore? so if i hosted a nulled ipb would i have a higher chance of getting my site taken down? That is quite true, I didn't even think about that. I'll do some research and get back to you.

GoDaddyHostGatorBlueHostArvixeDreamHostSiteGroundNetworkSolutionsHostMonsterAll of those are some popular hosts I can think of.

Looks sick as well, mind PMing me the .svg file?

You should implement a session timeout of your own. Both options mentioned by others (session.gc_maxlifetime and session.cookie_lifetime) are not reliable. I'll explain the reasons for that. First: session.gc_maxlifetime session.gc_maxlifetime specifies the number of seconds after which data will be seen as 'garbage' and cleaned up. Garbage collection occurs during session start. But the garbage collector is only started with a probability of session.gc_probability divided by session.gc_divisor. And using the default values for those options (1 and 100 respectively), the chance is only at 1%. Well, you could simply adjust these values so that the garbage collector is started more often. But when the garbage collector is started, it will check the validity for every registered session. And that is cost-intensive. Furthermore, when using PHP's default session.save_handler files, the session data is stored in files in a path specified in session.save_path. With that session handler, the age of the session data is calculated on the file's last modification date and not the last access date: Note: If you are using the default file-based session handler, your filesystem must keep track of access times (atime). Windows FAT does not so you will have to come up with another way to handle garbage collecting your session if you are stuck with a FAT filesystem or any other filesystem where atime tracking is not available. Since PHP 4.2.3 it has used mtime (modified date) instead of atime. So, you won't have problems with filesystems where atime tracking is not available. So it additionally might occur that a session data file is deleted while the session itself is still considered as valid because the session data was not updated recently. And second: session.cookie_lifetime session.cookie_lifetime specifies the lifetime of the cookie in seconds which is sent to the browser. […] Yes, that's right. This only affects the cookie lifetime and the session itself may still be valid. But it's the server's task to invalidate a session, not the client. So this doesn't help anything. In fact, having session.cookie_lifetime set to 0 would make the session’s cookie a real session cookie that is only valid until the browser is closed. Conclusion / best solution: The best solution is to implement a session timeout of your own. Use a simple time stamp that denotes the time of the last activity (i.e. request) and update it with every request: if (isset($_SESSION['LAST_ACTIVITY']) && (time() - $_SESSION['LAST_ACTIVITY'] > 1800)) { // last request was more than 30 minutes ago session_unset(); // unset $_SESSION variable for the run-time session_destroy(); // destroy session data in storage } $_SESSION['LAST_ACTIVITY'] = time(); // update last activity time stampUpdating the session data with every request also changes the session file's modification date so that the session is not removed by the garbage collector prematurely. You can also use an additional time stamp to regenerate the session ID periodically to avoid attacks on sessions like session fixation: if (!isset($_SESSION['CREATED'])) { $_SESSION['CREATED'] = time(); } else if (time() - $_SESSION['CREATED'] > 1800) { // session started more than 30 minutes ago session_regenerate_id(true); // change session ID for the current session and invalidate old session ID $_SESSION['CREATED'] = time(); // update creation time }Notes: session.gc_maxlifetime should be at least equal to the lifetime of this custom expiration handler (1800 in this example);if you want to expire the session after 30 minutes of activity instead of after 30 minutes since start, you'll also need to use setcookie with an expire of time()+60*30 to keep the session cookie active.

Really?

PS Connect provides a simple solution for any application to to implement single sign-on (SSO) with other IPS Connect compatible applications. In an IPS Connect network, there will be one "master" application and any number of "slave" applications. The IPS Community Suite (versions 3.4 and above), can serve as either a master or a slave in an IPS Connect network. This article will show you how to connect two IPS Community Suite installations using IPS Connect. Before you set up, you will need to decide which installation will be the master, and which will be the slave. Generally speaking, when setting up an IPS Connect network, the "new" installation (which does not have any existing user data) should be the slave. If you are connecting two installations which both have existing user data, it doesn't matter which is the master and which is the slave. Important Information about Single Sign-On In order for Single Sign-On to work properly, the slave application(s) need to read cookies set by the master application. Since cookies cannot be read across domains, this means that your slave application needs to be on the same domain or a subdomain of the domain that the master application is on. For example, your master application might be mysite.com, and the slave application might be something.mysite.com. It will not work if the master application is on mysite.com and the slave application is on somethingelse.com. Obtaining the URL and Key from the Master Once you have decided which will be the master, you will need to obtain two pieces of information from it - the IPS Connect URL, and the IPS Connect Key. This information can be obtained from Admin CP --> System --> Log In Management. Setting up the slave To set up your IPS Connect network, you simply need to input this information into the Admin CP on your slave installation. To do this: Go to Admin CP --> System --> Log In Management on your slave application. You will see a module called "IPS Connect" - click the pencil icon to edit it, and toggle the "Log In Enabled" setting to "Yes". Now click the icon next to the pencil icon for "IPS Connect", which looks like a cog - copy and paste the IPS Connect URL and Key which you obtained from your master application and. If your slave application already has member data, you want to make IPS Connect the primary log in module, and use "IPB Internal" as a fallback. To do this, simply drag and drop "IPS Connect" above "IPB Internal". If your slave application does not already have member data, you can disable the "IPB Internal" method completely - this is the recommended set up if possible in your circumstances. To do this, simply disable the "IPB Internal" method in the same way that you enabled the "IPS Connect" method. That's for IPB 3, should be similar in 4.

Looks great, thanks! I might be able to trace it in Illustrator now that I have the outline.

If you could share that information that would be lovely; I'm sure it could benefit someone else.

You could use a simple code lile: <!--Embed this in your HTML or PHP web page--> <script> alert("I am an alert box!"); </script>OR Use this plugin: http://www.jqueryscript.net/lightbox/Responsive-Accessible-jQuery-Modal-Plugin-Popup-Overlay.html Demo: http://www.jqueryscript.net/demo/Responsive-Accessible-jQuery-Modal-Plugin-Popup-Overlay/ You could also include a link with something like this: <a href="javascript:window.external.addFavorite('http://www.website.com','Website Title');"> Click here to add the homepage to your favourites!</a>You can customize to your liking.

I'd like some feedback on the verb-age and how well its written, any grammatical mistakes, missing rules, etc.

myBB isn't too bad, they have decent themes and plugins.

Thank you, let me know what happends. Love the way it has been made. Thank you :) I worked very hard on that. Sad that its broken but I'm working on a fix. I might just write a plugin for it instead.

It appears something broke in 4.0.12+ because I can't get it to work after I upgrade. I will try and work a fix.

You'll have to create it manually. You can contact me on Skype @ Nervodx if you need additional support.

Looks quite lovely if you like dark themes. Personally, I don't care for dark themes but if I did that would be quite nice.

Additional release notes:

The menu manager is lovely. Not too much a fan of the secondary bar...is there a way to disable it?