Ikiliki

In the URL of your server 🙂

Imgur supports https. I don't feel like proxying external images for that lock icon 😛

Update: Forum is not on HTTPS. Some pages however contain Mixed Content errors, because e.g. your imgur-hosted signature is served over HTTP. @Arix

Ah, that indeed used to redirect. Let me re-redirect it, thanks for letting me know.

.

Hi everyone, As of today, RuneLocus has a brand new official Discord server. The Discord server we used in the past was owned and managed by Lusfr_. It however, with all respect for his hard work and spent time, was not being managed the way an official RuneLocus Discord should be managed. Apparently @Ziek` and I were not the only ones with that opinion, as we've been receiving confronting messages regarding the Discord on a daily basis. Hereby I'm inviting you all to the new RuneLocus Discord server: https://discord.gg/6rK7dcr The old Discord server is, as mentioned above, owned by Lusfr_. The server will be renamed and unlinked from the RuneLocus community. It is up to Lusfr_ to decide what he'll do with the server. I however, recommend you to move over to our new Discord server. That is also the new place where you'll find all RuneLocus staff members. A few notes: RSPS Owners will have to re-submit a request for the rights to post in #rsps-advertisements We'll be using the forum ranks as Discord ranks. If you have a special rank on the forum, you may request the same rank on Discord. Use #role-requests for that. As of today, no special ranks or rights will be sold. This includes the special rights to use @everyone in your advertisements. If you've purchased special ranks or rights from Lusfr_ recently, please discuss the matter with Lusfr_ directly.

The forum is not self-hosted, but is hosted by IPS. I'd have to ask them to enable it for us. Most likely won't be an issue, but I'd rather do it after my vacation and preferably also after high season. I don't want the site to end up with possible Mixed Content errors while I'm unavailable :-)

As stated, theme still needs some fixing. The theme was still in development. Due to some issues with our previous host, we were forced to upgrade to the newest version of the CMS within 14 days or we'd go offline. But the previous theme didn't support the newest version at all. That required us to release the theme in a rush, which is why certain things still aren't finished. The tools menu is the best example of what still needs to be done 🙂

Exactly my thoughts

Glad to hear! Thanks for reporting the error!

I don't really understand what you just said lol. The issue usually fixes itself after waiting for a bit / the page to load 100%. That is why I really can't find what is going wrong

Not for a custom, matching theme. We've had that before, and that really caused headache each time the forum software had serious updates. A dark theme however is a good idea that I've heard before. If you have theme suggestions in mind, feel free to send me the link 🙂

Hahaha, that is what I'm still looking into. Still haven't figured out what is causing that.

Hi @bobsmit, What is your server? I'll have a look. Nothing has changed to the callback system. The only change to the callback system is the fact that it is now sending callbacks from another server/IP address. If your server's callback URL is IP-restricted to the previous IP address, than it needs replacing. If you don't have IP restriction (I'd recommend you not to do so), please send me your server name / toplist link. I can then check if our server is able to load your callback URL, or not. In almost all cases where servers don't receive callbacks from us, the server somehow blocks our connections or has an unknown kind of SSL certificate installed. Please send the server and I'll have a look

Hi @Genesis, I'm extremely sorry, I completely missed this post somehow! As for the bug you are reporting, that has been fixed yesterday. We did not only re-design the website, but we also updated some software. The new version of content management system had some trouble with extremely long callback variables in URL's. All servers that sent a callback variable with more than 100 characters resulted into the E10 error. The URL you sent has a callback variable of 148 chars ("dT5Y3nt2mz__AAtIADxGhFzs7BDwWBSx45R8b1JsEjWgypMPRvdrGKCwreEjd9uXoo4rGST_yG7P8dxsSfMJhChoue_aaaz2cdMAPRaaazSJrYL0JYahOAorUVfRBKYEgo4Lz219oFoSWaaazxCE"), and therefore error'ed. The issue has been fixed yesterday after someone else messaged me. Can you let me know if it's working for you too now?