The original task is from 2016 when we just overtook the old codebase.
Since then the site has been had a major update and should now adapt much
better due to React based frontend.

Great!
Thanks for bringing that up to attention.

Should be renamed, someone please confirm if it is correct now and then
close the ticket.

Ah okay, now it makes sense :)

Ah yes, I take care of that, thanks for reminding!

Should be all done/switched. Parent category is not possible if there
subcategories, so added those to a new one.

Okay :)
Renaming "Kdenlive FX" to "Kdenlive Lumas" then.
If there are any issues within 24-48 hours, we can simply switch back.
You need people also to switch categories for certain items then, or is
"Lumas" correct for all items in category 185?

Added, could take up to 24h to propagate fully through.

Hi Julius,

Great. Closing then.

Updating is different than uploading. Sorry, but I misunderstood the title.
First step for uploading would be to securely connect (via kaccounts or
webaccount), then we could gain experience with rating and comments as
first step to see how it goes.

Can this be closed? For new tasks, it's best to open new ticket.

If you have any idea how we could implement this in a good way for Alkimia
(and other), we would like to get this in.

If you still need to distinguish some older Python 2 files, we can also add
a dropdown selectbox via an attribute, so people can, but dont need to pick
2 or 3 or both to signal compatibility per File.

Okay, now I renamed both Python 3 to simply Python.
Can you just doublecheck and confirm I should remove the Python (2) ones
then altogether?

So Python 2 stays Python 2 and Python 3 should be simply Python then?

I think its the resolution of that cut-out? like can you just scroll down in your browser and then see Python 3,... and the rest?

They show up under store.kde.org fine?

Will rename then also the Example one to Python accordingly?
I did add all of the categories inc. Scilab, R, ... so I wonder why they
are missing. Will investigate.

Update:
All Documentation categories have now been added and should show up within
24 hours or earlier.

Best would be imo to define/override the "no image" case on the ghns side
to a) reduce loading times from server and b) also be flexible whenever a
new icon style is wanted on the Plasma side.

Great. I will add the new categories then, assuming it all goes well.

At least over here i only see one time 651 now.

Is it still 3 entries? It seems a hard to find issue, so hopefully some
change we did may already solved it on the api end.

We are looking into this, yes.

Great! There is a slight buffer for store.kde.org if i am correct, but it
shows up already by now over here :)

Also let me know if the other Documentation categories should be added in the same way, or if you like to change anything.

That you see the category 3xtimes is weird, I think @leinir should maybe have an idea as it is from within KDE.

Restructured it in the suggested way:
https://store.kde.org/browse/cat/649/order/latest/

Is it correct, that only one of the existing category so far shows a
product?

Category id is 644, added here:

Category is now added (id: 638), should be publicly visible after someone adds any product, if not after 48 hours, please contact again:

Direct Link:
https://store.kde.org/browse/cat/624/order/latest/

Hi phils,
what is panon?
Any suggestion what Category name and items those would be if panon had its own category for it?

Hello zachus,

We will have a look and hopefully can say whats up. If nothing big, we try
to fix it before monday.

It can take the maximum of 24 hours before a newly added product shows up.
If it does not, we need to investigate. Note that the cache of a running
kde session is not updated client-side until the next login iirc.

I added the new category now here:
https://store.kde.org/browse/cat/606/order/latest/

We certainly can add a new category = API Documentation QCH Files.
Linking files are possible via "Add url", simply pointing to a file as endpoint.
I'm not sure what needs to be done client-side, so Dan can likely help there.
I just need to know what the category name should be and when to add it.

I'd agree that flatness taken too far becomes unattractive/dull also for me
personally. When comparing Breeze and latest Iphone icons though, I think
our set looks awesomeness, it is so good that i have yet to find something
else that i would stick to and not go back to Breeze after relative short
time, elemantary included. Since its all subjective, I am not sure if
changing some of Breeze would make things better, but leave everyone
unsatisfied in the end, as current Gwenview, K3B fit imho so good with the
rest that starting to change them would rather require a new style
altogether than mixing or going halfway back to something Oxygen-like?
Maybe look forward for this then for Plasma 6?

Personally I find the Breeze icons dope, especially Kontact, Yakuake, K3b and Ark.

Looks wonderful indeed! :)

Will add them to ocs apiserver.
Note that for now those two categories may contain demo imports, which
might change or removed again in the near future, so its mainly for testing
at this point, as we havent also made those categories visible on the
frontend.

The link in store.kde.org is here:
https://store.kde.org/browse/cat/589/

store.falkon.org seems to be operational now.

What if two identical names?

After talking with Dan Leinir, here is another approach:

• Every file can be attached a tag, in this case "plasma-4" and "plasma-5" (or both or none).
• These tags can be set by every developer for their product files themselves
• If Dan does implement looking for the "plasma-5" tag actively set, the themes can stay in the category they are now, but only plasma-5 tagged themes will appear from Plasma 5.16 onwards, which from the end result should be like starting with an empty category.

I agree and therefore looking into a way to achieve the exact same outcome,
but easier implementation and no drawbacks for older versions. Just need to
test to see if its feasable.

