Support

July 5, 2017 at 1:53 pm

Thanks, Josh.

I genuinely appreciate your response.

There is no specific feature to WP 4.8 I have, but I am experiencing some CSS issues and there is a suggestion that the issue might be theme related.
Also, I do find the Slider mechanism in Iced Mocha to be somewhat frustrating in that you are limited to 10 slides (normally not a problem but…) and that that it is fidgety to add events to slides and impossible (unless I’ve missed something) to reorder them.

I know that WP has been improving some of the coding and will be doing a major update to the editor (Gutenberg) soon. I am concerned that Iced Mocha hasn’t had an overhaul in a couple of years.

July 6, 2017 at 3:31 am

Hey Josh,

Again, Thanks for your considered response. I genuinely appreciate it.

I am not a developer so I probably lack the linguistic precision to explain my concerns so I’ll use lay-terms.

In short, I am worried that I will wake up one day and find that I have to urgently redevelop my site because it modernisation killed it.

On the presentation slider it is not possible to automatically/easily include events, pages, posts and other items such as categories. The only way to do this is via custom posts. In custom slides it is possible to search/select images from the WP library but including pages links requires copy/paste.

One cannot reorder slides. If an event expires or you need to ‘insert’ a slide the entire slide show may need to be redone. I don’t think I have EVER had more than 5 slides and don’t think I would need more… cue music with background echo of Bill Gates allegedly saying “I don’t think anyone will ever need more than 640k….”

I don’t have any specific issues regarding CSS. I am trying to chase a CSS problem and Elegant Themes is saying it might be Theme related. I am not in agreement but I can’t rule it out either.

In the promotions plug-in/shortcode, if the text is beyond a certain length it breaks the design a bit.

It is hard for a non-developer to style additions such as a search box. I have tried and failed many times to restyle the text in EE. Because I am not an expert if I change the font sometimes I ended up with some brutally ugly pages, forcing me back to the default fonts or using a kludge to include multiple themes on site, in order to improve/change the look of pages/posts. I really dislike the styling applied to posts and not all the html tags seem to be recognised in IM.

Gutenberg: Ignore that. I might have seen some ‘hype-y’ media thing that led me to believe that it is imminent.

My overarching concern is that the changes in WordPress, without Iced Mocha (IM) keeping up, will eventually break the site. As you know, WordPress is simultaneously simple and complex. When a problem develops it can be astonishingly difficult to pinpoint the cause when you have multiple developers pointing fingers in different directions.

My first site I developed myself. Including writing all the HTML/PHP coding to handle the payment system (a collection of variable sent to PayPal) and conditional fields. This was in 2004, a few years before I heard of WordPress.

I love the idea of Event Espresso, and I understand that a) my use is non-standard and b) there are many variables that EE Developers cannot control. Never the less, keeping things up to date can help avoid security and obsolescence issues.

Every year, I’ve been surprised (you’ll notice a pattern in the time periods of my support posts) because some change broke something.

July 6, 2017 at 6:58 am

Hey Josh,

This just came from Elegant Themes:

Hello,

It looks like it’s a problem in your theme. I just noticed that admin-ajax.php file cannot be loaded when your theme activated. It’s core WordPress file, so many things don’t work while the important admin-ajax.php file cannot be loaded. This happens even when Divi Builder is deactivated.

Also, you can try to open wp-admin/appearance/customizer and you’ll see the page won’t be loaded because of the error I described above. Can you please check the attachment below to see what exact I mean.

You can contact your host or theme support to ask about the problem and you can refer the to the screen shot I posted below.

Please let me know how that goes..

I can send you the screenshot at your request.

July 6, 2017 at 7:27 am

I added to following to .htaccess and it seems to be working.

<IfModule mod_headers.c>
Header set Access-Control-Allow-Origin “*”
</IfModule>

July 6, 2017 at 3:35 pm

CANCEL THAT

Everything was fine until I made my first edit.

Then back to the same problem 🙁

