IanM thanks.
This nice error forbid the admin also to access to the admin backend.
An error to load flarum is showed to users.

I hope in the future Flarum can avoid extension to forbid admin access.

    Hello, I would like to request this extension to support Blog extension, because my users should need the draft extension function to save progress and prevent progress loss when writing long Blog articles.

    I discovered that in the /storage/logs folder there is a Drafts-publish.log file that contains the following content:

    Starting...
    Done.
    Starting...
    Done.
    Starting...
    Done.
    Starting...
    Done.
    Starting...
    Done.
    Starting...
    Done.
    Starting...
    Done.

    I know this is not an error

    Why do you have to do that?

    1.2.4 So far, everything is going well.
    Tks man.

    1.2.4

    • fixes issue in 1.2.3. Exporting data via blomstra/gdpr is now supported experimentally
    a month later

    IanM I imagine this can help performance in very active communities.

      2 months later

      I'm running the scheduler in kubernetes as a deployment with supercronic. The scheduler runs and I can see the below from the logs

      starting flarum scheduler via supercronic
time="2024-01-24T18:22:52-05:00" level=info msg="read crontab: /scheduler.cron"
time="2024-01-24T18:23:00-05:00" level=info msg=starting iteration=0 job.command="php /usr/share/nginx/flarum schedule:run >> /dev/null 2>&1" job.position=0 job.schedule="*/1 * * * *"
time="2024-01-24T18:23:00-05:00" level=info msg="job succeeded" iteration=0 job.command="php /usr/share/nginx/flarum schedule:run >> /dev/null 2>&1" job.position=0 job.schedule="*/1 * * * *"
time="2024-01-24T18:24:00-05:00" level=info msg=starting iteration=1 job.command="php /usr/share/nginx/flarum schedule:run >> /dev/null 2>&1" job.position=0 job.schedule="*/1 * * * *"
time="2024-01-24T18:24:00-05:00" level=info msg="job succeeded" iteration=1 job.command="php /usr/share/nginx/flarum schedule:run >> /dev/null 2>&1" job.position=0 job.schedule="*/1 * * * *"
time="2024-01-24T18:25:00-05:00" level=info msg=starting iteration=2 job.command="php /usr/share/nginx/flarum schedule:run >> /dev/null 2>&1" job.position=0 job.schedule="*/1 * * * *"
time="2024-01-24T18:25:00-05:00" level=info msg="job succeeded" iteration=2 job.command="php /usr/share/nginx/flarum schedule:run >> /dev/null 2>&1" job.position=0 job.schedule="*/1 * * * *"
time="2024-01-24T18:26:00-05:00" level=info msg=starting iteration=3 job.command="php /usr/share/nginx/flarum schedule:run >> /dev/null 2>&1" job.position=0 job.schedule="*/1 * * * *"
time="2024-01-24T18:26:00-05:00" level=info msg="job succeeded" iteration=3 job.command="php /usr/share/nginx/flarum schedule:run >> /dev/null 2>&1" job.position=0 job.schedule="*/1 * * *

      While my draft scheduled date passes in the above and the draft remains scheduled. I do have the timezone set in the container, the timestamp of the logs matches my local timezone -05:00 and date I scheduled the post for. In the database, the UTC time is stored. Perhaps something wrong with my TZ settings or something else?

      This is my first time using the scheduler, previously I just relied on the Queue driver which ran similarly in a container via supercronic. The admin panel shows the scheduler was never run, and the queue shows inactive and is also not triggering.

      https://discuss.flarum.org/d/24118-setup-the-flarum-scheduler-using-cron

      Is it important to actually change the working directory before executing the flarum schedule:run command? Thats the only difference I could really spot.

      */1 * * * * php /usr/share/nginx/flarum schedule:run >> /dev/null 2>&1

      Edit: Yes that was it! setting the working directory to where flarum is apparently is required. I know that's what the instructions show for the scheduler setup, but it looks cleaner calling the full path directly in a single command and I didn't think it'd matter 😉

      11 days later

      mix0nSPb I'm having the same problem, did you ever find a solution?

      I have a Freeflarum forum, no custom css but a custom header (tried without it too). I have the themes that were the standard settings, I use Chrome on my Mac and android and the logo is misaligned on both. On this forum the drafts logo is in the right position so it's an issue with my forum in particular. And I've noticed that the search bar also ismisaligned with Sign Up / Log In when I'm not logged in!

      Does anyone have a clue about what might cause this issue?

        11 days later

        mix0nSPb I just solved our problem by disabling Contactme, took a while to figure out lol

          a month later

          When I click on the Delete all drafts trash icon, the pop-up text continues to be visible:

            robinodds Please match the URL of your forum, possibly with some CSS you can fix this problem.

                2 months later

                Not sure if anyone else has this issue, but my draft button was a bit cattywampus (see screenshot), the below CSS fixed it for me though.

                // Draft Button Correction
    @media (min-width: 768px) {
        .Header-controls, .Header-controls>li {
            display: inline-block;
            vertical-align: top;
        }
    }
                3 months later

                1.2.11

                What's Changed

                Full Changelog: FriendsOfFlarum/drafts1.2.10 → 1.2.11

                2 months later