[John Hockaday]

Hi there.

I tried to follow the instructions below but as soon as Template, Customise is selected – th attached screenshot shows what appears. A blank screen

I took a look at this page, https://hhdba.com/member-directory/

The “logos” were uploaded as images (photos)

You need to change this.

Navigate to the Connections : Templates admin page and click the Customize button for cMap. The page will reload with the Customizer on the left and a preview on the right.

Click the back arrow on the upper left of the Customizer and then click the Image panel. Select the Photo as the Image Type.

Click the back arrow on the upper left of the Customizer and then click the Bio Image panel. Select the None as the Image Type.

Now, click an entry name in the preview. Any entry name it does not matter. The preview will load that entry’s profile detail view. Make the same two changes again. This needs to be done twice because the list view and the profile detail view are configured separately to allow greater flexibility in customization.

Thanks

John

Attachments:

You must be logged in to view attached files.

[Steven Zahm]

@ John

Have set a directory home page?

Are all the Connections addons, extensions and templates up to date?

Can you please try:

• How do I check for a theme conflict?
• How do I check for a plugin conflict?

Also, it is possible the memory allocated to PHP is being exhausted. The Customizer does require more resources.

Here’s is a blog post which covers several ways to increase the memory. Which method will work depends on the web host. My suggestion is to start at the top of the list an work your way down.

http://dailyblogging.org/wordpress/increase-wordpress-memory-limit/

Please let me know the results.

[John Hockaday]

Hi Steven

I’ve upped the memory to 512Mb

I’ve updated all plugins and modules – issue persists

I’ve gone back to 2016 Theme – issue persists

I’ve disabled every plugin – issue persists

One thing to note is that the same issue exists when I go to customise the Divi Theme Customiser – it’s the same screen (attached) as when I click on Templates, Cmap, Customise.

With Connections disabled, the Divi Customiser loads normally….

I’ve created a Staging site https://staging1.hhdba.com and an Admin login which should get to you by email

Thanks :-)

John

• This reply was modified 6 years, 8 months ago by John Hockaday.

Attachments:

You must be logged in to view attached files.

[Steven Zahm]

@ John

re: With Connections disabled, the Divi Customiser loads normally….

Well now, that’s odd because Connections does not load anything when the theme loads its Customizer.

re: I’ve created a Staging site https://staging1.hhdba.com and an Admin login which should get to you by email

Thanks, I’ll take a look when I receive the login details.

[John Hockaday]

This reply has been marked as private.

[Steven Zahm]

@ John

The logins do not seem to work. Could you please verify them? Also, you might want to enable the private reply option when replying back with valid login details otherwise you are posting them publicly.

[John Hockaday]

This reply has been marked as private.

[Steven Zahm]

@ John

I didn’t fix it, but it works now…

The page was actually loading fine, there was a fatal javascript error occurring which preventing the page preview and the Customizer from running.

It was not Connections, but the Connections Widget Pack. Specifically, I tracked it down to the code which registers the Connections Widgets Sidebar.

As soon as I remove the code, which is standard code WordPress code, nothing “funcky”, the page loaded fine.

So to hopefully track down the issue I let the sidebar be registered.

I wondered what would happen if I added a random widget to the sidebar. Success it worked. So I remove the widget, and, now it works without a widget it it too.

At this point I really have no clue why this happened. The only thing I know is the error was in the part of the core WordPress code removing “abandoned” widgets registrations (widgets added to a sidebar). “Abandoned” means, in this case, removing widgets which no longer exist (as would happen when deactivating a plugin which had widgets and its widget were active on a sidebar) assigned to an existing sidebar.

I can only guess at this point something was saved to WordPress which which triggered the error when the Widget Pack was activate.

If this happens again, please let me know. I would love to dig deeper into exactly what was happening.

[Author]

Posts