CB Package Builder..

About not intuitive.. for example, I do not understand how I create different versions of the same plugin ? I have the version in the plugin manifest file in my zip, but do I not enter it in the package builder ?? In short - how do I create an updated version of my plugin ?

Versions are based off file structures. It has automatic parsing for them. So for example I have the below files.

com_mycomponent_1.0.0.zip
com_mycomponent_2.0.0.zip
com_mycomponent_3.0.0.zip

I put these files in for example /images/mycomponent (this isn't ideal, ideally you should keep these outside of webroot). Now in CB Package Builder I just need to configure "Download" parameter to the following.

images/mycomponent/com_mycomponent_*.zip

That's it. Now when you add a new versioned zip file it will automatically detect it and automatically parse its version out when you run the release URL. This "Parsing URL" can be found in CB Package Builder > Parameters > Downloads. I recommend running it with CRON or as part of your build process, but you can run it manually as well if you want.

CB Package Builder is designed to work with more advanced workflows. So it's designed to work with deployment systems. For example you could setup Github to push a new build to your component folder above and run the release URL. This automates the entire process of releasing a new version. This is how we use it here at Joomlapolis, but with Gitlabs.

With that said you can use traditional upload files manually pipeline though and that's what the backend Files page as well as the upload input are for when editing a package, but it's a lot more efficient to setup a pipeline for your releases.

This may seam unintuitive at first, but that's primarily because its moved away from the traditional "upload files 1 by 1 manually" approach in traditional download managers. So there's a bit of upfront complexity here.

I see CBSubs Package Builder nowhere installed !? I only have CB Package Builder

Strange, it may not have installed for whatever reason. It appears included in the CB Package Builder in my tests. Please try redownloading and installed CB Package Builder again.

Also - if I add id=1 for specific extension then I get: 401 Unauthorized

Your URL should be as follows for example then.

index.php?option=com_comprofiler&view=pluginclass&plugin=cbpackagebuilder&action=versions&func=joomla&id=1&format=raw

Be sure you've enabled the Joomla version checker support in CB Package Builder > Parameters > Versions > Checker by setting "Joomla Checker" to "Enable". A lot of features are default disabled to avoid unwanted access.

Ok - now the CBsubs plugin is there after reinstall.

Now I ran into another problem: "Failed to save File because: File failed to move! From: /tmp/phpn3J2eP. To: /files/plg_signicatageverify_1.0.1.zip." - I cannot upload the file to a folder outside my Joomla root ?

-

Did you maybe have an answer to my last question ?
Now I ran into another problem: "Failed to save File because: File failed to move! From: /tmp/phpn3J2eP. To: /files/plg_signicatageverify_1.0.1.zip." - I cannot upload the file to a folder outside my Joomla root ?

Regarding Danish: I need to translate the package builder into Danish - how to do that ? is there a language plugin ?

Now I ran into another problem: "Failed to save File because: File failed to move! From: /tmp/phpn3J2eP. To: /files/plg_signicatageverify_1.0.1.zip." - I cannot upload the file to a folder outside my Joomla root ?

Backend file management won't work if the files are outside of Joomla root without adjusting your server permissions. Not a Joomla or PKB configuration issue here that's just how servers work for security purposes.

Regarding Danish: I need to translate the package builder into Danish - how to do that ? is there a language plugin ?

You'll need to use language overrides as shown below to translate it if it's not translated in the Danish CB language plugin.

www.joomlapolis.com/blog/kyle/18701-language-overrides-have-arrived

Backend file management won't work if the files are outside of Joomla root without adjusting your server permissions. Not a Joomla or PKB configuration issue here that's just how servers work for security purposes.

Ok, so what would be the best approach to secure the files so that they cannot be directly downloaded ? Say if I place the files in [Joomla root]\downloads