Joni Halabi

Interesting. I was unable to reproduce this one, but I did just make some changes to the PHP setup function in the latest plugin version (v.4.3.1). Please let me know if that helps!

Thank you! I noticed that error too. It is fixed in the next plugin version. (v. 4.3.1)

Sorry, I just saw this issue. This was an issue between the plugin and PHP 8. (This issue does not exist on PHP 7.) A bug fix was pushed to this plugin. If you are running plugin version 1.1.3 or later, you should not see this error.

Hello!
You can add as many Color blocks as you would like to the Palette block. It does get a bit tricky, though:

1. Select the Color Palette block is selected in the editor.
* This is not the single Color block. You need the parent block to be selected.
* If you are having issues selecting the Color Palette block, you can select the single Color block, then in the toolbar, click on the left-most button that says “Select Color Palette” when you hover over it.
2. Now the entire Color Palette block should be outlined. In the bottom-right corner of the block, there will be a button with a plus (+) sign. Click that button.
3. A new Color block will appear!

Apologies for the weirdness. The new block editor’s does not exactly make it easy to add new blocks to a parent block. I’m hoping the editor / core team will address that soon!

I have been able to reproduce this issue:

1. Create a new revision of an existing post/page.
2. Edit the title of the new revision. You can see here (even before saving the revision as a draft or publishing the revision) that the permalink has changed.
3. Publish the new revision.
4. View the page. You are taken to the new permalink from the revision. This produces a 404… because the permalink of the original post was never changed, even though the content has, because publishing the revision changes the content of the original post but, apparently, does not change the original post’s permalink.
5. Go back to the list of pages in the admin and find your original post (now with new content / title). You can view the original post (with the new content from the revision) from here at the original permalink.

I am not sure if the correct behavior is to not change the permalink in the revision post in the first place or to make sure the permalink change carries over to the original post when you publish the revision, but, imho, one of those two things needs to happen.

Yes… it is using WordPress’s jQuery.

I just pushed an update to the plugin that will allow you to select countries in which this shipping option is available. You can choose to make it available for all available countries (i.e. all countries you ship to) or to specific countries. (This is similar functionality to the baked-in “fixed rate” shipping option in WooComerce.)

Please let me know if this solves your issue, or if you have any questions. Thanks!

I do not see a way to do that actually. I can look into adding a feature that will let you choose which countries this option is available in. Sorry it’s not in there now!

My fix above worked for me (and it sounds like you are having the same issue). I made the change in /advanced-custom-fields-link-picker-field/js/input.js.

It is a relatively low-risk change, but just keep in mind that if you do edit the file and then update the plugin later, that update will overwrite any changes you make. Good luck!

I am marking this as resolved, but please feel free to change that or let me know if you are still seeing this issue. Thanks!

Hi Benjamin,

I am so sorry it has taken so long to reply. I never received a notice that there was a support question here and just checked the site and found your message tonight.

There was definitely a bug in the plugin where the saved settings were not being applied. (Thank you so much for finding that and letting me know about it!) I believe it is fixed now. I pushed an update to the server (version 2.4.5.). You should see it the next time you log in to your site. Please note that after you update, you may need to clear your cache and cookies.

Please let me know if you are still seeing issues with this. Thanks again!