GoldFish CMS [Arcturus Morningstar, Laravel, Bootstrap4]

[cammy]

Hate the design but love the layout. I just really dislike old habbo... This is great though!

 

[ashe]

Nice to see Laravel being used, here are some minor tips.

Use migrations, they'll come in very handy later down the line. Setup seeders for default static data and then just migrate off your migrations.

You seem to be conditionally checking

if (Request::isMethod('post'))

a lot, there's a better way. Bind the route to the POST method, and the controllers method won't ever get hit on GET, PATCH, DELETE, etc.

Models, you seem to be declaring a protected

$tableName

for models that you don't have to. Laravel is smart enough to recognize the table name by the class name. As long as the class name is camel case with the parts of the table name, don't worry about giving a table name. I tend to never give one unless it fails or I know its going to fail.

Not sure if you have a good reason, but why are you declaring API routes in the web file? In case you didn't know, It has its own file, along with a lot of the confirmation ( prefix, middleware ) set up for you by Laravel out of the box.

One last thing, if I took a guess I would say you copy and paste your models and controllers. Start using

php artisan make:controller / make:model

and you won't copy over so much junk data.

All the best!

 

[PotatoJFlamingo]

the housekeeping reminds me of phpretro, this looks good.
and maybe you'd want to

add images like how habbo did on their site next to navigator

You must be registered for see images attach

 

[Laynester]

Okay, Ive been dead for weeks, i picked this back up last night, heres a list of things ive done overnight

Spoiler: List

• findretros integration
• public room creator
• public room list
• public room editor
• public room category creator
• public room category editor
• RCON Helper
• RCON Page
• Voucher codes
• fixed exploits
• recoded housekeeping navigation, each link now has its own permission
• user look up list
• badge giver
• client settings (vars/swfdir..)
• emu settings (ports/ips)
• fixed chatlogs in user lookup
• ban list
• ban adder (rcon and normal)

This is near completion of my housekeeping list, just a few more things needing to be done, then i shall work on another theme or two. then it will be ready for release.

Post automatically merged: Jul 10, 2019

Nice to see Laravel being used, here are some minor tips.

Use migrations, they'll come in very handy later down the line. Setup seeders for default static data and then just migrate off your migrations.

You seem to be conditionally checking

if (Request::isMethod('post'))

a lot, there's a better way. Bind the route to the POST method, and the controllers method won't ever get hit on GET, PATCH, DELETE, etc.

Models, you seem to be declaring a protected

$tableName

for models that you don't have to. Laravel is smart enough to recognize the table name by the class name. As long as the class name is camel case with the parts of the table name, don't worry about giving a table name. I tend to never give one unless it fails or I know its going to fail.

Not sure if you have a good reason, but why are you declaring API routes in the web file? In case you didn't know, It has its own file, along with a lot of the confirmation ( prefix, middleware ) set up for you by Laravel out of the box.

One last thing, if I took a guess I would say you copy and paste your models and controllers. Start using

php artisan make:controller / make:model

and you won't copy over so much junk data.

All the best!

Tbh i have no idea how to use the API, its why i created a route in the web file, for the controllers, its easier for me to duplicate existing files, most files that i duplicate, require the same files so no junk data is in files (i hope)

Post automatically merged: Jul 15, 2019

You must be registered for see images attach

Goldfish is nearing v1 release, ive just completed the setup screen. includes create an account, changing cms settings and setting your client config, and most of all, creating the tables required for goldfish to work.

The only part the setup cannot do, is run composer, (install laravel) and it cannot change your ENV settings, that will be done manually by editing the .env file

 

[mxtt]

love it

 

[Laynester]

New theme: Legacy
Now that goldfish is nearing release, i decided to create a fresh new theme along with the original, this new theme is called Legacy, because its made to look like the original habbo website in 2007.

You must be registered for see images attach

index - credits to not hablush because their index was a rip of IlluminaCMS

You must be registered for see images attach

 

[mxtt]

Great work Layne keep it up <3

 

[Laynester]

You must be registered for see links

GoldFish is finally ready for production

 

[cammy]

The design has really grown on me, I love this CMS! I honestly wouldn't use anything else. I expect many people to be using this.

 

[Zombie]

Liking this Layne nice release mate

 

[Laynester]

Since the launch of GoldFish 1.0.0 ive fixed a few things,

• legacy css
• goldfish css
• goldfish disconnection page
• legacy disconnection page
• legacy banned page
• housekeeping chatlog error
• housekeeping user view error
• added housekeeping fuserights configuration
• fixed installatin sql not including the findretros account name
• created a self updater
• fixed photos page pagination error
• fixed the language on the badges page in HK
• fixed the news editor, adding a duplicate /images/news onto the image url
• fixed housekeeping tabs using wrong FuseRight helper format.
• changed the socket_open to fsock
• fixed the legacy housekeeping button, showing for every rank
• added logout button to legacy theme
• fixed installation using the wrong logo

 

[leenster]

I saw a nice development of Goldfish today, wondering if Layne is going to post a teaser screenie on here....

 

[Laynester]

Goldfish Legacy Theme will be soon getting Customizable Profiles with stickers, notes, and widgets
preview gif:

You must be registered for see links

You must be registered for see images attach

Credits to HoloCMS for the catalogue base, included most stickers, modified to GoldFish's database structure, And Quackster's hotel ClassicHabbo for having the classic Homes for me to mimic for goldfish.

if voted for, this will be ported to GoldFish default theme

thanks
i believe this is the first public cms to get functioning homes since 2010? correct me if im wrong.

 

[LeChris]

Goldfish Legacy Theme will be soon getting Customizable Profiles with stickers, notes, and widgets
preview gif:

You must be registered for see links

You must be registered for see images attach

Credits to HoloCMS for the catalogue base, included most stickers, modified to GoldFish's database structure, And Quackster's hotel ClassicHabbo for having the classic Homes for me to mimic for goldfish.

if voted for, this will be ported to GoldFish default theme

thanks
i believe this is the first public cms to get functioning homes since 2010? correct me if im wrong.

Jonty had an uber edit with working homes, Wesley had one with working homes as well. This was 2012+ish.

It's the first custom CMS to have functioning homes, even more impressive if you were able to redo the JS from scratch! The original homes code could be cut down heavily if it was redone with CSS3 and ESNext.

Love your updates!

 

[rrodo]

Could you explain to me in more detail why in xampp I am not going? install the compost and everything but still not going, how would the commands be but for xmapp? for this cms

 

[Laynester]

You must be registered for see links

after many months, goldfish development has continued,

bug fixes include:
online friends box fixed,
login POST URL fixed,
updater check URL changed,
login logs fixed

 

[Daltron]

Wow, Daddy Layne is doing something! Amazing! Haha keep it up bub.

 

[Swayn]

You must be registered for see images attach

 

[LeChris]

Yum, exploits.

That is the debug screen when on a local environment. If you update your APP_ENV when in production, it will show a generic 500 page instead.

The data shown in there also isn't exploitable. It just shows you the error and the call stack with said error. Cookies are your own and can be viewed in inspect element regardless.

The only potentially 'harmful' data would be the env dump at the bottom. But as I said above, this is only for local environments.

 

[GayChilin]

Now the real question is; is this still being worked on?