Formulaire, the premium form builder

shaman79

luceos Thank you for tip. Tried that and unfortunately it does not changed anything 🙁

luceos

shaman79 can you output the full error, I see Problem 1, so I assume there are more? Also post the output of php flarum info please.

Edit; I do not see any new tokens being generated or your account, please get in touch with me on discord luceos#0001 or send me an email at earth@extiverse.com to get this resolved.

shaman79

The Problem 1 is the only problem.


Flarum core 1.0.4
PHP version: 7.4.3
Loaded extensions: Core, date, libxml, openssl, pcre, zlib, filter, hash, pcntl, Reflection, SPL, session, standard, sodium, mysqlnd, PDO, xml, calendar, ctype, curl, dom, mbstring, FFI, fileinfo, ftp, gd, gettext, iconv, json, exif, mysqli, pdo_mysql, pdo_pgsql, pgsql, Phar, posix, readline, shmop, SimpleXML, sockets, sysvmsg, sysvsem, sysvshm, tokenizer, xmlreader, xmlwriter, xsl, zip, Zend OPcache
+----------------------------------+---------+--------+
| Flarum Extensions                |         |        |
+----------------------------------+---------+--------+
| ID                               | Version | Commit |
+----------------------------------+---------+--------+
| flarum-tags                      | v1.0.3  |        |
| flarum-suspend                   | v1.0.0  |        |
| flarum-lock                      | v1.0.0  |        |
| flarum-flags                     | v1.0.0  |        |
| flarum-markdown                  | v1.0.1  |        |
| kilowhat-formulaire              | 1.5.0   |        |
| isaced-email-verification-switch | 1.0.0   |        |
| fof-formatting                   | 1.0.0   |        |
| fof-best-answer                  | 1.0.1   |        |
| flarum-mentions                  | v1.0.0  |        |
| flarum-subscriptions             | v1.0.0  |        |
| flarum-sticky                    | v1.0.0  |        |
| flarum-statistics                | v1.0.0  |        |
| flarum-likes                     | v1.0.0  |        |
| flarum-lang-english              | v1.0.0  |        |
| flarum-emoji                     | v1.0.0  |        |
| flarum-bbcode                    | v1.0.0  |        |
| flarum-approval                  | v1.0.0  |        |
| fof-user-directory               | 1.0.2   |        |
| fof-subscribed                   | 1.0.0   |        |
| fof-polls                        | 1.0.3   |        |
| fof-links                        | 1.0.0   |        |
| kyrne-websocket                  | 3.0.3   |        |
| fof-upload                       | 1.0.1   |        |
+----------------------------------+---------+--------+
Base URL: <redacted>
Installation path: <redacted>
Debug mode: off

luceos

shaman79 are you positive you generated a new token and stored it onto your server?

shaman79

luceos I am relatively positive that I done it right. I checked composer config --list and it shows correct entry for [bearer.extiverse.com].

I am not using my account on extiverse, but zdeneque - this is my colleague who is registered there an who manages the extensions.

clarkwinkelmann

I think everything's good on my side, the extension should install fine on 1.2.1.

From the error message it looks indeed like an Extiverse misconfiguration. I hope you can resolve this with luceos, otherwise you can also contact me via email or Discord but if it's Extiverse related I might not be able to help directly.

shaman79

clarkwinkelmann Can you check, please, if we have correctly set subscription?

clarkwinkelmann

shaman79 I'm not seeing any active subscription with a username or email containing zdeneque. Maybe the yearly subscription was terminated? I also don't see any recent payment error that would have caused an automated termination.

Unfortunately the Extiverse dashboard doesn't show me cancelled subscriptions, luceos would have to look into that.

luceos

shaman79 the subscription was cancelled and deleted on November 12th of last year.

shaman79

clarkwinkelmann Hi, are you sure it should have been cancelled? It should have been lifetime subscription as our company sponsored the development if I remember correctly. I was not directly involved, so I might be confusing something, but can you re-check it? Thank you.

Teddan

clarkwinkelmann is the extension not able to run under php 8.0?

GreXXL

I think this is really useful and I finally decided to give it a spin 😉 A question about user-forms. Is it currently possible to give the user a possibility to decide who is able to view it's filled out information. From my understanding it is possible to select access on a per-form basis, but it's not possible to let the user decide weather its only visible to himself, or for example all members. If it is as I think - could this be a future feature that is supported by formulaire? 🙂

A side question: Would it be possible (as a custom extension) to make a graph out of the results of a user-profile?

Maybe to better explain my use case that I had realised with a custom extension on a previous forum:
I want members to be able to add levels on a per-day basis to their profile. This is currently very achievable with a multi-entries form in formulaire. I'd love for people to have the possibility to decide weather its just visible to themselves or to all members. Then I would want to display those entries in a graph within the user-form 🙂

clarkwinkelmann

GreXXL unfortunately there's currently no feature to let users choose to make their own profile public, but that's a great idea! I'll take note for a future update.

A way to achieve this in the current version would be to create 2 copies of the same profile form, make one public and one private, and have users fill either one or the other. But they wouldn't be able to easily switch between the two, the data would have to be copied/deleted manually when they switch. And they might end up filling both which could also be problematic to your use case.

As for adding graphs, it could totally be added as well! If it's a custom extension and if it's the only thing that needs to become public/private, then it would be even easier to implement the user control. The graph could be placed on a tab of the profile everyone can see, and the data would only be made available from the backend if the user enabled the public graph. It's probably not too complicated, with a library like Plotly it's easy to make interactive graphs in the browser. Probably a few hours of work. The only concern might be the amount of data points, though Formulaire will probably have issues long before Plotly if there are hundreds or thousands of lines.

