V2-Beta

[LifeGold]

Hi. When will be update available for download?

[WhiteCoreWebUI]

Probably next weekend although in a limited version without admin interface just for testing purposes

[LifeGold]

Sorry this took so long, because judging by the demo, the main functions of the website work. wanted to ask, how did you manage to solve the problem with registration? And in the config file there is a line where the table Avatar but now its in the database no as she nazivaetsa now?

[WhiteCoreWebUI]

i do it by manual database entrys because the option to show it from the system itself is not currently working

[greythane]

I'm intrigued by the manual db entries? If this is something that will add functionality it would be better for me to add it into the core services

[emperorstarfinder]

It is an interesting idea. Perhaps it might be better to have the webui point to the services it needs within the Core Services and eliminate the need for an addon-module?

[WhiteCoreWebUI]

i basically only save the .aa file and add the name including the image UUID to a DB table the rest is loaded as is

[WhiteCoreWebUI]

so if you save a .aa archive it would probably make sense to save the name and the image uuid without extension into a database table like this

[greythane]

ah, ok.
This would be easy to do as it would just involve saving to the db that already exists.
I think this was possible at one stage in the early Aurora code but was removed sometinme before we took over.
The .aa file and an associated image is already saved to the 'AvatarArchives' folder but for complete web access the data could be saved into the data also as a blob and associated graphic, probably a thumbnail image would be nice as well.
These could be served up when required via an API call.

If this is suitable, l'll have a look at implementation.
Btw. I have started to port across the webui procedures as standard API type calls. Early stage though.

[WhiteCoreWebUI]

@greythane Ok grey first the .aa saving is still buggy it saves at times in the bin folder, second using a blob probably only eats mysql memory and removes the "portable" option so i think it would be a better idea to just save the name and image uuid in the Database and let the WebUI fetch those also this reduces the calls the webui has to make to the services because i see heaps of calls when i open a webpage on the webui be it the "builtin" one or mine doesnt matter

[greythane]

Ok... The 'portable' option has not been fully checked out (by me) yet and is just an option that I was looking at due to me moving between development systems continuously.

Anyways... I'll re-check the saving stuff and see what is happening there.

[WhiteCoreWebUI]

@greythane okay let me know if you come up with something