wolstech

You can't. You need to move to Tommy, or develop for 2.7 on Ricky. From the wiki (http://wiki.helionet.org/Flask):

It would be mods, admins, and you two. I should be able to set it up sometime later tonight.

You can always let a mod or admin know and we can post it in the News forum for you (who can create new topics in that forum is restricted because it broadcasts on our social media). You can also put the warning on the front page of the wiki a few days ahead of time.

If you guys want your own hidden board for wiki dev stuff, I can do that for you so we don't need to cram all of this in one topic, especially considering this will be an ongoing project. Not sure about the other 2. I'd probably just rename the existing forum to "Wiki Access Requests and Questions" as one board to keep it simple. We've never really had enough content for a separate "Wiki questions/other" forum to be warranted.

This one sounds like a CF issue honestly. Krydos can verify there's nothing going on here, but we've had a few people whose sites just would not work when they tried to run CF with the website. We'll see what Krydos says, but you may end up needing to contact CloudFlare and ask the question there.

In that case, it's possible something else caused it. The limit is supposed to be 50 emails per day. Usually being able to send 1 email is a sign of throttling due to overuse, which shouldn't be the case here. Our root admin Krydos can check and see why you aren't able to send mail. Have you checked the result of mail()? It should return true if it's sending/thinks it sent mail. Also I'm assuming you've tried sending to a different recipient address and checked the spam bin (email from us has been known to erroneously flag as spam)?

You probably got throttled for sending too many emails. There's a few reasons for this happening, the most common being sending too many emails. Escalating.

The URLS are just inline links to the images, so this is probably the cause. We came from an ancient version where it was enabled by default. It might be easiest to just turn this setting back on...it hasn't been an issue for the past 5 years since we restrict editing to approved users anyway.

I assume you mean "need to be embedded"...some of those can't be embedded/stored as part of the wiki since they're actually PHP scripts that output image data (or might be image files regularly regenerated by a PHP script vs. generated on-demand). Is there a reason we can't just link to an external image like we can now? Can the domain restriction be removed entirely so we can use third party images without re-hosting them?

It's possible (or at least in the past it was) to get suspended for "High MySQL Load" just like it is for "High Server Load" (CPU/RAM). Abuse generally weeds itself out quite quickly on the production servers (unlike Johnny, who just bogs down from the abuse and takes forever to find resources for suspending it...)

https://www.helionet.org/index/topic/30202-increase-maximum-php-file-size-71/ I'm sure he can increase that...it's 8MB on Johnny, so I don't see why Tommy couldn't be increased as well.

Looking good Any idea why I can't get external images to embed? I'm trying to fix https://wiki-dev.bailey.cf/Template:Server_load The pictures are also broken on https://wiki-dev.bailey.cf/Installing_a_Let%27s_Encrypt_SSL_Certificate

@Krydos: His username is pipe0482, on Tommy.

It was Sunday yesterday, so it's fairly common for none of us to be around. Krydos usually checks this forum either around mid-day or late at night (EDT) from past experience, so he should look at this today sometime.

Unblocked.

Name servers are changed at your registrar, not here. You need to set them to ns1.heliohost.org and ns2.heliohost.org to use our services.

The DNS settings are correct and I see a website at that domain now that appears to work.

This support request is being escalated to our root admin.

Unblocked. In the future, if you use https://heliohost.org/login/ you won't get blocked for incorrect passwords.

This support request is being escalated to our root admin.

This support request is being escalated to our root admin.

It failed then. Thats pretty common on Johnny... Escalating so that can be corrected.

Did you add that domain to your account as an alias or addon domain? Domains always show queued if they're not attached to an account.

Both of those aren't free if you want certain (somewhat common) functionality or need more than the very basics. I've never seen a form processor that was completely free honestly, short of writing it myself. A large part of the reason WP is so popular in the first place is because a lot of the functionality of all these integration services that try to upsell you, is available in WP as extensions for free.

WordPress is one of if not the worst written, bug and vulnerability-filled CMS software out there. Abject junk. Seriously, just about any other CMS or website generator out there is going to do a better job. All of us here highly recommend you just replace your WP install instead of trying to fix it. You won't have to deal with these errors anymore, the site will be faster, and it will be more secure too. That'd be quite useful. A lot of the WP sites I've seen on here are indeed in this category. Rarely updated static content. Definitely no need for the bloat and risks of WP. The ones that don't are usually either crude stores built with a WP plugin (a proper ecommerce system would be better suited for that), or content/news aggregation sites of some form. Can Hugo do basic interactive elements like a contact form? I haven't had time to look into it more...