Marc Dahmen

Thanks for the pro tip, Ashley. Worked like a charm.

Thanks for the reply and info, Ashley.

Do you know what settings in iThemes I should be adjusting or making to allow your plugin to use the REST API?

Thanks for the reply, Abid. I updated Elementor Pro to 3.2.0 without any issues regarding your plugin. Everything works as expected.

I think I figured this out.

I changed my Custom Commands code to:

Here are my Custom Commands codes:

“columnDefs”: [ { “className”: “mobile-p”, “targets”: [0] }, { “className”: “tablet”, “targets”: [ 0 ] }, { “className”: “desktop”, “targets”: [ 0, 1, 2, 3, 4, 5, 6 ] } ]

That seems to do the trick nicely.

Many, many thanks TobiasBg!

TablePress 1.12 solved all my problems. I can now edit the table and it collapses as expected with TablePress Extension: Responsive Tables. Also, my navigation has restored its drop-down menu function on the page on which my TablePress table resides. And I can now properly edit that page within Elementor Pro.

I am good to go.

Also, I just noticed your other plugin TablePress Extension: Responsive Tables is no longer collapsing my TablePress table in responsive mode.

Thanks, Ashley.

I ended up deleting the transients from your plugin and the archive then expanded the current month as expected.

One more question, Ashley.

When I first installed your plugin and created 8 Blog post test for July, your plugin automatically expanded the month of July so all the posts were showing. That is what I want and have the Expanding Archives widget set to “Automatically expand current month”.

However, after several days but before August arrived, the month of July went into “collapse” mode and wouldn’t automatically expand on page load.

Is there some kind of time limit set by the transient that initially sets the current month to “expand” but only after a certain period of time and then it collapses?

Hi Ashley,

Thanks for the response and for the pro tip. I installed Transient Manager and deleted the transient for your plugin. Now my posts for August are showing.

And thanks for the explanation as to why they weren’t showing in the first place. Makes total sense for a server/usability standpoint. We definitely don’t want it querying on every page load.

For purposes of my development site, however, the use of the Transient Manager plugin is key so I can quickly see how your plugin integrates with my site as I’m developing it, instead of having to wait 24 hours.

Thanks again!

Thanks for the reply, Tobias. Glad to hear I solved it the correct way. And it’s working flawlessly now.

I figured it out. I had the wrong targets set for mobile-p.

I changed:
{ “className”: “mobile-p”, “targets”: [2,3,4,5,6] }

To:
{ “className”: “mobile-p”, “targets”: [0] }

And now my table is collapsing appropriately. Let me know if that was the wrong solution.

Thanks.

I’m having the exact same problem. Running WordPress 5.2.2, on a server running PHP 7.1.30, with Materialis Pro 1.0.178, and Materialis Companion 1.2.125.

The site works fine on my localhost, but as soon as I push the content to a staging site, the Customizer won’t load.

This is detrimental, as all the pages of my site are using the Materialis Companion plugin. If I turn that plugin off Customizer will function, but I lose all the functionality that I need from the Materialis Companion plugin.

I’ve read that other people are having the same issue with Mesmerize, which is a theme created by the same folks as Materialis, and Mesmerize also has a companion plugin authored by the same person who created Materialis Companion.

Were you able to find a solution? I’ve tried numerous things, including increasing the memory allocation to PHP, enqueuing the parent theme before the child theme in functions.php, and adding scripts to htaccess, and creating a php.ini file.

No luck so far.

• This reply was modified 5 years, 5 months ago by Marc Dahmen.
• This reply was modified 5 years, 5 months ago by Marc Dahmen.

Thanks, Jeremy. Jetpack 4.8.2 has solved my module loading issues. Thanks for the quick turnaround.

Ryan,

I did fill out that form shortly before finding this thread and posting my experience. You should have all my contact info and error descriptions. Let me know if you don’t.

I ended up manually rolling back to Jetpack 4.7.1 and all my modules are now loading. Still running WordPress 4.7.3, so Jetpack 4.7.1 appears to be compatible.

Just thought I’d put that out there in case it helps anyone else.