Sat, Dec 7
Mon, Nov 25
No, you did not do anything wrong. The problem was on our side.
Sat, Nov 23
Your product should be found now.
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.
Nov 8 2019
@starbuck Thanks. Tried a first link with https://store.kde.org/p/1334948 and adapted the KNSRC file of KDevelop, worked as wanted.
(well, once I added a workaround for some strange KNewStuff behaviour on archive extraction, cmp. 39a8a51d33 ;) )
Nov 7 2019
I added the new category now here:
Thanks for the reply, sounds good.
Nov 6 2019
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.
Confirmed, thank you :) Need to do a bit of jiggery-pokery to the various consumers of the data, but it's already much more consistent now - always had a kind of "...what in the world?" feel when the numbers didn't match, and having this works well i think :) Thanks! Think we can call this one all done (if it turns out to need further work, we'd probably want to open a different ticket to track what and why for that, rather than this one)
You should get now all comments.
Great, i can work with that! :)
Well, so I'll return all comments in /comment/data in the future, even if not all of them contain a rating. You then have to ensure that the number of ratings is calculated correctly and displayed in the dialog. In your example, that would be 3 ratings/reviews for a total of 28 comments.
Hmm... In that case, if it's more like a filter, it might actually make sense to send all the comments out - how much trouble would it be to make it do so? (if it's a huge amount of work, then it's probably not really worth it, but i think it might well be good; it'd allow us to perhaps add some more interesting filtering and sorting options on the client side)
Oh, I see. With /comment/data only comments with ratings are displayed at the moment. In /content/data however the number of all comments is displayed.
I will change the number of ratings/comments in the /content/data response.
I think we have a discrepancy between the comments being sent out via this call, and the number of comments reported in the content call. As an example, see below:
Is there anything else to do from the server side?
Oct 21 2019
Oh well, yes, that is not immediately recognizable.
First, you should add a type in the backend under '/backend/browselisttype'.
Important is the name and view page. The name is not a problem - any string. The view page is the name of the view script without the extension '.phtml' which must be stored in the directory '/application/modules/default/views/scripts/explore'. After that you should be able to select the Browse-List-Type under '/backend/categories'.
I will expand the database seed so that there is always at least one browse list type available.
You could run the following SQL snippets, so you should definitely be able to create categories again.
INSERT INTO browse_list_types (browse_list_type_id,name,desc,render_page_name,is_active,deleted_at) VALUES (1,'default','Default List type is List','index-react',1,NULL);
Oct 20 2019
I'm trying to understand how the backend works, and I have a question: in localhost/backend/categories, how do I add a Browse-List-Type?
Oct 15 2019
Oct 10 2019
Yes, that's like a thorn in our side. A migration is planned for this year and urgently needed. I do not know if we can do it in time to put the system completely on another framework. But the minimum requirement is a migration to Zend 2.
@alexanderschmidt Thank you very much for this 😄 I was able to successfully run the web application on my computer.
Hello, sorry for the delay. We have prepared a repository containing the required data. It's far from being finished, but maybe you can work with it.
It is currently hosted on Github and is not public, but here is the invitation:
Still important to know, the interesting part for you is in Branch kde.
If any information is missing then please contact us at any time.
Oct 9 2019
Sep 17 2019
Sorry, but next week we will start putting together a package for developers. An empty database is one thing, but you'll need at least a few more products to see the structure of the site.
Aug 31 2019
Aug 29 2019
[spam comment removed by sysadmin]
Aug 23 2019
Looks wonderful indeed! :)
And there we go, ain't it a lovely thing ;)
Thank you very much :) i shall follow up with a screenshot when i've got it all happy :)
This also is looking great! If we could make avatarpicfound be 1 and 0 (rather than true and false), that would be super handy, as that would allow me to not have to change attica's parser, which expects something which can be converted into an integer.
OK, some person data are now public:
That is so much better, thank you :D Works an absolute treat! Witness the now much nicer looking (though of course as yet somewhat unpolished) comments display in the shiny, new KNewStuffQuick components :)
Please take a look at my changes.
Aug 21 2019
Maybe a mysqldump --no-data should be enough until you have more time to create documentation?
Aug 17 2019
Ok thanks :)