Private Forum Facade

MarkoK

SychO Great! Thanks a lot! Really appreciated!

anonymousDev

SychO Wait, $12/year? Cheap............
However, this is great extension. It could easily be in the core in fact.

syntaxbyte

SychO
Thanks for the extension. But am getting this while installing with composer:
Your requirements could not be resolved to an installable set of packages.

Problem 1
- Root composer.json requires sycho/flarum-private-facade, it could not be found in any version, there may be a typo in the package name.

Potential causes:

A typo in the package name
The package is not available in a stable-enough version according to your minimum-stability setting
see https://getcomposer.org/doc/04-schema.md#minimum-stability for more details.
It's a private package and you forgot to add a custom repository to find it

Read https://getcomposer.org/doc/articles/troubleshooting.md for further common problems.

Installation failed, reverting ./composer.json and ./composer.lock to their original content.

luceos

syntaxbyte do you have an active subscription on extiverse? https://extiverse.com/extension/sycho/flarum-private-facade

syntaxbyte

@SychO

I followed the installation procedure:
composer require sycho/flarum-private-facade:"*"

Or am i doing something wrong please

syntaxbyte

luceos
No I have not.
I'm not aware that I needed to. My bad!

moreany

I can't install 🙁

luceos

moreany do you have an active subscription from extiverse? https://extiverse.com/extension/sycho/flarum-private-facade

moreany

luceos Nope

samtto

i can't install @SychO what can i do ？tks.

samtto

I have been looking forward to having this plug-in for a long time. Unfortunately, it is charged. I don't know how to pay. Personally, I can't afford this cost. Even if I pay, I don't know how to install it in a LAN without a network @luceos any free version available? It doesn't matter if there are fewer functions 0.0

luceos

samtto it's not my extension. You can reach out to @SychO to see whether he's open to a discounted plan.

djayt

@SychO I have purchased a license. But I am using flarum docker installation. How can I add a repo and get authenticated with the token?

Screenshot

I would be grateful for the instruction.

luceos

djayt you can store the token inside your repository with an auth.json file when you remove the --global flag in the composer config command. Then, while building the image, composer should just work as usual.

You can also store the token as a secret inside your ci/cd if you don't expect to run commands once the Docker container is up.

djayt

luceos
Thank you for the answer, unfortunately I don't have the knowledge to understand it. Currently, I only know that when I start the terminal (bash), I can enter a command, e.g.
docker exec -ti flarum extension require sycho/flarum-private-facade:"*" - to install the extension.

If it wasn't a big problem, I would ask you to indicate the steps to be taken for a complete layman.
Thank you.

jacobgrillo

The login form doesn't show up after updating to v1.5.0

SychO

jacobgrillo Thanks for the report! Fixed in v0.1.9 please update.

🔔 v0.1.9

Compatibility with Flarum v1.5

jacobgrillo

SychO I updated but on mobile the form out of the view, and below the footer.

Video:
https://i.gril.tk/wp-content/uploads/2022/09/IMG_6734.mov

SychO

jacobgrillo just tagged v0.1.10 which fixes the issue

phaphaya

Hi @SychO , thanks for a great extension!
I subscribed to your extension but after installation I encountered two problems:

(1) I had to disable registration in my forum (admin -> permissions -> signup CLOSED). However, when using your extension, the Sign Up is still possible. It seems the extension doesn't check this setting.

(2) I need TAGS page as a default page of my forum, not All Discussions list (admin -> basics -> homepage -> Tags page). However, after loggin in using the log in form in your extension, the user is redirected to All Discussions list. It seems the extension doesn't check this setting as well.

Can you help, please?

SychO

phaphaya Both issues have been fixed in v0.1.12, please update and try again.

« Previous Page Next Page »