Maintenance Mode

Anagastes

This version is incompatible with Flarum-v1.1.1

Loading composer repositories with package information
Updating dependencies
Lock file operations: 0 installs, 105 updates, 0 removals
  - Upgrading flarum/core (v1.0.4 => v1.1.1)

composer require datitisev/flarum-maintenance:"*"

[InvalidArgumentException]                                                                                                                                                                                                      

Could not find a matching version of package datitisev/flarum-maintenance. Check the package spelling, your version constraint and that the package is available in a stability which matches your minimum-stability (stable).

datitisev

Anagastes This message does not mean it is incompatible. This message means it cannot find the package, which would be because you haven't set up Extiverse premium exts and/or you have not subscribed to/paid for a plan.

GreXXL

Extension breaks Flarum administration dashboard with error:

mount-redraw.js:15 TypeError: Vnodes must either always have keys or never have keys!
    at e.normalizeChildren (vnode.js:21:11)
    at t.exports (hyperscript.js:93:26)
    at a (index.js:7:43)
    at n (patchMithril.js:7:33)
    at n.getMenu (Dropdown.js:138:12)
    at n.view (Dropdown.js:46:30)
    at Function.s (render.js:30:16)
    at render.js:155:45
    at render.js:160:3
    at c (render.js:66:8)

datitisev

GreXXL Should be fixed in v1.1.0 now. The extension also now requires Flarum v1.3.0 or later.

m4v3rick

Got the extension recently for our forum and it works perfect. Before it I had to do that manually with some workarounds and this saves me some time and now I also have the possibility to test something before users are back in the forum.
Thanks to @datitisev for letting me try it first.

Two things I would recommend though:

More details to the fields or maybe a description with examples (e.g. error page file path). I couldn't get that running. HTML field works perfect, but I would prefer to use the file path.
This is more a feature request: it would be great to switch the maintenance mode on with a cronjob. Is that possible? Because I want to do backups via ssh from one machine to another but automatically putting the forum to maintenance before would be great!

Thoughts: such extensions should be in the core. Also considering a transportation (eg. dev->test->prod) system between systems would be great.

m4v3rick

m4v3rick This is more a feature request: it would be great to switch the maintenance mode on with a cronjob. Is that possible? Because I want to do backups via ssh from one machine to another but automatically putting the forum to maintenance before would be great!

@datitisev - do you think that would be possible?

Boss81

Hi @datitisev

I would like to ask if I buy the package, then it is enough to install it and then it can be used, or is there anything else that needs to be done?

https://extiverse.com/extension/datitisev/flarum-maintenance

datitisev

Boss81 I believe that should be it. You'll want to probably configure the error message, and the settings that dictate how you wish the maintenance mode to act (i.e. disable site for everyone, allow for specific users if DB is functional, etc).

m4v3rick

hi @datitisev

composer update --prefer-dist --no-plugins --no-dev -a --with-all-dependencies

gives me:

Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Root composer.json requires datitisev/flarum-maintenance *, found datitisev/flarum-maintenance[1.1.0] in the lock file but not in remote repositories, make sure you avoid updating this package to keep the one from the lock file.

It used to work until May but not any longer?

I just saw that there is no more https://extiverse.com/ - maybe there is an issue with our software license for Maintenance mode?

luceos

Resolving this through Discord m4v3rick

m4v3rick

luceos

Thanks. I had to follow this guide: https://discuss.flarum.org/d/32812-the-future-of-flarum-in-2023-balancing-open-source-and-success/61

« Previous Page