There is a reason Laravel supports localisation.. you doing it wrong m8
Printable View
https://laravel.com/docs/5.4/localization, I know about it @Joopie.
But this isn't a Language system. I see you're little misunderstanding what I'm doing here. The thing it's that, HabboWEB has it's own language system in .json files. I'm justing replacing "Habbo" word by {{$chocolatey['name']}}, of course this
or thisCode:echo __('messages.welcome');
Seems be so much decent. Maybe I'll switch to Localization. It's a good idea. But, I'm basically doing the same.
Also in the HabboWEB templates I'll do the same. "Habbo" for Hotel Name. Anyways, next release I'll add localization.
- - - Updated - - -
One last thing:
Localization in Laravel it's for language system. Obviously if I had the control of the thing, and we don't have Angular in HabboWEB this would be pretty amazing to put.
But see, I'm not changing the localization strings. Maybe those languages are good for Internal Texts that aren't on HabboWEB Language Files.
But for templating engine I don't think that this Is good. I mean, Chocolatey has some Blade Global Variables that makes everything easier. It's like on RevCMS. The User Model, the Settings Model.
You can access both Mail Settings, Chocolatey Settings and User Instance (if available). This is good for pro developers and newbies. They just need insert {{$user['my_user_attribute']}}. {{$chocolatey['my_setting_attribute']}}
I will change from Array to objects. Because it's more easier and pretty more decent.
I will use Localization feature for Internal texts.
I also need think on a way to make HabboWEB stuff easier to edit/patch/etc. Adding a new language isn't easy since you need add the .json schema of the language and replace all Habbo words with safe.
Obviously if you don't want you don't need change Habbo to {{$chocolatey->name}}. But you may do it.
Regards,
Claudio
Hay people, sorry about the lack of updates. Was busy irl. This week I will continue all the items of the Issues List of Chocolatey, including Facebook Auth.
See the Issues list, by clicking here: https://github.com/sant0ro/chocolatey/issues
You also can contribute or report a bug by creating an Issue.
New Release o Chocolatey, Version 2.400 Released!
Contains many improvements... And... Facebook Login Working! (for some cool guys that asked it)
Download the Release right now, from here: https://github.com/sant0ro/chocolate...ases/tag/2.400
Urgent Fixes.
(After discovering that I forgot to commit some files.)
Here is it the Alpha Release 2.405, that fixes the Register Problem (Birthdate) and the Client Problem (Variables)
Download it here: https://github.com/sant0ro/chocolate...ases/tag/2.405
Again some Urgent Fixes
Again I'm really sorry, because I'm really busy on IRL and didn't tested all the things.
As I said, I need to create Unit Test cases for Chocolatey.
New Release.: https://github.com/sant0ro/chocolate...ases/tag/2.410
The pages just refreshes constantly..
Sorry forgot to commit a change. My mind isn't the best those days.
- - - Updated - - -
4 fucking releases in one day. My mind is blowing. All because I didn't commit properly or tested things. I'm really out of time so many things to do. I'm really sorry about my poor quality of testing. Need create Unit Test Files soon as possible.
I hope this version now solves everything.
Working Release (Tested)
https://github.com/sant0ro/chocolatey/releases/tag/2.415
How can i enable de ads and put my ads in chocolatey?
@ISitckerz only Client Adverteisments works currently. We disabled the In-CMS Ads.
We think that only the In-Client Ads (Interstitial) are sufficient and sufficient annoyable for a user.
Remember, the intention of Chocolatey isn't creating money with Habbo Retro's.
You can see the ADS Documentation on our Wiki
All Adverteisement codes were removed. Obviously you can add it back by patching HabboWEB's Original Angular Templates (on scripts.js) but that's not noob friendly and I'm aware that I cannot help you here with it.
If you REALLY want ADS on your ENTIRE CMS and not only on the CLIENT. Please create an Issue and I'll help you. But understand, the CMS it's under OpenSource license.
If you start to modify the CMS code you're aware that any changes will be your responsible. Since Sulake policy it's against it.
Sorry about this big warning. But I'm keeping clear that's an nonprofit project.
An error message in the register because of the recaptcha. i did it successfully but it says, that i need to finish the recaptcha.