Skip to Content Skip to Menu

Package Builder - 401 problem

  • krileon
  • krileon
  • ONLINE
  • Posts: 49549
  • Thanks: 8483
  • Karma: 1465
1 day 18 hours ago - 1 day 17 hours ago #341959 by krileon
Replied by krileon on topic Package Builder - 401 problem
Below are the only things that can cause a 401 for that endpoint.

1. Package ID does not exist in the database
2. Package is not published
3. Package is not a Joomla type
4. Package is a Joomla Plugin and is missing XML > Folder
5. Package is missing XML > Element
6. Package has no available versions (you're not using * wildcard for versioning in Package > Download)

Those are strictly the only ways the version endpoint can cause a 401. I'll be reviewing causing less 401's in a future release and just skipping over things to output an empty version XML instead in a future release, but those are still issues that should be checked and addressed. I'll see if I can have a release out shortly to implement that.

Edit: There is no logical way for me to remove these 401. They are the result of an incomplete package configuration.


Kyle (Krileon)
Community Builder Team Member
Before posting on forums: Read FAQ thoroughly + Read our Documentation + Search the forums
CB links: Documentation - Localization - CB Quickstart - CB Paid Subscriptions - Add-Ons - Forge
--
If you are a Professional, Developer, or CB Paid Subscriptions subscriber and have a support issue please always post in your respective support forums for best results!
--
If I've missed your support post with a delay of 3 days or greater and are a Professional, Developer, or CBSubs subscriber please send me a private message with your thread and will reply when possible!
--
Please note I am available Monday - Friday from 8:00 AM CST to 4:00 PM CST. I am away on weekends (Saturday and Sunday) and if I've missed your post on or before a weekend after business hours please wait for the next following business day (Monday) and will get to your issue as soon as possible, thank you.
--
My role here is to provide guidance and assistance. I cannot provide custom code for each custom requirement. Please do not inquire me about custom development.
Last edit: 1 day 17 hours ago by krileon.

Please Log in or Create an account to join the conversation.

  • rbuelund
  • rbuelund
  • ONLINE
  • Posts: 623
  • Thanks: 42
  • Karma: 4
  • Add-ons
1 day 17 hours ago - 1 day 17 hours ago #341960 by rbuelund
Replied by rbuelund on topic Package Builder - 401 problem
Hmm well - I have checked all the points:

1. Package ID does not exist in the database
- It does indeed exist in 
Code:
_comprofiler_plugin_packages
2. Package is not published
- It is
3. Package is not a Joomla type
- It is Joomla type and installs fine as so on a site. It contains a component and a module.
4. Package is a Joomla Plugin and is missing XML > Folder
5. Package is missing XML > Element
- As in 3. - it installs fine as a package on a site.
6. Package has no available versions (you're not using * wildcard for versioning in Package > Download)
- I am using *  -> pkg_smssystem_*.zip
Last edit: 1 day 17 hours ago by rbuelund.

Please Log in or Create an account to join the conversation.

  • krileon
  • krileon
  • ONLINE
  • Posts: 49549
  • Thanks: 8483
  • Karma: 1465
1 day 17 hours ago #341961 by krileon
Replied by krileon on topic Package Builder - 401 problem

- As in 3. - it installs fine as a package on a site.

It doesn't matter if it installs fine or not. Those parameters must be set for the version checker. They're exclusively used for it. Please edit your package and under the XML tab be sure you've set those parameters correctly.

It sounds like it's a Joomla package. So you should only have XML > Element to configure. This should match whatever you set the element to in your XML file. In a future release CB Package Builder will automatically extract this. Right now it does not so you need to configure that parameter for the version checker to know what the package element is.


Kyle (Krileon)
Community Builder Team Member
Before posting on forums: Read FAQ thoroughly + Read our Documentation + Search the forums
CB links: Documentation - Localization - CB Quickstart - CB Paid Subscriptions - Add-Ons - Forge
--
If you are a Professional, Developer, or CB Paid Subscriptions subscriber and have a support issue please always post in your respective support forums for best results!
--
If I've missed your support post with a delay of 3 days or greater and are a Professional, Developer, or CBSubs subscriber please send me a private message with your thread and will reply when possible!
--
Please note I am available Monday - Friday from 8:00 AM CST to 4:00 PM CST. I am away on weekends (Saturday and Sunday) and if I've missed your post on or before a weekend after business hours please wait for the next following business day (Monday) and will get to your issue as soon as possible, thank you.
--
My role here is to provide guidance and assistance. I cannot provide custom code for each custom requirement. Please do not inquire me about custom development.

Please Log in or Create an account to join the conversation.

  • rbuelund
  • rbuelund
  • ONLINE
  • Posts: 623
  • Thanks: 42
  • Karma: 4
  • Add-ons
1 day 17 hours ago - 1 day 17 hours ago #341963 by rbuelund
Replied by rbuelund on topic Package Builder - 401 problem
Sorry - but exactly which tag in the xml file for the package do you refer to ?? I have no element tag ?

Do you mean I have to add this to the package manifest file <element>smssystem</element> - if my package name is pkg_smssystem
Last edit: 1 day 17 hours ago by rbuelund.

Please Log in or Create an account to join the conversation.

  • krileon
  • krileon
  • ONLINE
  • Posts: 49549
  • Thanks: 8483
  • Karma: 1465
1 day 17 hours ago - 1 day 17 hours ago #341964 by krileon
Replied by krileon on topic Package Builder - 401 problem
For Joomla packages it's represented as "packagename" in the XML prefixed by pkg_ as per Joomla documentation. I've no idea why they went with that when all other XML's in Joomla use "element" but it certainly adds to the confusion unnecessarily. Example as follows.

Code:
<packagename>myextension</packagename>


XML > Element = pkg_myextension

Basically it will match whatever the "element" column is in _extensions for that package when installed. It's used by Joomla's update system to match extensions to check for updates.


Kyle (Krileon)
Community Builder Team Member
Before posting on forums: Read FAQ thoroughly + Read our Documentation + Search the forums
CB links: Documentation - Localization - CB Quickstart - CB Paid Subscriptions - Add-Ons - Forge
--
If you are a Professional, Developer, or CB Paid Subscriptions subscriber and have a support issue please always post in your respective support forums for best results!
--
If I've missed your support post with a delay of 3 days or greater and are a Professional, Developer, or CBSubs subscriber please send me a private message with your thread and will reply when possible!
--
Please note I am available Monday - Friday from 8:00 AM CST to 4:00 PM CST. I am away on weekends (Saturday and Sunday) and if I've missed your post on or before a weekend after business hours please wait for the next following business day (Monday) and will get to your issue as soon as possible, thank you.
--
My role here is to provide guidance and assistance. I cannot provide custom code for each custom requirement. Please do not inquire me about custom development.
Last edit: 1 day 17 hours ago by krileon. Reason: typo

Please Log in or Create an account to join the conversation.

  • rbuelund
  • rbuelund
  • ONLINE
  • Posts: 623
  • Thanks: 42
  • Karma: 4
  • Add-ons
1 day 17 hours ago #341966 by rbuelund
Replied by rbuelund on topic Package Builder - 401 problem
Ok so now i added <packagename>smssystem</packagename> to the package manifest xml, and in the Package under XML -> Element I entered: pkg_smssystem and by the way I have selected Site underneath. Still no luck!

Please Log in or Create an account to join the conversation.

Moderators: beatnantkrileon
Powered by Kunena Forum