-
New Commercial Services Section
We have now opened a commercial services section here on the forum for registered users. If you have a Fabrik project that you wish to have someone work on for you, post it under Help Wanted. If you are an application developer and wish to earn some money helping others, post your details under Fabrik Application Developers.
Both of these are unmoderated. It will be up to both parties to work out the details and come to an agreement.
-
Joomla 5.1
For running J!5.1 you must https://fabrikar.com/forums/index.php?wiki/update-from-github/ or include the new file manually https://fabrikar.com/forums/index.php?threads/joomla-5-1-and-fabrik-cannot-find-files-error.54473/post-285151 See also Announcements
Github update deleted prefilters
- Thread starter rackem
- Start date
- Status
Fortunately I have a relatively recent local backup that I can copy/paste my old settings.
Confirmed, see https://github.com/Fabrik/fabrik/issues/377
cheesegrits
Support Gopher
Yeah, sorry about that. A rather unfortunate side effect of a commit from a few days ago that was intended to fix another issue with filtering.
Thanks to everyone for reporting this, glad we got it fixed quick enough so it didn't do any major damage.
Just FYI, I'm looking at ways we can slightly modify our github routine, so Rob and I commit to a "bleeding edge" repo, rather than the master, so our trusty core of volunteer guineapigs can test out our changes, before they get pushed over to the main "master" that everyone updates from.
This would greatly reduce the risk of unintended damage to "normal" users from changes that Rob or I haven't sufficiently tested. Which is hard to do for us in isolation, as Fabrik is such a huge project, and automated unit testing is almost impossible to implement.
-- hugh
Thanks to everyone for reporting this, glad we got it fixed quick enough so it didn't do any major damage.
Just FYI, I'm looking at ways we can slightly modify our github routine, so Rob and I commit to a "bleeding edge" repo, rather than the master, so our trusty core of volunteer guineapigs can test out our changes, before they get pushed over to the main "master" that everyone updates from.
This would greatly reduce the risk of unintended damage to "normal" users from changes that Rob or I haven't sufficiently tested. Which is hard to do for us in isolation, as Fabrik is such a huge project, and automated unit testing is almost impossible to implement.
-- hugh
cheesegrits
Support Gopher
Yeah, sorry about that. A rather unfortunate side effect of a commit from a few days ago that was intended to fix another issue with filtering.
Thanks to everyone for reporting this, glad we got it fixed quick enough so it didn't do any major damage.
Just FYI, I'm looking at ways we can slightly modify our github routine, so Rob and I commit to a "bleeding edge" repo, rather than the master, so our trusty core of volunteer guineapigs can test out our changes, before they get pushed over to the main "master" that everyone updates from.
This would greatly reduce the risk of unintended damage to "normal" users from changes that Rob or I haven't sufficiently tested. Which is hard to do for us in isolation, as Fabrik is such a huge project, and automated unit testing is almost impossible to implement.
-- hugh
Thanks to everyone for reporting this, glad we got it fixed quick enough so it didn't do any major damage.
Just FYI, I'm looking at ways we can slightly modify our github routine, so Rob and I commit to a "bleeding edge" repo, rather than the master, so our trusty core of volunteer guineapigs can test out our changes, before they get pushed over to the main "master" that everyone updates from.
This would greatly reduce the risk of unintended damage to "normal" users from changes that Rob or I haven't sufficiently tested. Which is hard to do for us in isolation, as Fabrik is such a huge project, and automated unit testing is almost impossible to implement.
-- hugh
- Status