In T8126#184221, @kossebau wrote:

Or would you need to demonstrate yourself as well first that the store system works for this purpose of moving things between categories? :P

Well, we could do many approaches, i think it is important to find something that is the least disturbing, hence having split the categories might not be the best approach.
If we are fine introducing some new method in Plasma 5.16 and keep it backwards compatible for Plasma 5 and also KDE SC 4.x users, then I would rather seek to implement such a method.
It would make use of the tagging system and probably also be best to demonstrate to see and play around with it without actually breaking things or making them irreversible.

That category demonstrates how the not so radicale way would go by moving
one oldest theme to it. This theme should now in 24 hours no longer be
searchable or found via ghns. Imo the other mire radicale way of creating a
total new category would mean much more effort and potentially errors than
this non-destructive, reversible path forward.

The filtering can be done by a db update moving themes older than a certain
date into the new Plasma 4 Theme folder.

The other way would make it impossible for users not on the latest plasma
5.16 then to find moved themes though?
Imo this could be more important than kde4 users not finding their old
themes anymore, but one way or the other it goes when splitting.

Wouldnt be the reverse much safer and could start right away?
That is simply add a category "Plasma 4 Themes" and move old themes there,
so the current category can stay as is, but gets potentially better and
better themes?

Any update on this?

That I dont know. The chosen url just needs to point to the same IP adress
than store.kde.org.

An example where this would be useful is that a search only brings back relevant results, e.g.:
https://store.kde.org/s/Falkon/search/projectSearchText/book

Just as info, it is also possible for Falkon to be viewed as a subsection (similar to a subreddit):
https://store.kde.org/s/Falkon/

I added those to ocs:// install protocol, does it work from Falkon side via "Install"?

So adding Falkon Extensions could need a dropdown to choose either Qml or
Python?

Sure. How exactly is an extension or theme "installed"? Like if you would
simply download a Falkon theme/extension, what would you manually need to
do to have them enabled in Falkon?

Hi David,

Good ideas, will be clearer for sure.

We are working on it as I write this.

If there is any such "bug url" for store.kde.org on kde infra that we can
point users to, like bugzilla, we can add this information in the sidebar.
Will check.

We can easily add a new category and make that compatible to replace the
current one. We could also sort all plasma themes newer as a certain update
date into that or leave it empty to totally cold start. I just need to get
an official confirmation whatever is decided to proceed.

Are there older plasma themes from kde4 times that do work in Plasma 5?
Or are all themes before a certain date broken?

Your welcome! If you like we can also remove the "Dock" from "Latte Dock"
main category name.

Done (Variant 2), should be updated in next 24 hours.

For the other category, I have the info that it was internally labelled "Skrooge report template", so this is what was searched and matched some time in the past.
Since then we never changed that, but if nowadays the exact DISPLAY name is used, we can certainly revise that.
Please double-check if internally the client looks for "Skrooge Report Templates" or "Skrooge report template".

We can try the following: We move the items over to the new category and
set new category name to legacy name in the database and ocs-api server.
Then you do not need to have double entries and we can remove old Scrooge
group, since content in new group Alkimia has set legacy name to Scrooge it
can serve both old client and new one from the new category.

So Skrooge is renamed to Alkimia?
Because there is also a second category for Skrooge?

What is the exact name of the category that Alkimia is looking for?

Added Alkimia Online Quotes category:
https://store.kde.org/browse/cat/560

Hi Ralf,

Due to protection against attack vectors like automated spam and upload
bots, we do not support upload feature over ghns.

I think it might be needed to wait 24 hours to replicate on the api-server.
So if by tomorrow there still is nothing, please ping again.

I matched all categories to the older naming scheme. Should take a bit
before it becomes visible, though you can see its already used by the
Octave worksheet uploaded.
If anything else needs adjustements, just ping here again.

Exactly that.

Upload from within programs is not possible due to abuse reasons.

should be set now

Ronald will have a look on monday, as it is vacation day in Germany.
Meanwhile is there any chance for using a modern alternative like RSS and discontinue the legacy RDF?
Just checking some options.

Thanks. Item should have been switched.
If you notice anything at odds, please report here.

Hi Michail,
what is your user id on opendesktop.org?

I suggest to wait for the actual switch of the main site and see what Haris has done with the WP, as he consolidated a lot of what has been given and then start to change or finetune that and NOT all change it at once again.
Just my 2 cents.

This is actively being worked on as we speak:
store.kde.org database already added an attribute to exclude any item from being shown via GHNS (called ghns_excluded), and we are now looking into making it available via OCS-API so those items are then easily "filterable".

Would further be also likely more consistent with other toggles in the future, like imagined on mobile "wifi crossed out=disabled", etc.

@ronaldv : Is this done?

Yes, I can confirm subcategories are now searchable. I assume it is due to
that we allow multiple categories now for the same type and are able to
handle them.

What are wallpaper plugins?
Do they need a new seperate GHNS button, in the wallpaper dialog?
Added a new empty category just in case.

Should be fixed now from the backend side, try and see again if it works.