Member Since: 8/7/2015
Posts: 10,837
|
Quote:
Originally posted by Athens
Sorry about the wait. The forum runs smoothly on the local installation I've been building on, but it's putting up errors on the beta server. It looks like it's related to a new method we're using to make layout changes, so we'll be reverting to a stable albeit less efficient method for launch. There's 0 difference for you guys in the end.
Reverting to the old method may take a few days, but we'll be up this weekend at the latest. I have some good ideas on how we'll compensate the extra days of wait, but that's something we'll work on detailing after the beta returns.
Some more details for those interested
Often times upgrading the IPB software (e.g 4.1.2 to 4.1.4) involves updated html files. By default, IPB will not touch html files that have been modified by the admin, so when you upgrade, you may end up with files that get updated and others that don't. This can lead to errors and break a forum's layout if all files aren't sharing the same version, so the next step for the admin is to rebuild the whole theme on the latest version of the forum and that can be a painfully slow process the more the html is customized.
For this reason, most forums will either use a theme they bought from a professional who will make those updates and release them periodically or they just style their forum's css and call it a day (That's also why many forums that use the same software look similar - they're being practical, not lazy). ATRL has a lot of html edits; possibly more than any other forum out there currently. Instead of editing the html directly, we made a plugin that makes those changes to the html without actually modifying any files and only while the plugin is active. When we need to update the software, all the files get updated because we haven't modified them.
That's the plan, but unfortunately it's a system that's not yet ready for prime time. Because it works on my local install, I'm not sure if it's a problem in the code or just something with the software or with the server configuration. We'll work it out later, but for now we'll do it the old way to make sure we can still hit our main deadline. Both methods provide the same experience to the end user, but as I've mentioned before, it's just a very slow and tedious process that we probably won't want to take on every time there's a new update.
|
KING 
|
|
|
|