Guust

You have added this to the one page only and not the other page:

.gd-read-more-wrap {
    display: none;
}

I changed the video shortcode in the detail template.

To add any of the custom fields you have chosen to add to the sidebar, try using this shortcode: [gd_output_location location=”detail”]

Please post the URLs of the relevant pages and WP admin details in a private reply so we can check if you like.

Thanks

Firstly, layout=”3″ is not the same as listview, that would be layout=”1″.
The same shortcode should show the same on different pages unless you have created more than one GD Archive Item template or are hiding things with CSS.
Please post the URLs of the relevant pages and WP admin details in a private reply so we can check if you like.

Thanks

1. Every GD version has a “Show in what locations” option for each custom field. In V2 it is called “Show in extra output location”.
Because you posted in the V1 section, we assumed you were running V1.
This is the V2 documentation for that option: https://wpgeodirectory.com/docs-v2/places/custom/#show

You possibly need to add the GD Output Location widget to your Detail page sidebar, but that depends if you are using V1 or V2.

2. In V2 you use the shortcode [gd_loop_paging], see https://wpgeodirectory.com/docs-v2/geodirectory/design-elements/#gd_loop_paging

If we need to check your settings, please post your URL and WP admin details in a private reply and we will have a look.

Thanks

This is the error you have:

You have exceeded your request quota for this API. See https://developers.google.com/maps/documentation/javascript/error-messages?

You will need to add billing to your Google API project.

Thanks

Please try renaming the slug for the GD Search page to something else than “search”. For the moment you are having 2 pages trying to use “/search/” as the URL part.

Please post your URL and WP admin details in a private reply if we need to have a look at your settings.
Thanks

That looks like a little bug. There should not be a comma after “in” when using the %%in_location%% tag.

This tag has the same problem:
%%location%%

Thanks for reporting, we’ll get this fixed.