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!

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 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.

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!

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.

Hi there,

Youi can click the expand button on this page next to the searchbox, where an age filter & city search is available. https://justfans.qdev.tech/search?query=&filter=people

Thanks and let us know.

@ic0de

I missed your sale. I was investigating, comparing, and didn’t realize the sale would end so soon. I hope you have another sale soon. I would love to buy and try it out.

Thanks

Hi there,

Hi, I also want to add more fields to the initial registration. I want to add relationship statuses, like Single, Married, Divorced, Engaged, In a civil union, In a domestic partnership, It’s complicated, and Widowed. Maybe have a dropdown list. Also, add a filter in the advanced people search options to select relationship statuses.

We have created an internal ticket to look into this possibility. will let you know if we have any news on this one.

Another important feature missing is to have option to embed YouTube videos via copy and paste YouTube URL. Not everybody wants to start an adult sex site. Please add on for others to have. If you are running an adult sex website, then you have the option to turn it off. Because that will help save server storage space. Videos take up a lot of server storage space and also help save money for the site owner. I noticed many similar scripts have those options to embed YouTube videos. There’s no maintenance mode. I hope you add my requests to the next update.

Yup, YouTube embeds and maintenance mode are something we have on our radars as well, and will most likely be added with upcoming versions.

Thanks for the suggestions, and do let us know if you have any other questions.

Hi there,

Thanks for the kind words and feedback!

Yes, at a glance, it seems like your concern is valid. I was able to reproduce it as well.

I have created an internal ticket and will have this one sorted out with the next update. If this turns out to be a quick one-file fix, I can probably forward you the fix, but better to wait for the next update either way, as it will be a pretty big one.

Thanks again, and do let me know if you run into any other issues/questions.

Hi there,

Unfortunately, no, you can not add new fields out of the box, but that could be achieved quite easily with some custom changes.

I’ve created an internal note as well. Maybe in the future we could have more advanced registration options from the admin panel.

Thanks, and let us know if you have any other questions.

Hi there,

Unfortunately, at the moment, it would seem like this is not possible.

The limitation seems to come from the fact that the platform doesn’t actually have a “free-profiles only” mode enforcement. If we add such a mode, your case should then be possible.

I have created an internal ticket on this matter, as this sounds like a good idea.

In the meantime, you could still achieve a similar system by:

1) Making free profiles the default profile type 2) Users will still be able to change their profile type to paid 3) Now you can either enforce ID checks, so only admin-verified users can post content 4) You can also set the Settings > Compliance > Posts before monetization to 1.

With these settings, you can achieve a similar flow, as step 4 can stop the ability of actually earning money, even if the profile is set to “paid”.

Thanks, and let us know!

Hi there,

From what you described, this sounds normal. Here’s a quick message template I had on profile types, maybe this will make things a bit easier to understand on your side:

So, in order to accommodate multiple scenarios of running the website, there are multiple profile types, some can be disabled entirely from the admin side.

• Regular profiles – Requires a subscription in order to gain messenger and posts access.
• Free profiles – Requires a “Follow” in order to gain messenger and posts access.
• Open profiles – Logged-in users can follow their posts for free, and also message them. Their feed posts are also available to users who haven’t logged in to the site. This option can be toggled on/off from the admin panel.

Also, PPV posts/streams/messages are locked until purchased, for all of the profile types mentioned above.

The “Is public” user-side setting is only used for hiding the user from Google search results and internal search results. Their profile will still be available to people who have access to their direct profile link.

I hope that makes sense, but please let me know if you have any other questions. Thanks.

You mentioned that Open profiles – Their feed posts are also available to users who haven’t logged in to the site. But when I set the profile to open in admin and visited the profile, I got the error: 403 | Profile access is denied.

Hi there,

One reason you might get that 403 is if the profile is having geo-blocking enabled, and he might actually be blocking your country (though admins are exempted from this, if logged in).

Thanks, and let me know.

Hi there,

Yes, you have read everything well from previous comments.

Per their guides & licensing terms, extended licenses are required for instances in which the end-user (website users) are being charged for (eg: paying for subscriptions).

Though we have tried not to make too much of a difference between the regular and extended versions, there are some small limitations (regarding theme generations service), and more such limitations could appear in the future.

