-
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
PHP 5.5
- Thread starter zebrafilm
- Start date
cheesegrits
Support Gopher
As far as we know. I'm using 5.5 on one of my test sites, although I'm still doing all my development against 5.4. Let us know if you run in to any 5.5 related issues, and we'll fix 'em. I suspect it would mostly be "developer" level issues, like deprecated warnings.
But there may be some actual warnings and notices generated, for things like using functions that return arrays as the input to other functions that expect their args passed by reference ... so traditional shortcuts for splitting up (say) comma separated strings, like array_pop(explode(",", "one,two,three")), which would return "one", will now generate a warning, and we have to turn that in to two lines, and assign the explode() to a variable first.
Anyway ... certainly nothing serious that I'm aware of. Just let us know if you see any notices/warnings, and we'll fix 'em.
-- hugh
But there may be some actual warnings and notices generated, for things like using functions that return arrays as the input to other functions that expect their args passed by reference ... so traditional shortcuts for splitting up (say) comma separated strings, like array_pop(explode(",", "one,two,three")), which would return "one", will now generate a warning, and we have to turn that in to two lines, and assign the explode() to a variable first.
Anyway ... certainly nothing serious that I'm aware of. Just let us know if you see any notices/warnings, and we'll fix 'em.
-- hugh