csloisel

I feel like you may be adding mystery where there really isn’t any.

1. Add the custom fields
2. In the template: Get the field values
3. Display values as desired.

Fields aren’t displayed automatically because there is no way to predict how a developer wants to handle or display values. Getting values depends on the options framework but ACF is pretty straightfoward: See the docs here. Use get_field() for each field then output the value as desired.

If you are inside a WP loop you don’t have to specify the post id, it will use the current global post setup by the loop. Outside the WP loop you should specify which post you want to retrieve the value of.

Obviously the output will require some basic knowledge of html, css, php, and WP templating; You are, after all, creating a custom template. But if you know exactly how you want to display the data it shouldn’t be difficult to figure that part out.

It’s being thrown because WP is trying to get the height of an attachment and it is returning 0.

The error may be thrown by a core file but that doesn’t mean it’s caused by a core file, it’s most likely initiated by the theme or plugin. Since we can’t debug your theme your best bet is to contact the developer for support. If your theme is no longer supported and you want to debug, you would need to check your server error log or enable stack trace error messages. It’s also worth noting that “Warnings” are pretty harmless errors and probably won’t cause any critical issues. I usually recommend turning off debug to prevent those on live production environments and only keep them on development environments.

Look at your developer console, your javascript is throwing fatal errors. Try fixing those and see if it works.

If they show in the admin, that would indicate a theme, plugin, or configuration change. You can try to narrow it down by disabling plugins one by one and switching to a default theme to see if the problem goes away.

Are you doing this on a template or in pasting this in the content via the editor? The shortcode may work in the editor, but not in the template. Even in the editor, it will probably only work outside a link. Try doing this instead: paste the shortcode on a new page, then add a link to the new page in the menu.

• This reply was modified 7 years, 12 months ago by csloisel.
• This reply was modified 7 years, 12 months ago by csloisel.
• This reply was modified 7 years, 12 months ago by csloisel.

It’s tough to say without seeing the code and inspecting the page. Are there any relevant errors in the developer console?

Do the posts show in the admin, or is there only one there too?

Try <br/> instead of </br>.

You need to contact the theme developers for support. Forum volunteers can’t offer support on paid or commercial themes, and the developers will be better able to assist.

You can’t use a shortcode as a link target, you need to use a url. Why can’t you just use the menu editor to add the link you want?

Is it possible they aren’t enabled in the screen options?

There is not enough useful information in that message, to be able to advise we would need to see the code that initiated the error, not the code that threw the error. Furthermore this is just a warning, and is non-critical; It’s usually best to suppress non-critical errors on live production sites.

• This reply was modified 8 years ago by csloisel.
• This reply was modified 8 years ago by csloisel.

Search your theme and plugins for redirects, I’ve seen this a few times before, and it’s probably intentional functionality to keep users on the front-end.

I would search for an enhanced post list widget plugin that supports sticky posts. I haven’t used any before so it’s tough for me to recommend one, I would just try a few out and see if you can find one that works for you.