Plug rocks. Should really be native ;)

The plugin loads js and css resources when logged in as admin, even for non-cp requests.
This leads to errors because I'm not loading jQuery on my site.

Bug Description

When editing a supertable field using quick-field, it is impossible to save.

The server responds with a 400 Bad request error.

I suspect this is caused by the quick-field modal not showing the translationMethod dropdown as I only have 1 site.

Steps to reproduce

1. Set up a single-site Craft 4 install
2. Using the Craft native UI, create a Supertable field with the following subfields:
   • heading (Redactor)
   • contentType (Entries)
3. Save the field
4. Add the field to a field layout
5. Edit the field using quick-field
6. Rename the field handle
7. Save the field
8. The modal shakes to indicate an error, nothing else explains why it failed in details
9. In the dev tools's network tab, the query to https://example.ddev.site/index.php?p=admin%2Factions%2Fquick-field%2Factions%2Fsave-field&v=1697446077292 shows the 400 error

Expected behaviour

Saving the field should succeed.
If it doesn't, the errors property from the server response should be displayed in the quick-field modal.

Quick Field version

2.0.6

Craft CMS version

4.5.6.1

Heya,

Not sure how this is best fixed hopefully just a css tweak (taking the clear: both off of .fieldlayoutform.quick-field .newfieldbtn-container "fixes" this but causes other weirdness at different screen sizes)

If you have insanely long field groups they can overlay the quickfield buttons:

What question would you like to ask?

This plugin is currently marked as "Not Ready" for Craft 5. Are there plans to add Craft 5.0 support?

Bug Description

When creating or editing a field using quick field, the Craft "Use this field’s values as search keywords" checkbox value isn't saved.

Steps to reproduce

1. Go to a section settings
2. Edit one of its entry types
3. Create a field using the quick field modal
4. Select the "Use this field’s values as search keywords"
5. Save the field
6. Edit the field using Craft native UI to see the "Use this field’s values as search keywords" isn't checked

Expected behaviour

The "Use this field’s values as search keywords" value should be saved

Quick Field version

2.0.5

Craft CMS version

4.5.6.1

Bug Description

Since upgrading to Craft 4.4 I am not able to use the Save as new field button within the Quick Field modal for matrix fields

Error message
Cannot assign string to property craft\models\MatrixBlockType::$fieldId of type ?int in /var/www/html/vendor/craftcms/cms/src/fields/Matrix.php:297

Steps to reproduce

1. Create a new matrix field using Quick Fields
2. Edit the field in Quick Fields modal (update the name and handle)
3. Try to Save as new field

I am also trying to save the new field from within a Neo field in the CP.

Expected behaviour

No response

Quick Field version

2.0.3

Craft CMS version

4.4.7.1

If you try to save a field that contains errors in the form (invalid field handle, some required field not being filled out, etc) it will close the modal and report that something went wrong, but you'll lose everything you filled out.

It should report errors for individual fields without closing the modal.

If a field fails to save, two "An error has occurred" messages are shown but there's nothing letting you know what happened. For example save a matrix field with a field in it using a reserved word, such as 'name'. It won't save obviously but the error doesn't let you know all you need to do is change the handle from a reserved word to fix it.

I appreciate this is a very small thing that nobody's likely to ever encounter but here you go anyway!

There's no check on the existence of field groups before the New Field button is shown on field layouts. Clicking this button gives a hanging modal.

Replicate:

• Vanilla craft with quick fields installed
• Remove all field groups
• Edit a section
• Click the New Field button.

Description

Gets a 400 Post request required when saving a Super table field.

How to reproduce the error

1. Use CraftCMS 4
2. Install Quick fields plugin
3. Install Super table plugin
4. Create Section
5. Create a Super table field in with Quick field
6. Save -> Get error in console (POST 400)

System Info

Application Info

PHP version: 8.0.24
OS version: Linux 5.10.16.3-microsoft-standard-WSL2 & Linux 5.10.124-linuxkit
Database driver & version: MySQL 10.4.26
Image driver & version: Imagick 3.6.0 (ImageMagick 6.9.11-60)
Craft edition & version: Craft Pro 4.3.3
Yii version: 2.0.46
Twig version: v3.4.3
Guzzle version: 7.5.0

Plugins

Amazon S3 2.0.1
Amazon SES 2.0.1
Button Box 4.1.0
Feed Me 5.0.4
Field Manager 3.0.4
Navigation 2.0.13
Quick Field 2.0.2
Redactor 3.0.2
Smith 2.0.0
Sprig 2.3.0
Super Table 3.0.5
Typed link field 2.1.4

Add ability to edit the current fields and field groups. I'm imagining "cog" buttons next to unused fields and groups that drop down a menu with the option to edit or delete. So similar functionality to the solid bordered tabs and fields.

Creating a multi-select only allows 1 option to be added.

I have to go into craft/settings/fields to add more options, when pressing the button '+ Add an option' nothing happens.

Thanks!

Plugin icon for Craft 2.5 please :) Assuming this is compatible with 2.5+?

When creating fields through the FLD, the edit button doesn't work for the new fields.

When editing a field, changing it's group to a group that previously had no fields will not show the group.

Hey,

I have installed the plugin but in the Field Layout Designer the buttons are not showing.

Craft Version is 4.2.0.2 and Plugin version 2.0.1

Is there anything I missed ?

Thanks :)

It would be excellent if we could have the ability to spawn quick fields on other field layouts such as users, categories, assets etc. not just sections.

Bug Description

After editing a Neo field in quick-field from an entry type field layout, I noticed the field has changed to an Asset field.

While creating this ticket, I think I found the root cause of the issue: when the quick field modal window opens, the Field type dropdown isn't properly initialised and thus takes the value of the first <option>. If the user isn't extra careful when editing the field, he will overwrite the field type when saving.

Steps to reproduce

1. Using Craft UI, create a Neo field, named "Main" (handle: contentBuildersMain)
2. Go to an entry type and add the Neo field to it
3. Save the entry type
4. Edit the entry type again and edit the Neo field using quick field
5. Set the name of the Neo field to "Content blocks"
6. Save the Neo field
7. Using Craft UI, edit the Neo field and notice its type has changed to Asset

Expected behaviour

The type of the Neo field should be kept when editing a field in quick field.

When the quick-field modal window opens, the Field type dropdown should be properly initialised with the current field type.

Quick Field version

2.0.5

Craft CMS version

4.5.6.1

At the moment the form has element ID's that aren't getting namespaced, so there's possibility of ID clashing which will affect scripts from running correctly.

There's actually a working example of this - the "name" and "handle" fields already exist on some pages, so the handle script doesn't execute correctly.