July 6, 2017 at 4:10 pm

whoops. I meant Fatal error: Class ‘EE_Registry’ not found in /home/hiphopin/public_html/wp-content/themes/iced-mocha-1.0.7/includes/widgets.php on line 175.

I cannot get to the IM widgets at all.

July 7, 2017 at 9:19 am

Hey, Josh.

The only thing loaded on my site is Divi Builder, Elegant Themes Support, and widgetkit. Widget kit was added after the error to see if there was anything, for any reason, that IM was relying on. A long shot but I needed to test this.

One important note. If I load EE4 this error doesn’t appear, HOWEVER, this was not an issue before. Previously I was able to disable EE4 and it had no apparent effect on the operation of IM. Maybe this is one of the things that ‘changed’?

July 7, 2017 at 10:23 am

Thanks Josh. That makes this all the more bizarre, unfortunately. I was hoping that that might be the issue but it obviously isn’t.

I am trying EE4 with other themes as a test to see if I rule in or rule out IM as the issue.

Once again, I genuinely appreciate your responses.

Omar

July 7, 2017 at 2:27 pm

Not 100% certain what you’re asking, Josh, but I’ll try. So far I’ve tested against the ‘Divi’ Theme, the ‘Big Easy’ Yoo theme, and against the ‘Twenty Seventeen’ Theme. The fatal error, above, does not occur under these three themes. It occurs if the IM theme is active but the EE4 plug-in is deactivated.

July 7, 2017 at 3:06 pm

Ahhh! I see.

No, I am happy to explain. It’s been nearly 4 weeks in total that I’ve been trying to solve a problem with Divi Builder that only occurs on this site. I manage several others and the main difference between them is that Event Espresso and Paid Memberships Pro exist on this site (hiphopinternational.co.uk) but none of my other sites.

Each time I’ve thought I found the culprit it’s proven to be a deadend or another latent problem that I only discovered because I was digging – such as this fatal error.

It’s frustrating as weeks have gone by and I feel no closer to solving the problem This fatal error and two other errors

Catchable fatal error: Argument 1 passed to EED_WP_Users_Admin::_connect_wp_user_with_contact() must be an instance of WP_User, boolean given, called in /home/hiphopin/public_html/wp-content/plugins/eea-wp-user-integration/EED_WP_Users_Admin.module.php on line 282 and defined in /home/hiphopin/public_html/wp-content/plugins/eea-wp-user-integration/EED_WP_Users_Admin.module.php on line 356

and https://hiphopinternational.co.uk/wp-admin/admin-ajax.php/?action=dynamic_styles

All seemed to point at IM. Which made me feel hopeful, hence my comment. Nothing negative about EE4, Just a hope that these errors were the “keys” and I finally found the culprit in IM.

This looks much less likely now.

July 7, 2017 at 11:49 pm

Thank You, Josh!

A new direction. Hopefully, this leads to a resolution.

You would have to see Elegant Themes about the ‘how’ but yes, Divi Builder can be seen as an add-on to the MCE (my way of looking at it, not theirs) and works very well on all my other sites… well, if you don’t mind the insane amount of ugly code generated.

The ‘Dynamic styles’ points to at least one place inside of IM

// Synchronizing the tinymce width with the content width
add_filter('tiny_mce_before_init', 'iced_mocha_dynamic_editor_styles', 10);
function iced_mocha_dynamic_editor_styles($settings){
    $settings['content_css'] .= ",".admin_url('admin-ajax.php') ."/?action=dynamic_styles";
    return $settings;

July 8, 2017 at 5:56 am

Please see my note above. For now, as originally suspected, Siteground (my host) have deermined the problem to be Divi and added SubstituteMaxLineLength 10m to my .htaccess

I want to thank you, Josh, genuinely for your patience in handling this mess that is potentially not to be yours at all.

I will test the site and get back to you if it continues to be a problem or let you know the issue is resolved. I will also download the 1.0.8 update. Thanks