Overall, to keep things simple and not expensive, you can start on a regular one, configure everything, see if you like the script, and then if you start earning money, you can upgrade to an extended one, so you can be fully legit with your instance.

And yes, if you want to upgrade later on, I can refund you the regular one so you can upgrade to extended quite easily.

Thanks and let me know.

After comparing other similar scripts. I think what you said is very important: “Yes, if you want to upgrade later on, I can refund you the regular one so you can upgrade to extended quite easily.” You should post it on your detail page because many people would want to upgrade to the Extended License and may get you more sales.

Thanks

Thanks for the suggestion, will try to add that as general info on one of our pages.

Hi there,

That kind of error should usually pop up if the actual SMTP credentials/config is not properly set (could be from address, port or SSL issues).

If still having issues, feel free to send me a DM with your admin panel and SMTP credentials and I can have a quick look as well.

Thanks!

Hi there,

Yes, by default, all profiles are “paid”, meaning users need to subscribe to them in order to see the posts/content. On top of the subscription, creators can also sell PPV content (posts, streams).

Regarding monetization, you can set up “Taxes” from the admin panel, which allows you to take a cut of each transaction made on the site.

All the money goes into the account of your payment provider, and payouts (to creators) can be done either manually or semi-automatically. You can also enforce a withdrawal fee for creators.

Thanks, and do let me know if you have any other questions.

So, if I understand the example you gave here correctly: https://justfans.qdev.tech/admin/taxes the figures shown are the money I will receive for each subscription? Is that correct?

Yes, exactly. Those are applied to each transaction made on the site, including one-time payments (tips, or PPV posts unlocks) or each subscription (and subscription renewals).

Thanks & let us know.

Hi there,

Unfortunately, the cron jobs aren’t publicly exposed and can’t be run externally at the moment.

This means that you need to set up this single cron task per this guide @ https://docs.qdev.tech/justfans/documentation.html#crons .

I have also created an internal note so we can further research this; maybe it’s something we can safely add in upcoming versions.

Thanks, and let me know if you have any other questions or need any help setting them up.

Hi there,

Please send us out a DM using this form @ https://codecanyon.net/user/ic0de#contact, and we’ll get back to you over email.

Thanks!

Hi there,

The location field (for profiles) is actually getting searched in search results (for users search), if that’s what you mean.

Feel free to send me additional info (steps/screenshots) if you think there’s a bug going on.

Thanks!

Hi there,

The ID verification module can be used to split the users between verified users, who can post content (creators), and regular users, who might not need verification at all, but can buy content from creators.

You can enforce it so it’s enabled for new accounts, but it won’t block people from accessing/using the base site, so to speak.

I imagine that is something that could be custom-coded quite easily, but I made a note, maybe this is something we could offer out of the box.

Thanks!

Hi there,

It is not open-source in the sense of licensing terms (EG: not MIT or GPL), but when purchasing, you do gain access to an Envato-licensed copy of the source code.

You can go over the following links to get started with Envato’s licensing.

https://codecanyon.net/licenses/standard https://codecanyon.net/licenses/terms/extended https://codecanyon.net/licenses/terms/regular https://help.market.envato.com/hc/en-us/articles/115005593363-Do-I-need-a-Regular-License-or-an-Extended-License-

Thanks & let us know if you have any other questions.

Hi there,

Thanks for the kind words and feedback. Going over your mentions:

possibility to format date strings in Carbon by locale for different languages, like Carbon::parse->format(‘d.m.Y’,’de_DE’)

That should already be supported out of the box.

possibility to translate slugs for different tos and privacy pages in different languages, like [‘slug’ => __($page->slug)]

Custom slugs are supported, but for some core pages (such as tos/privacy), they must be marked as such.

Haven’t really thought about slugs, but we do plan to add easier-to-translate/multi-language public pages with the next updates.

possibility to translate site description like <meta name=”description” content=”{{ __(getSetting(‘site.description’))}}”>

Regarding age control, we do plan to improve further compliance, including with modern, 3rd party-based age verification modules.

As for offline payments, yes, that system can be slightly modified via settings and translation files to accommodate other offline payment providers.

Thanks again.