, sometime close to the expiry day. After some waiting time I've received the following information:- The plan with numbers after the name and without are the same plan, so it cannot be changed to the same plan.
- The renewal price is the renewal price for new purchases.
- The actual renewal price is buried deep, deep, after the wrong renewal price is mentioned several times.
Current hosting time expires 21.06, I plan to buy new (same...ish, actually it's not the same, as the support said, it'll be slightly better, albeit in a way that won't be noticeable to you in any way) hosting, probably 19.06 or 20.06, move everything there, re-point DNS to the new hosting, and if there won't be any technical differences(shouldn't be, still the same thing, just slightly higher limits) it should go through smoothly, without you ever noticing that, but remembering how many times I had to sit with the support initially, especially to make the forum's mailing go through...well it might not go through as smoothly as with the straight-up renewal, unless we'll be literally placed on the same physical machine. The positives - they now have 2-year plans (so we'll be good to go for another 2 years, once everything is configured properly) and I'll pay for those 2 years less than I'd pay to renew for 1 year of current plan (20% less in total = 60% cost reduction on a 1:1 scale), totally worth the hassle (more than likely - their support will spend more time with me, than they would on simply changing the plan to the same...ish plan
).In the worst case scenario, if support was wrong and they won't actually let me to, I'll just renew as is and we'll be moving to another hosting provider next year (I already have enough of $$$ for renewal, which was set to auto, prior to today that is, just in case I would be somewhere, where I wouldn't be able to).
I might lock the forum on old host, to prevent posting, while the DNS records will be updated, so you might see the locked forum for a few minutes (if you'll be unlucky to visit at that exact time - just try refreshing a few times).
tl;dr - to save significant cost, we will be moving to the same host under the same plan (I know it's weird) sometime between 19-21.06, just be aware of the possible connectivity issues, albeit there should not be any.
), so I'll be receiving forum-related mail all over the place, will be more difficult to keep track of things, but it kinda works. Hopefully the 3rd party mail provider will unblock server, as they have more favorable mail limits, in the mean time, if you have issues receiving account creation mail - just try again later.
so figured migrations near completion
it's not critical, but a certain combination of things can cause either 1 bug (not storing one thing properly in the database) or another bug (breaking layout by adding additional <div>) that causes visual bug after a post that contains this bug. It's all the very same issue, but I'm not that great at php (rarely web-coding these days, and even if - it's mostly asp.net) and on top of that there's a lot of regex mambo jumbo involved, technically I can fix it right now (but that will introduce security issue), so it's kinda complicated, as it is right now - I can manually fix the issue for each involved new post in the database, but obviously it's not a long-term solution. Still looking for an acceptable band-aid solution, but also considering changing underlying engine to the one that natively supports newer php, already downloaded the closest option available and will be trying porting things on there (will require quite a lot of work and not every required feature is there, so even more work, and some database structure differences, so even more work), from what I saw it looks doable and in the end should be even better, but there's no way to do it fast, documentation is bad, and it will be hard to spot all the differences, for instance default user IDs(anon, admin, etc.) are different (won't be difficult to fix in database, but to spot all of the instances in the code...), and I wanted to finally push for the Launcher's update, always out of time, always