jamieschmid

I just wanted to update that the above instructions worked for us. Thank you for your help @WFAdam

Oh, sorry. No I did not use Composer.

No, the CSS file is loading.

• This reply was modified 3 years, 9 months ago by jamieschmid.

Thank you, that fixed it!

Done! Thank you for looking into this ??

That’s excellent news! I can hold off until the release, thank you.

Are they going directly to the new url as well?

Please note, changing the URL doesn’t necessarily afford you better security. But this has happened to me before with xml-rpc, a big botnet attack can cripple your server. If you’re only getting a few notifications, that’s not a big deal. I think you can turn those notifications off if you’re sick of getting them.

HOWEVER, if it’s really bad and is affecting your server, get Cloudflare as it’s more powerful than Wordfence for brute force attacks.

There is a nuclear option too – you can block all IP access to the URL and whitelist only your IP (as long as it is static). I believe the free version of Wordfence lets you do this but check to confirm.

• This reply was modified 3 years, 10 months ago by jamieschmid. Reason: didn't notice he already had WF

Those are most likely spam bots trying to access wp-admin — which presumably is the reason you’ve changed the login URL in the first place? It seems the plugin is working as it should.

Right now they’re just showing in Gutenberg in the default custom fields area. Just like before 5.0, that location is “below” the editor (even if it doesn’t really look like it).

You can set the metabox to display above the editor, below the editor, or in the sidebar in Gutenberg as well. However, just like ACF has always worked, you will still have to manually call all the ACF fields in your template file.

If you want to be interspersing ACF fields with different Gutenberg core blocks, and even giving your user the ability to move them around themselves, you will be able to do that with ACF v5.8.0 using the ACF blocks function. https://www.advancedcustomfields.com/blog/acf-5-8-introducing-acf-blocks-for-gutenberg/

However that version is still in beta and we don’t have an official release date yet. You can download the beta though and test on your staging site in the meantime!

• This reply was modified 5 years, 10 months ago by jamieschmid.

Have you tried the relationships field? Create a relationship field for Function posts, and match it the Persons CPT. That will give you a dropdown list of all Persons posts to pick from on the Functions post, and then you can do an ACF relationship query (basically a nested post query) to display and work with it dynamically.

If that doesn’t work you might consider looking at the Post2Posts plugin as it creates relationships between content types in a slightly different way that may work better for you.

Out of curiosity, is there a functional reason you’re using ACF fields for the title and body of the Functions cpt, instead of post_title and the_content?

• This reply was modified 5 years, 10 months ago by jamieschmid.

Hi, it appears to still be using my email. Moving this to the #forums channel on Slack for resolution, thank you for your help!

• This reply was modified 6 years, 3 months ago by jamieschmid.
• This reply was modified 6 years, 3 months ago by jamieschmid.

Ok, thank you! kinda sad to see my 2014 WCSF attendance deleted but that’s la vie!

The user I need deleted is “hellojamie” please.

Are you able to access the Admin? Try deactivating all plugins and see if it comes back online. If not, switch to a default theme like twentyseventeen and see if that fixes it. If not, check out this post for more in-depth troubleshooting: How to fix the 500 Internal Server Error

Also: If you cannot access the Admin, or if you are on managed WordPress hosting, and/or are not familiar with FTP, you should contact your host or WP support person for help. The very minimum they could do is restore a recent backup for you and you can try again ??

• This reply was modified 6 years, 5 months ago by jamieschmid.
• This reply was modified 6 years, 5 months ago by jamieschmid.

I assume you’ve already done this, but in case you haven’t, update your Gutenberg plugin to the latest version. As it’s still very much in Beta, many bugs and features are still being ironed out, but these issues you encountered should have been fixed in updated releases of the plugin. If you still have the issue, deactivate all your plugins and switch to a default theme (like twentyseventeen) to see if it’s a conflict with a theme or plugin.

In general, CSS in the head of your HTML will be put there by either a plugin or theme, by hooking into the wp_head() action hook. As to where the CSS is being SET, that could be many places: the Customizer, plugin settings, separate theme settings, etc. Currently, Gutenberg block styling (even for shared blocks) is added as inline CSS on the exact element you are styling so what you are seeing probably isn’t an output from Gutenberg.