GreXXL

clarkwinkelmann I think this would be a great addition. As for the plugin, I'll get in touch via Discord 😉 In the meantime, I have a different question on Fomulaire:

Is it intentional that for the discussion fields, you can only select tags in hierarchy 1?
Can I restrict the permission so people cannot create new discussions while still using the form to create a discussion? Or won't people be able to use the form if they do not the permission to create a new discussion?

I was thinking about creating a recipe form with formulaire and trying to find the best option for that. There are so many options that come to my mind and need more exploration 🙂 Thanks!

clarkwinkelmann

Version 1.6.1 - August 3, 2022

Fixed: lock discussion forms on Flarum 1.3+. The changes in Flarum 1.3 had made possible to continue editing the form answers on a locked or soft deleted discussion.
Fixed: unreadable colors in some parts of the form manager.
Performance: compiled javascript with Webpack 5 to reduce size.

This version is only compatible with (and necessary for) Flarum 1.3 and later.

clarkwinkelmann

GreXXL Is it intentional that for the discussion fields, you can only select tags in hierarchy 1?

That's indeed a bug, I have added it to my bug tracker for next release. You can work around it by visiting the Tags page of Flarum first, and then go to the form manager without leaving the single page app. After doing this all tags will be loaded and visible in the dropdown. I would still recommend to use first-level primary tags for this feature, but it should work with child tags and secondary tags as well.

GreXXL so people cannot create new discussions while still using the form to create a discussion

If you use the "Automatically create discussions from form submission" feature, it will bypass the discussion creation permission entirely when using the form URL to create a discussion. Only the form permissions will be checked. You can even create the discussion in a tag the user cannot see at all if you need.

I would actually recommend to prevent the user from creating discussions in that tag if the feature is used since the manually created discussions would go around the template and submission limits configured in the form.

GreXXL

clarkwinkelmann thanks so much for the detailed answers - that helps a lot. Some other questions have come up though 🫣.

If I use formulaire to create a discussion, the entry cannot be deleted within the form's mask. I can delete the discussion that has been created, though. Doing so will not get rid of the submission, though. How is that deleted? Or are you not meant to delete those?

A second question: If a field is not mandatory and is not used, would it be possible to hide it in the discussion? Currently, it's displaying the heading, but it's not filled out any content.

On the, tabs you can select there is "Access: CLOSED", which is self-explanatory. Then there is "Access: CREATE ONLY", - which I don't understand. Either it's "Access: OPEN" or reflects user permissions. Even if I allow editing own or all fields, it remains "Access: CREATE ONLY" where I'd expect something like "Access: CREATE AND UPDATE". Maybe I'm just interpreting too much into it, though...

Also, I did have another idea (don't know if feasible, though): Could formulaire overwrite the "Start a Discussion" button within a tag if there is a form assigned to this tag - so you are going to the form directly?

clarkwinkelmann

Version 1.6.2 - August 3, 2022

Fixed: all tags including children are now shown in tag selection dropdown.
Fixed: rename controls around enable and draft status for non-standalone to clear up confusion.
Fixed: make empty submission text translatable on discussion.

GreXXL the entry cannot be deleted within the form's mask

"linked" forms (discussion fields and user profiles) submissions are stored identically to standalone submissions in the database, however they should not be manipulated directly. That's why I have disabled lock/delete actions. I intend to hide the submission page entirely as well, currently it's still visible only because the code is re-used for all form types. Submissions for linked forms should automatically be created and deleted as needed by the extension.

GreXXL If a field is not mandatory and is not used, would it be possible to hide it in the discussion?

I will add an option for this in the next feature release. I think I'll add the option per-field as it will give the most flexibility.

GreXXL there is "Access: CREATE ONLY", - which I don't understand

This was also a side-effect of the same UI being used for both standalone and linked forms. I have published a patch request where I updated the translations to better reflect their purpose. On linked form, it's either in draft or enabled mode. Ability to edit is controlled through the permissions. There isn't really a concept of creation vs edition for linked forms, since its existence it linked to another resource.

GreXXL Could formulaire overwrite the "Start a Discussion" button within a tag

This is not really planned. The intent is to have forms support inside of the discussion composer in a future update.

The "create discussion from standalone form" option was a bit of a hack, it was created as a client request but that's not how I originally intended the extension to be used.

GreXXL

clarkwinkelmann "linked" forms (discussion fields and user profiles) submissions are stored identically to standalone submissions in the database, however they should not be manipulated directly. That's why I have disabled lock/delete actions. I intend to hide the submission page entirely as well, currently it's still visible only because the code is re-used for all form types. Submissions for linked forms should automatically be created and deleted as needed by the extension.

Got it, totally makes sense. Will just ignore it for now.

clarkwinkelmann I will add an option for this in the next feature release. I think I'll add the option per-field as it will give the most flexibility.

That would be very awesome. Makes the result much cleaner.

clarkwinkelmann This was also a side-effect of the same UI being used for both standalone and linked forms. I have published a patch request where I updated the translations to better reflect their purpose. On linked form, it's either in draft or enabled mode. Ability to edit is controlled through the permissions. There isn't really a concept of creation vs edition for linked forms, since its existence it linked to another resource.

Thanks for the clarification!

clarkwinkelmann This is not really planned. The intent is to have forms support inside of the discussion composer in a future update.

Sure - that makes more sense of course. Is there any estimate on this? Maybe something that could be (partly) funded/financed to get it in?

ctml

If someone is considering integrating charts with the forms then I want to throw out echarts as an option for charting library.
https://echarts.apache.org/en/index.html

« Previous Page Next Page »