I'm pleased to share we have just released ITFlow version 25.01 as a stable release!

The full changelog is available here, but some notable changes include:

Breaking:

  • Cron/CLI scripts have been moved to the /scripts subfolder — update your cron configurations!

  • The client portal has been moved from /portal to /client:

    • Links in previous emails will be broken.

    • The Azure Entra ID SSO Redirect URI needs to be updated to /client.

    • You may need to update other links (e.g., website, support page).

  • Guest links have been moved from / to /guest. Previous links will be broken.

General:

  • Added support for saving cards in Stripe for automatic invoice payments.

  • Page titles now display detailed information.

  • Tidied modals & includes into sub directories.

  • Implemented domain history tracking.

  • Added Asset Interface Linking/Connections to show what interface is connected to which interface port of another asset.

  • Added tooltips to main navigation badge counts to clarify what is being counted.

  • Reduced max records per page from 500 to 100 to prevent performance issues.

  • Updated several plugins:

    • stripe-php from 10.5.0 to 16.4.0

    • Inputmask from 5.0.8 to 5.0.9

    • DataTables from 2.1.8 to 2.2.1

    • pdfmake from 0.2.8 to 0.2.18

    • php-mime-mail-parser to 9.0.1

    • TinyMCE from 7.5.1 to 7.6.1

  • Disabled HTML Purifier caching.

  • Fixed an issue where the ticket edit modal didn't show multi-client or no-client projects.

  • Fixed a TinyMCE license issue.

    wrongecho Breaking:

    Cron/CLI scripts have been moved to the /scripts subfolder — update your cron configurations!
    The client portal has been moved from /portal to /client:
    Links in previous emails will be broken.

    You may need to update other links (e.g., website, support page).
    Guest links have been moved from / to /guest. Previous links will be broken.

    to make these old links work again add these 2 rewrite rules to you apache vHost file

    1. RewriteRule ^/portal(/.*)?$ /client$1 [R=301,L]
    2. RewriteRule ^/guest_view_(item|invoice|quote|ticket)\.php$ /guest/guest_view_$1.php [R=301,L]

    And then restart apache sudo systemctl restart apache2

        Bigbug In hindsight it would've been great to include these in the htaccess. At least we know for next time.

          Whilst we did add most of the Stripe saved card/auto-pay, I apparently forgot to add the Stripe option to the recurring modal. And by forgot, I mean I had written the code but forgot to incude the files in my commit… I didn't pick this up in testing because I was manually editing the database; we were in the process of moving all the modals to their own directory and I didn't want to cause merge conflicts.

          itflow-org/itflow1155 - Will fix this in develop

          -

          I also fixed the portal URL when a login key is set: itflow-org/itflow20a862f

            I personally would like to switch back to the daily "micro" updates vs the new monthly push.

            But now you are talking preferences. To take the Debian approach, monthly is stable, weekly is testing, daily is Sid (at times I hate that kid…).

            This way as issues are found, and random features introduced, they can be addressed more quickly.

            But, that is a decision left to the developers.

              JosephWithCOR To take the Debian approach, monthly is stable,

              Here in ITFlow it turned out to be not so stable…
              So doing a micro update just to fix those few things that should've been in 25.01 would be great!

                  Bigbug Potentially, but we've already removed the old cron setup from develop. Ideally, I wanted to give people a little more notice to change things.

                  JosephWithCOR The separate develop branch and release cycles are part of a wider initiative involving roadmapping, tracking bugs and features to ensure they get done, and overall stability. The develop branch has proven itself to be a great place to properly work on & test bigger features without impacting production installs. Maybe monthly is too long, but I think we'll find a middle-ground eventually.

                  Personally, I want ITFlow to be as rock solid as other apps people are using in production. The whole commit & push as you go didn't really provide that (see the tens of forum posts asking why X doesn't work even though there's a big banner over the top of it that says its in development).

                  You're perfectly welcome to use the develop branch if you want: update config.php and do a git switch develop. If it breaks: you get to keep both *pieces!

                        wrongecho Stripe option to the recurring modal.

                        I was about to start a bug report thread on this, as i couldn't find it…

                            wrongecho I set up a test environment and did the switch to the develop branch, but when I try to run updates from the GUI it's just stuck and doesn't update

                              • johnny

                              • Post #13
                              • Edited

                              @Bigbug make sure to change the branch in config.php from master to develop as well

                                Bigbug Here in ITFlow it turned out to be not so stable…

                                How often does Mozilla Firefox (for instance) release an update to turn around and release a .0.1 update days later? It happens. For the most part, at least in my instance, the software has been more or less rock solid.

                                wrongecho I am just tossing out idea's. If you are moving to a monthly cadence, Great!

                                I like using the software and am happy to support it as I can.

                                    johnny unstickied the discussion .