getblocklab / block-lab Goto Github PK

It would be nice if there was a way to export a block as a standalone plugin with minimal scaffolding required.

It would still need to maintain the current acb_locate_template() mechanism and template loader.

A searchable list of users.

• Minimum Value
• Maximum Value
• Step Size

• Choices

😮

I noticed that although I could successfully save a custom block with a number character in the slug, as well as set up the template file, the block was not accessible in the GB editor. After changing the slug (removing number), and updating the template to match I was able to access it in the editor.

This is especially useful for theme authors who wish to use ACB to build blocks, and want to distribute the blocks with their themes.

Shows a rich editor, including formatting controls.

I get this error in the console whenever I add a block.

Might have to do this with a little JS magic.

If field_one is equal to foo then hide field_two.

Video screen recording of issue -> https://d.pr/v/voYvBl

When not providing a value to the max length property it defaults to zero and you can't enter characters. This value needs to not be written to the json value, or use the HTML default of 524288.

The experience with what you get when you hover over a CPT menu item where you get the "Add New" option, we should have that. :)

These will appear in the sidebar

In the editor, once the fields have been completed, a preview of the block is show.

This should include the ability to return to "edit" mode to change the fields again.

Logged in users only.

With the update to the icons in GB (Material icons), it seems we've lost access, in the current format, to dashicons.

• Required
• Default value
• Field instructions

• Placeholder text
• Character limit

• Choices

The current scripts are incredibly basic and has been used as a quick way to clean up the plugin for distribution.

We need to consider whether gulp is the right tool for the job, what we ideally would like automated (e.g. readme.txt with auto changelog), etc.

A searchable list of posts, from a given post type.

• Post type
• Post
• Taxonomy filter

When tryinh to publish a CPT from another plugin, I get the WordPress admin error
The link you have followed has expired
When I disable this plugin, I am able to publish as normal.
Have tested on a few environments and observed the same issue.

Advanced Custom Blocks Block Lab

Minor visual tweak

Steps:

• Create new custom block.
• Provide title, description, slug.
• DON'T add any fields.
• Publish the block.

Result:

Notice: Undefined index: fields 

Need to check for empty value.

This should introduce the concept of control options for custom fields. Potentially, abstract fields out further to have a field type interface / abstract, with each field type (text, texture, select) implemented as its own class.

• Choices

Implement unit testing.

The user should be able to choose from the Dashicons library. The options should be displayed visually, not as text from a dropdown menu.

Only dashicons for now.

• Return value
  • Image object
  • Image url
  • Image ID

I found this project before I found ya'll's. Ya'll's currently works for what I need but it looks like these guys also have a more expansive feature set in certain ways.

Anway, thought you might want to check it out and maybe use some of it's code, or collaborate with the dev working on the project.

https://github.com/rchipka/advanced-custom-blocks

@rheinardkorf

The block doesn't show up at all.

When a block is published, all the field (default values, required, etc) revert to default state.
Observed on:

• Toggle
  -Checkbox
• Range

• Remove date
• Add Fields column, with a count of how many fields are added

E.g. https://github.com/rheinardkorf/advanced-custom-blocks/blob/develop/php/post-types/class-block-post.php#L173

Should be esc_attr_e.

acb_field( $name, $echo ) and acb_value( $name ).

The editor breaks in Safari at the moment due to a type error when checking if control is a text input. This is not an issue in other browsers, but needs to be fixed.

The first Documentation link in https://github.com/rheinardkorf/advanced-custom-blocks points to a non-existent page. In the FAQ section and in WordPress.org it's the right link.

Plugin could not be activated because it triggered a fatal error.

Fatal error: Uncaught Error: Class 'AdvancedCustomBlocks\View\Admin_Menu' not found in /var/www/vhosts/acb.number11.co/httpdocs/wp-content/plugins/advanced-custom-blocks/advanced-custom-blocks.php:95 Stack trace: #0 /var/www/vhosts/acb.number11.co/httpdocs/wp-admin/includes/plugin.php(1897): include() #1 /var/www/vhosts/acb.number11.co/httpdocs/wp-admin/plugins.php(178): plugin_sandbox_scrape('advanced-custom...') #2 {main} thrown in /var/www/vhosts/acb.number11.co/httpdocs/wp-content/plugins/advanced-custom-blocks/advanced-custom-blocks.php on line 95

• This is on a new WP install.
• Plugin is v0.1 from the wp.org repo
• Default theme
• Not other plugins active
• PHP 7.1.20
• Has Let's Encrypt SSL Cert
• https://acb.number11.co/
• Apache