3963 comments found.
Hi, thanks a lot for your answer.
Here is my concrete scenario and what I’m trying to achieve on my platform (intimiclub.fr):
From a business point of view, there are two user types:
Creators: can create posts, start streams and earn money on their profile.
Subscribers/fans: can subscribe, buy content and send messages/tips, but they should never be able to create content or start streams from their own account.
What I would like is:
Non‑verified users should not be able to create posts or streams (this is already handled by the ID‑check enforcement, as you mentioned).
Non‑verified users should also not see any “create” UI at all: no “Create post”, no “Create stream/New stream ”, no access to /my/streams in the menus. Currently they can access these pages, but the action fails because they are not verified. I would like these menus/buttons to be completely hidden in that case.
Even when a user passes the ID‑check, I do not want every verified user to automatically become a “creator”. I would like an additional layer (for example a “creator” flag/status, or any mechanism you recommend) that I, as the admin, can control to explicitly promote a user to creator. Only these “creator” users should see the create post/stream menus.
From what you wrote, I understand you already have an internal ticket about hiding “create stream/posts” from menus for non‑verified users. This is exactly what I need as a first step, but ideally I also need the extra “creator” layer described above.
My questions are:
Is there already a configuration option, flag or recommended pattern in the current version to distinguish “creator” vs “regular user/subscriber” on the frontend, beyond the ID‑check and Compliance settings?
If not, could you provide some guidance on where to hook this in the code (controllers, middleware, config) so that I can implement this additional permission layer cleanly on top of your existing system?
If needed, I can provide you with test accounts (one creator, one subscriber) on intimiclub.fr so you can see the difference between what I want for creators vs subscribers.
Thanks again, and looking forward to your recommendations.
Best regards,
Hi there,
Non‑verified users should not be able to create posts or streams (this is already handled by the ID‑check enforcement, as you mentioned).
Non‑verified users should also not see any “create” UI at all: no “Create post”, no “Create stream/New stream ”, no access to /my/streams in the menus. Currently they can access these pages, but the action fails because they are not verified. I would like these menus/buttons to be completely hidden in that case.
Even when a user passes the ID‑check, I do not want every verified user to automatically become a “creator”. I would like an additional layer (for example a “creator” flag/status, or any mechanism you recommend) that I, as the admin, can control to explicitly promote a user to creator. Only these “creator” users should see the create post/stream menus.
From what you wrote, I understand you already have an internal ticket about hiding “create stream/posts” from menus for non‑verified users. This is exactly what I need as a first step, but ideally I also need the extra “creator” layer described above.
Yes, your observations are correct. Our initial intention was to:
- Use ID verify as an admin approval step
- Restrict users from creating content based on it
- Leave the UI enabled, but restricted (so users can see they can become creators/sell content if they wish)
As far as I am aware, most of the fan-based sites are doing the same, I assume, to increase the conversion of creators.
But from what I understand, this is not fully compatible with the scenario where you’d like to basically have diffferent UIs for creators and regular users.
However, I imagine that if we add more granular options for hiding (for good) all content creation interfaces, for the ID checks, it would basically be what you’re asking, but still with one drawback, which is that regular users wouldn’t be able to do ID-cheks w/o becoming authors (but maybe this is fine).
Is there already a configuration option, flag or recommended pattern in the current version to distinguish “creator” vs “regular user/subscriber” on the frontend, beyond the ID‑check and Compliance settings?
If not, could you provide some guidance on where to hook this in the code (controllers, middleware, config) so that I can implement this additional permission layer cleanly on top of your existing system?
If needed, I can provide you with test accounts (one creator, one subscriber) on intimiclub.fr so you can see the difference between what I want for creators vs subscribers.
So overall, if I were you, I’d do this:
- Ignore filament-shield permissions for now
- Create a new users.is_creator flag
- Duplicate the ID-verify, user settings module & rebrand it to a creator check step
- Duplicate both the user-side flow and the admin side one for this
- Once you reliably have that flag set for each user, you could go over each section that is used for posting content and deny access (404) if that flag is not present (EG: You could do this at a higher level, like the controller’s construct, middlewares, etc.)
I think this would be feasible. I’ll also circle back over this aspect, maybe this is something we could add out of the box w/o too much friction/making things too complicated for users.
Thanks & let me know.
Hello, I liked your work. When will we see an “explore posts” button or the ability for paid users to post for free? That would make it a very complete platform.
Hi there,
Thanks for the feedback, I appreciate it.
Regarding the explore button, there is actually one available for unregistered users, which sends to the search page, but we plan on revisiting that one. I’ll be reserved and won’t give additional info on this one atm, but this will be addressed soon enough (got some big plans in mind).
As for paid profiles being able to post free posts, I made a note on this one so we can further review. So far, the platform has been optimized for paid accounts, then free and open profiles on the side, which can post for free. We intended to have users create two accounts, one paid one and one free one, and have them linked via the profile URL field.
Thanks again for the feedback!
For example, if I try to access http://127.0.0.1:8000/admin, after logging in I see the message: “An internal error occurred. Sorry, something happened on our end.
Please try again or contact us if the error persists.”
Go to top »
Hi there,
That is not expected. If possible, send us a DM with your storage/logs/larave.log file or cPanel credentials, and we’ll have a look.
Thanks!
Thank you for the new update !
Hi there,
You’re welcome, and stay tuned, as more features and improvements are planned for the upcoming period!
Thanks for the feedback, really appreciate it!
Hello dear Ic0de team 1. Can you add new modern landing page in coming update ? 2. Can you add more payment gateways in coming update ( iyzico,payu etc..) ?
Thanks Regards
Hi there,
1. We’d like to revamp the homepage in the next update.
2. Turkish-based/supporting payment providers are on the list. We’ve done some research, as far as I recall, we had some issues registering accounts, at least for Yzico, w/o a Turkish ID card.
For 2, if you think you can help with an account, feel free to send us a DM, and we’ll look more into it.
Thanks!
Hello again dear Ic0de team You can add the PayU and Verotel (2checkout ) payment system. Thanks Regards
It would be great if you modernized the design beyond just the homepage, because they’ve been using the same design for years.
Thanks for the feedback. we will look into it.
Stories still need some refinement.
1. Unfortunately, Stories often stop and don’t progress to the next one. You can see this in Rachel’s demo. You have to click to move to the next one.
2. Video in any format other than vertical is excessively stretched horizontally and cut off.
3. It’s bad that the inscription that can be added can only be in one place in the middle and it cannot be moved.
I haven’t fully tested Stories yet. But these are my first impressions.
Besides, you still haven’t fixed the previous reported issues, starting with dimming the lightbox or not cutting off the video in the carousel for example…
Hi there,
1. Yes, it seems like there is such a bug for videos, will have it investigated and fixed in the next patch. It could be related to the demo not having ffmpeg and not properly probing videos’ lengths (so it doesn’t know when it ends), but even in that case, it should follow the maximum/default story length admin settings.
2. Yes, generally speaking, stories are vertical content optimized (and this is common for social media networks). There aren’t many options other than cropping (what we do), stretching, or adding black bars.
3. Text overlays can be moved around wherever you want. Just add the text via the text field, then click & drag/tap the text section to move it around. It also has a snap-in-place feature so you can center it decently.
Overall, though we’ve done extensive testing, some bugs might still go through with the first version; it will be improved over time.
As for your previously reported, feed-related media consistency issues, I still have that ticket around, but I was considering a larger-scoped, feed/profiles-related refactoring session, where we want to touch more feed aspects in one update, most likely in the new one.
Thanks for the feedback, and do let me know if you have any other questions.
3. It’s strange, because on my Android phone I can’t seem to move texts onto the video. It only moves slightly horizontally, making strange combinations.
I see, it does seem like you’re right. I think the mobile draggable events might be a bit off.
Created a note and will have this fixed in the next patch.
Thanks!
Ok, it would be nice to be able to add black bars to various video formats, or have the background blurring out of these videos, which is often the case.
Yup, actually, blurred zoom-ed in bgs instead of blackbars is something that sounds more modern/seen some other sites doing it.
I’ve created a note on this matter. But yeah, overall, as mentioned, stories & reels are basically vertically centered optimized content.
Will let you know when we have news on that one.
Yes. But the user can add different formats. The platform should automatically complete the vertical format.
Thanks for the suggestion. I will have this under the radar for upcoming story-related updates.
Hello my friend : Add a feature that allows models to send mass messages to sell media based on a list of all subscribers, or all profile visitors, similar to OnlyFans.
Second feature: add an agency account. This allows the creation of an agency, the ability to add models, and to pay them through a commission chosen by the agency. Models can request to join an agency, and the agency profile can manage certain options of the model, etc.
Hi there,
You can already send mass messages to your subscribers (including PPV ones) via the messenger.
Regarding your 2nd suggestion, I did note this one down, but can’t make any promises on it atm, will let you know. Btw, as a site admin, you can impersonate any users and manage their accounts.
Thanks, and let us know.
Hi, are you planning to add face recognition to the ID validation feature?
Currently we would not know if the ID is submitted by the owner of the ID.
Thanks for your reply
Hi there,
Yes, we do plan to add 3rd party based ID-checks in the upcoming updates.
Will let you know when we have any news on this one.
Thanks & do let us know if you have any other questions.
Dear JustFans Support Team,
Thank you for your previous response regarding the streaming access control issue. Following your suggestion, I implemented the role-based permission system, but unfortunately, it does not resolve the core problem.
What I’ve Implemented:
Following the standard Laravel/Shield permissions approach, I have:
Created a new “Creator” role with the following permissions:
Create Post
Create Stream
Create Attachment
Assigned the “Creator” role to creator accounts
Kept subscriber accounts with the “User” role (0 permissions)
Left “Enforce ID check” disabled
The Problem:
Despite having different roles assigned, subscribers (User role) can still access streaming features:
They can navigate to /my/streams page
They can see and click the “NOUVEAU FLUX” (New Stream) button
They have full access to the streaming interface
The role-based permissions appear to only control backend/admin panel access, not frontend user features like streaming, posting, etc.
Test Case:
User: “test abon” (@u1767801648)
Role: User (0 permissions)
Issue: Can still access /my/streams and stream creation features
Questions:
Is there a native JustFans feature or setting to restrict streaming functionality to specific roles on the frontend?
Do the Shield roles only apply to admin panel access, not to user-facing features?
If there’s no native solution, would this require custom code modification? If so, which files/controllers should be modified?
Is there a “Creator Mode” or similar feature that distinguishes content creators from regular subscribers?
What I Need:
A way to ensure that only users with the “Creator” role (or verified creators) can:
Access the streaming pages
Create streams/lives
See streaming-related menu items
While regular subscribers should only be able to:
View content
Subscribe to creators
Send messages
Platform Details:
JustFans Version: v9.5.1
Website: intimiclub.fr
Roles Module: Shield (Filament)
Could you please provide guidance on how to properly implement role-based access control for frontend features like streaming? Or if this requires custom development, could you point me to the relevant controllers/middleware that need modification?
Thank you for your continued support.
Best regards,
Dear JustFans Support Team,
Thank you for your previous response regarding the streaming access control issue. Following your suggestion, I implemented the role-based permission system, but unfortunately, it does not resolve the core problem.
What I’ve Implemented:
Following the standard Laravel/Shield permissions approach, I have:
Created a new “Creator” role with the following permissions:
Create Post
Create Stream
Create Attachment
Assigned the “Creator” role to creator accounts
Kept subscriber accounts with the “User” role (0 permissions)
Left “Enforce ID check” disabled
The Problem:
Despite having different roles assigned, subscribers (User role) can still access streaming features:
They can navigate to /my/streams page
They can see and click the “NOUVEAU FLUX” (New Stream) button
They have full access to the streaming interface
The role-based permissions appear to only control backend/admin panel access, not frontend user features like streaming, posting, etc.
Test Case:
User: “test abon” (@u1767801648)
Role: User (0 permissions)
Issue: Can still access /my/streams and stream creation features
Questions:
Is there a native JustFans feature or setting to restrict streaming functionality to specific roles on the frontend?
Do the Shield roles only apply to admin panel access, not to user-facing features?
If there’s no native solution, would this require custom code modification? If so, which files/controllers should be modified?
Is there a “Creator Mode” or similar feature that distinguishes content creators from regular subscribers?
What I Need:
A way to ensure that only users with the “Creator” role (or verified creators) can:
Access the streaming pages
Create streams/lives
See streaming-related menu items
While regular subscribers should only be able to:
View content
Subscribe to creators
Send messages
Platform Details:
JustFans Version: v9.5.1
Website: intimiclub.fr
Roles Module: Shield (Filament)
Could you please provide guidance on how to properly implement role-based access control for frontend features like streaming? Or if this requires custom development, could you point me to the relevant controllers/middleware that need modification?
Thank you for your continued support.
Best regards, IntimIClub Platform Administrator
Hi there,
So starting with this:
The role-based permissions appear to only control backend/admin panel access, not frontend user features like streaming, posting, etc.
Yes, that is a correct observation. The roles on the admin side are currently tailored for the admin interface, mainly targeting moderation purposes.
However, I suspect that it should be possible to add your own layer of permissions on the frontend based on it.
Overall, our current system doesn’t feature a per-se “creator-role”, keeping things a bit more dynamic, by being able to restrict users from posting content (or streams) based on the ID-check flag (which would be required for a proper creator-elevation as well), then based on additional Compliance settings you can further restrict who’s able to earn money on their profiles as well.
Can you maybe walk me through again your initial desired scenario? If you can attach me step to reproduce, maybe I can understand it better.
PS: Now that I think better, I do have an internal ticket referring to being able to hide the create stream/posts from menus if not verified. At the moment, it lets you access them, but you can’t really post/stream. Is this what you mea,n maybe?
Thanks, and let me know.
Hello, good evening. When will the new version with the bug fixes be released? I’m hoping for a fix for the bug that prevents tips from appearing in the notification panel.
Hi there,
We’re nearing completion of the next update, which includes the fix you mentioned, along with other fixes and new features.
Hopefully, it will arrive in a day or two, if everything goes well.
Thanks, and let me know if you have any other questions.
I am getting the just fans logo when creators try to make an account, why are hey seeing this, the site has been rebranded… any ideas on how to fix it?
Hi there,
That doesn’t sound expected. Have you made sure you replaced both light and dark logos from the admin?
Feel free to send us a DM with your site link so we can also have a look @ https://codecanyon.net/user/ic0de#contact.
Thanks, and let me know!
One more question , In order to extend support I always need to pay the license + support , or is there an option to just pay for the support ? Thanks
Hi there,
I am not sure exactly how, but you should be able to just renew the support w/o buying another license.
Seems like this page includes more details/screenshots on the process @ https://help.market.envato.com/hc/en-us/articles/207886473-Extend-or-renew-Item-Support .
Thanks, and let me know if you have any other questions.
Hi , I did an update to the last version and Im getting this error:
Oops! An Error Occurred The server returned a “500 Internal Server Error”. Something is broken. Please let us know what you were doing when this error occurred. We will fix it as soon as possible. Sorry for any inconvenience caused.
in the laravel.log Im getting this: [stacktrace] #0 /var/www/os/vendor/laravel/framework/src/Illuminate/Database/Connection.php(778): Illuminate\\Database\\Connection->runQueryCallback() #1 /var/www/os/vendor/laravel/framework/src/Illuminate/Database/Connection.php(397): Illuminate\\Database\\Connection->run() #2 /var/www/os/vendor/laravel/framework/src/Illuminate/Database/Query/Builder.php(3188): Illuminate\\Database\\Connection->select() #3 /var/www/os/vendor/laravel/framework/src/Illuminate/Database/Query/Builder.php(3173): Illuminate\\Database\\Query\\Builder->runSelect() #4 /var/www/os/vendor/laravel/framework/src/Illuminate/Database/Query/Builder.php(3763): Illuminate\\Database\\Query\\Builder->Illuminate\\Database\\Query\\{closure}() #5 /var/www/os/vendor/laravel/framework/src/Illuminate/Database/Query/Builder.php(3172): Illuminate\\Database\\Query\\Builder->onceWithColumns() #6 /var/www/os/app/Helpers/helpers.php(97): Illuminate\\Database\\Query\\Builder->get() #7 /var/www/os/app/Helpers/helpers.php(17): getSettingVoyager() #8 /var/www/os/app/Providers/SettingsServiceProvider.php(375): getSetting() #9 /var/www/os/app/Providers/Filament/AdminPanelProvider.php(91): App\\Providers\\SettingsServiceProvider::setupLocalStorage() #10 /var/www/os/vendor/filament/filament/src/PanelProvider.php(15): App\\Providers\\Filament\\AdminPanelProvider->panel() #11 /var/www/os/vendor/laravel/framework/src/Illuminate/Collections/helpers.php(266): Filament\\PanelProvider->Filament\\{closure}() #12 /var/www/os/vendor/filament/filament/src/Facades/Filament.php(177): value() #13 /var/www/os/vendor/laravel/framework/src/Illuminate/Container/Container.php(1672): Filament\\Facades\\Filament::Filament\\Facades\\{closure}() #14 /var/www/os/vendor/laravel/framework/src/Illuminate/Container/Container.php(1590): Illuminate\\Container\\Container->fireCallbackArray() #15 /var/www/os/vendor/laravel/framework/src/Illuminate/Container/Container.php(990): Illuminate\\Container\\Container->fireResolvingCallbacks() #16 /var/www/os/vendor/laravel/framework/src/Illuminate/Foundation/Application.php(1078): Illuminate\\Container\\Container->resolve() #17 /var/www/os/vendor/laravel/framework/src/Illuminate/Container/Container.php(903): Illuminate\\Foundation\\Application->resolve() #18 /var/www/os/vendor/laravel/framework/src/Illuminate/Foundation/Application.php(1058): Illuminate\\Container\\Container->make() #19 /var/www/os/vendor/laravel/framework/src/Illuminate/Foundation/helpers.php(138): Illuminate\\Foundation\\Application->make() #20 /var/www/os/vendor/filament/filament/src/FilamentManager.php(361): app() #21 /var/www/os/vendor/laravel/framework/src/Illuminate/Support/Facades/Facade.php(363): Filament\\FilamentManager->getPanels() #22 /var/www/os/vendor/filament/filament/routes/web.php(15): Illuminate\\Support\\Facades\\Facade::__callStatic() #23 /var/www/os/vendor/laravel/framework/src/Illuminate/Routing/Router.php(524): Illuminate\\Support\\ServiceProvider->{closure}() #24 /var/www/os/vendor/laravel/framework/src/Illuminate/Routing/Router.php(480): Illuminate\\Routing\\Router->loadRoutes() #25 /var/www/os/vendor/laravel/framework/src/Illuminate/Routing/RouteRegistrar.php(212): Illuminate\\Routing\\Router->group() #26 /var/www/os/vendor/filament/filament/routes/web.php(14): Illuminate\\Routing\\RouteRegistrar->group() #27 /var/www/os/vendor/laravel/framework/src/Illuminate/Support/ServiceProvider.php(194): require(’...’) #28 /var/www/os/vendor/spatie/laravel-package-tools/src/Concerns/PackageServiceProvider/ProcessRoutes.php(14): Illuminate\\Support\\ServiceProvider->loadRoutesFrom() #29 /var/www/os/vendor/spatie/laravel-package-tools/src/PackageServiceProvider.php(85): Spatie\\LaravelPackageTools\\PackageServiceProvider->bootPackageRoutes() #30 /var/www/os/vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php(36): Spatie\\LaravelPackageTools\\PackageServiceProvider->boot() #31 /var/www/os/vendor/laravel/framework/src/Illuminate/Container/Util.php(43): Illuminate\\Container\\BoundMethod::Illuminate\\Container\\{closure}() #32 /var/www/os/vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php(96): Illuminate\\Container\\Util::unwrapIfClosure() #33 /var/www/os/vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php(35): Illuminate\\Container\\BoundMethod::callBoundMethod() #34 /var/www/os/vendor/laravel/framework/src/Illuminate/Container/Container.php(836): Illuminate\\Container\\BoundMethod::call() #35 /var/www/os/vendor/laravel/framework/src/Illuminate/Foundation/Application.php(1151): Illuminate\\Container\\Container->call() #36 /var/www/os/vendor/laravel/framework/src/Illuminate/Foundation/Application.php(1132): Illuminate\\Foundation\\Application->bootProvider() #37 [internal function]: Illuminate\\Foundation\\Application->Illuminate\\Foundation\\{closure}() #38 /var/www/os/vendor/laravel/framework/src/Illuminate/Foundation/Application.php(1131): array_walk() #39 /var/www/os/vendor/laravel/framework/src/Illuminate/Foundation/Bootstrap/BootProviders.php(17): Illuminate\\Foundation\\Application->boot() #40 /var/www/os/vendor/laravel/framework/src/Illuminate/Foundation/Application.php(342): Illuminate\\Foundation\\Bootstrap\\BootProviders->bootstrap() #41 /var/www/os/vendor/laravel/framework/src/Illuminate/Foundation/Console/Kernel.php(473): Illuminate\\Foundation\\Application->bootstrapWith() #42 /var/www/os/vendor/laravel/framework/src/Illuminate/Foundation/Console/Kernel.php(195): Illuminate\\Foundation\\Console\\Kernel->bootstrap() #43 /var/www/os/artisan(35): Illuminate\\Foundation\\Console\\Kernel->handle() #44 {main} [stacktrace] #0 /var/www/os/vendor/laravel/framework/src/Illuminate/Database/Connection.php(406): PDO->prepare() #1 /var/www/os/vendor/laravel/framework/src/Illuminate/Database/Connection.php(811): Illuminate\\Database\\Connection->Illuminate\\Database\\{closure}() #2 /var/www/os/vendor/laravel/framework/src/Illuminate/Database/Connection.php(778): Illuminate\\Database\\Connection->runQueryCallback() #3 /var/www/os/vendor/laravel/framework/src/Illuminate/Database/Connection.php(397): Illuminate\\Database\\Connection->run() #4 /var/www/os/vendor/laravel/framework/src/Illuminate/Database/Query/Builder.php(3188): Illuminate\\Database\\Connection->select() #5 /var/www/os/vendor/laravel/framework/src/Illuminate/Database/Query/Builder.php(3173): Illuminate\\Database\\Query\\Builder->runSelect() #6 /var/www/os/vendor/laravel/framework/src/Illuminate/Database/Query/Builder.php(3763): Illuminate\\Database\\Query\\Builder->Illuminate\\Database\\Query\\{closure}() #7 /var/www/os/vendor/laravel/framework/src/Illuminate/Database/Query/Builder.php(3172): Illuminate\\Database\\Query\\Builder->onceWithColumns() #8 /var/www/os/app/Helpers/helpers.php(97): Illuminate\\Database\\Query\\Builder->get() #9 /var/www/os/app/Helpers/helpers.php(17): getSettingVoyager() #10 /var/www/os/app/Providers/SettingsServiceProvider.php(375): getSetting() #11 /var/www/os/app/Providers/Filament/AdminPanelProvider.php(91): App\\Providers\\SettingsServiceProvider::setupLocalStorage() #12 /var/www/os/vendor/filament/filament/src/PanelProvider.php(15): App\\Providers\\Filament\\AdminPanelProvider->panel() #13 /var/www/os/vendor/laravel/framework/src/Illuminate/Collections/helpers.php(266): Filament\\PanelProvider->Filament\\{closure}() #14 /var/www/os/vendor/filament/filament/src/Facades/Filament.php(177): value() #15 /var/www/os/vendor/laravel/framework/src/Illuminate/Container/Container.php(1672): Filament\\Facades\\Filament::Filament\\Facades\\{closure}() #16 /var/www/os/vendor/laravel/framework/src/Illuminate/Container/Container.php(1590): Illuminate\\Container\\Container->fireCallbackArray() #17 /var/www/os/vendor/laravel/framework/src/Illuminate/Container/Container.php(990): Illuminate\\Container\\Container->fireResolvingCallbacks() #18 /var/www/os/vendor/laravel/framework/src/Illuminate/Foundation/Application.php(1078): Illuminate\\Container\\Container->resolve() #19 /var/www/os/vendor/laravel/framework/src/Illuminate/Container/Container.php(903): Illuminate\\Foundation\\Application->resolve() #20 /var/www/os/vendor/laravel/framework/src/Illuminate/Foundation/Application.php(1058): Illuminate\\Container\\Container->make() #21 /var/www/os/vendor/laravel/framework/src/Illuminate/Foundation/helpers.php(138): Illuminate\\Foundation\\Application->make() #22 /var/www/os/vendor/filament/filament/src/FilamentManager.php(361): app() #23 /var/www/os/vendor/laravel/framework/src/Illuminate/Support/Facades/Facade.php(363): Filament\\FilamentManager->getPanels() #24 /var/www/os/vendor/filament/filament/routes/web.php(15): Illuminate\\Support\\Facades\\Facade::__callStatic() #25 /var/www/os/vendor/laravel/framework/src/Illuminate/Routing/Router.php(524): Illuminate\\Support\\ServiceProvider->{closure}() #26 /var/www/os/vendor/laravel/framework/src/Illuminate/Routing/Router.php(480): Illuminate\\Routing\\Router->loadRoutes() #27 /var/www/os/vendor/laravel/framework/src/Illuminate/Routing/RouteRegistrar.php(212): Illuminate\\Routing\\Router->group() #28 /var/www/os/vendor/filament/filament/routes/web.php(14): Illuminate\\Routing\\RouteRegistrar->group() #29 /var/www/os/vendor/laravel/framework/src/Illuminate/Support/ServiceProvider.php(194): require(’...’) #30 /var/www/os/vendor/spatie/laravel-package-tools/src/Concerns/PackageServiceProvider/ProcessRoutes.php(14): Illuminate\\Support\\ServiceProvider->loadRoutesFrom() #31 /var/www/os/vendor/spatie/laravel-package-tools/src/PackageServiceProvider.php(85): Spatie\\LaravelPackageTools\\PackageServiceProvider->bootPackageRoutes() #32 /var/www/os/vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php(36): Spatie\\LaravelPackageTools\\PackageServiceProvider->boot() #33 /var/www/os/vendor/laravel/framework/src/Illuminate/Container/Util.php(43): Illuminate\\Container\\BoundMethod::Illuminate\\Container\\{closure}() #34 /var/www/os/vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php(96): Illuminate\\Container\\Util::unwrapIfClosure() #35 /var/www/os/vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php(35): Illuminate\\Container\\BoundMethod::callBoundMethod() #36 /var/www/os/vendor/laravel/framework/src/Illuminate/Container/Container.php(836): Illuminate\\Container\\BoundMethod::call() #37 /var/www/os/vendor/laravel/framework/src/Illuminate/Foundation/Application.php(1151): Illuminate\\Container\\Container->call() #38 /var/www/os/vendor/laravel/framework/src/Illuminate/Foundation/Application.php(1132): Illuminate\\Foundation\\Application->bootProvider() #39 [internal function]: Illuminate\\Foundation\\Application->Illuminate\\Foundation\\{closure}() #40 /var/www/os/vendor/laravel/framework/src/Illuminate/Foundation/Application.php(1131): array_walk() #41 /var/www/os/vendor/laravel/framework/src/Illuminate/Foundation/Bootstrap/BootProviders.php(17): Illuminate\\Foundation\\Application->boot() #42 /var/www/os/vendor/laravel/framework/src/Illuminate/Foundation/Application.php(342): Illuminate\\Foundation\\Bootstrap\\BootProviders->bootstrap() #43 /var/www/os/vendor/laravel/framework/src/Illuminate/Foundation/Console/Kernel.php(473): Illuminate\\Foundation\\Application->bootstrapWith() #44 /var/www/os/vendor/laravel/framework/src/Illuminate/Foundation/Console/Kernel.php(195): Illuminate\\Foundation\\Console\\Kernel->bootstrap() #45 /var/www/os/artisan(35): Illuminate\\Foundation\\Console\\Kernel->handle() #46 {main} “}
Column not found: 1054 Unknown column 'order' in 'order clause' at /var/www/os/vendor/laravel/framework/src/Illuminate/Database/Connection.php:406)Hi there,
If possible, please send us your cPanel/server credentials (or full log file) at https://codecanyon.net/user/ic0de#contact and we’ll get back to you/have a look.
Generally speaking, that error you included is not 100% relevant, could be related to .env missing in the update procedure.
Thanks and let me know!
Hi I want to send video how to install it please Thank you
Hi there,
Unfortunately, we do not have any recent installation videos other than the one from the description.
However, if you need any help with the installation process, feel free to send us a DM at https://codecanyon.net/user/ic0de#contact, and we’ll try to get you unstuck.
Thanks, and let me know.
Hi, Is there a setting option (adminpanel) that allows non-logged-in users to view all post feeds (i.e., make the feed public without requiring login)?
I want to make the Home feed (justfans.qdev.tech/feed) and Steams page (justfans.qdev.tech/search?query=&filter=videos=) available to the public without requiring login.
Hi there,
No, unfortunately, at the moment, there is no such option.
We did, however, consider a similar approach so we could have at least exposed some feed posts over different pages w/o being logged in (like homepage/login page).
I will let you know when/if we manage to add this one.
Thanks, and let us know.
Hi Icode, thank you for confirming. Please consider having an admin settings to allow the Home page feed and Streams page feeds (at least the free feeds) to be publicly accessible without requiring users to log in. Let me know here if this happens.
Will do, thanks for the suggestion!
Hello,
I saw in the comments that you previously helped a buyer integrate JustFans with a dating / matching concept.
I’m currently building a SaaS where:
users match through a dating interface
once there is a match, communication (chat, audio/video calls, private content, live, tips) is handled by JustFans
creators are free to monetize or not
I would like your advice on the best technical approach:
integrate JustFans as the core platform and connect a custom dating front-end?
or keep JustFans as a separate module linked via user sync / API?
From your experience, what would you recommend to make this scalable and maintainable?
Thank you in advance for your guidance. Marc
Hi there,
Overall, I think the best approach, at least from a broader perspective, might be to have both apps as separate platforms and have a common login entry point (such as an SSO) that allows you to share/sync accounts between platforms. And then, if needed, you could expose some API links to share data between them further.
It might not be the most trivial thing to do, but it is definitely possible.
Thanks, and let us know.
Hi again, thanks for your previous advice.
Quick question: for the dating/matching side, we are considering Loveria (Laravel) instead of a WordPress solution like Qiupid. Since Loveria is also Laravel (same stack as JustFans), we assume it will be easier to integrate via SSO + API and keep both apps separate as you suggested.
In your opinion, is Laravel-to-Laravel (Loveria + JustFans) the better foundation for scalability/maintenance vs WordPress (Qiupid)?
Any pitfalls you’d warn us about (auth conflicts, user models, real-time features, database sync, etc.)?
Thanks!
Hi there,
Hmm, yes, I think Laravel-Laravel might be a better choice than Laravel-WP, if that script meets your requirements.
To be honest, I wouldn’t really be able to identify common pitfalls at a glance. I previously worked on such projects, but they were on a different tech stack, and a slightly different architecture, so I can’t say for sure.
I am currently working around the clock to send out a new update for this product, but after, I could have a look over some native SSO solutions, maybe we could facilitate this a bit out of the box in the near future.
Anyway, if you decide to kickstart your implementation and have any general questions, do let me know via a comment or a DM, and I’ll try to advise as best as we can.
Thanks, and let me know!
The filter field doesn’t seem to be working properly. https://imgur.com/a/oClYYjO
Hi there,
Sorry, seems like your image isn’t loading.
Also, better to use the same message thread so we can reply to them more easily.
Thanks.
Hi, does this software have below functionalities: Video calls, pay to text, subscriber wallet, keyword detector to see if creators or subscribers are communicating outside of our privacy policy, ability to post on twitter and snap with once click and gift shop for subscribers to be able to buy creators gifts via the sites Amazon store.
Hi there,
Not supported:
- Video calls
- Keyword detector to see if creators or subscribers are communicating outside of our privacy policy
- Gift shop for subscribers to be able to buy creators gifts via the sites Amazon store.
Supported:
- pay to text (PPV messages), subscriber wallet
- ability to post on Twitter and snap with one click (default media share dialog from OS)
We’ve made some notes on the unsupported features, maybe we can add some of them in the upcoming versions.
Thanks, and let us know if you have any other questions.
Hello, I have configured Live Streaming with Livekit, but for some reason in camera settings, camera and microphone are not visible and nothing is showing.
Hi there,
If possible, please send us a DM with more info, like the site link, and I will have a look as well.
I suspect there could be some kind of browser (possibly permissions-related as well) error causing them not to open.
Thanks, and let me know.
Pusher service was not configured. That is why it was not asking for camera and microphone permissions.
I have another issue with uploading big media files, 1.4GB. It is taking so long and I can’t see any progress. I’m using local storage
Got it, sounds good.
Regarding file uploads, they can be tricky to set up, but should be stable after that. I suspect the issues you’re having are with videos, right?
Checking these guides might help as well:
- https://docs.qdev.tech/justfans/documentation.html#file-upload-limits
- https://docs.qdev.tech/justfans/documentation.html#ffmpeg-troubleshooting
PS: We plan on adding some improvements over the transcoding area in upcoming updates as well.
Thanks, and let us know.
Thanks for the suggestions.
Now we see some improvement, but still upload is not working and I think the issue is with Cloudflare. Im getting timeout from Cloudflare. I see progress on video preview is done, but it doesn’t end and it ends after some time and I see in network tab that I got timeout from Cloudflare. I have turned on chunk upload and put 10 MB per chunk. Do you have any suggestions?
Hi there,
Yeah, the thing is, the ffmpeg processed tasks as running in synced mode, meaning the web-server, PHP, and in your case, Cloudflare timeouts should be increased.
I could have added async/queue-based jobs instead quite easily, but I kind of avoided that, as most of the customers have low tech experience or shared hosting packages, we initially preferred a simple solution.
I do plan to look into encoding-related optimizations after this update that is about to come.
Will keep you posted on this aspect.
Thanks, and let me know if you have any other questions.
I have managed somehow to make it all work, but now when I play video, it becomes laggy at some point. I did uploaded 4K video, so its big video, but how to make it not laggy. Do you have any suggestions on this matter?
Hi there,
You mean you now get issues when playing out the media?
The media is served straightforwardly, using standard browser rendering/buffering, but there is no streaming, so to speak, with adaptive bitrate as the streams are built.
One thing that might improve loading speeds could be using a storage driver with CDN support (which serves the content from the best locations, next to the client).
As for encoding improvements, as mentioned, we plan on researching some more performant ways of doing it in upcoming updates.
Thanks, and let me know.
Yes. If you have some email, I can share website link with you, so you can check how it looks. This is the most important thing for us, because our clients is mostly depended on videos. If video is not working as well, that is not good for us. I understood what you are saying, but I don’t think this is CDN issue. Friend from USA where server is located also have issues with playing video. It looks like something with player.
Hi there,
Sure, feel free to send me a website link and credentials over a DM and I’ll have a look @ https://codecanyon.net/user/ic0de#contact .
Thanks!
Is the watermark on the website name or the user’s profile name?
Hi there,
The watermark can either be an image or user profile url as text.
Watermarking requires videos transcoding (ffmpeg/coconut) and GD for images (but this is usually included with PHPs).
Thanks, and let us know.
