Quantcast
Channel: Joomla! Forum - community, help and support
Viewing all articles
Browse latest Browse all 1885

Extensions for Joomla! 3.x • Re: Upgrading from unpublished Virtual Domains extension to forked version on GitHub

$
0
0
Your best bet would be to ask the developers how they intend to maintain these forks and whether their forks are stable for production use. From a quick look at the changes I can see that tkempf's fork maintains compatibility with J3 whereas caincoulton's fork is compatible with J4+ only. So that's at least one major difference.
Maybe "PHP 7.1 and later" means effectively PHP 7.x?
For the most part, yes. PHP generally does not introduce breaking changes in minor versions, although there are some exceptions for minor behavioral changes. It can also introduce deprecation messages but that shouldn't be an issue because error display should be disabled in production anyways.
Would "supports PHP8" also mean it works with older versions of PHP, including PHP 7.x?
You'd have to review the code or ask the developers. If they're not using any PHP 8+ syntax or features, it should work on PHP 7 too. This seems to be the case here for now.
Probably I can download something from GitHub. What? How?
Do I need to build it?
First you'll need to either checkout the repository or download the source code directly from Github. The rest depends on which fork you use. tkempf's fork already has a Composer file with Phing dependency. So you can run these commands to build the package:

Code:

composer installvendor/bin/phing build
coincoulton's fork does not have a Composer file so you have to install Phing manually. Either globally on your PC or locally in the repository/source directory. See Phing documentation https://www.phing.info/.
Once you build the package you can then install it on your Joomla site.

Statistics: Posted by SharkyKZ — Sat Feb 10, 2024 10:53 am



Viewing all articles
Browse latest Browse all 1885

Trending Articles





<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>