[detroitwidget]

Excellent! Thank you Brad.

[detroitwidget]

In WordPress 4.9, this is also a problem in the latest version of Chrome for Mac.

Searching a CSS file in edit mode only scans the viewport. Great. More improvements.

[detroitwidget]

Or, depending on your perspective, you could say it was a known issue with many Genesis child themes.

In any case, StudioPress doesn't seem concerned enough to fix it.

[detroitwidget]

You're not imagining things.

This is a known issue with several Genesis child themes (especially earlier versions) that rely on home page ID anchors. The problem is compounded by the latest version of Chrome (v61) which tends to render some scrolling anchors nonfunctional.

StudioPress has confirmed these issues, but to my knowledge hasn't issued an official fix.

You might try contacting support directly.

[detroitwidget]

Thanks.

[detroitwidget]

Interesting.

Victor - Where did you find this filter?

[detroitwidget]

Try:

https://wordpress.stackexchange.com/questions/220352/infinite-loop-after-genesis-theme-upgrade

[detroitwidget]

This is a known issue with Chrome 61 and has been confirmed by StudioPress. It may affect earlier versions of the following child themes (and possibly others) that rely on home page ID anchors:

- Altitude Pro
- Atmosphere Pro
- Cafe Pro

Updating the child theme may resolve the issue. If not, contact StudioPress support -- They were very helpful.

[detroitwidget]

If by "heading" you mean your site title, the simplest way would be to reduce the font size to 34px or less. See line 1042 in style.css:

.site-title {
    font-family: 'Titillium Web', sans-serif;
    font-size: 36px;
    font-weight: 700;
    line-height: 1.2;
}

[detroitwidget]

Thanks Victor.

The text widget "improvements" in WP 4.8 also remove all "i" tags, which are used in many Genesis theme setup guides to insert icon fonts. For example, the 6 panels in widget area 4 on the front page of the popular Infinity Pro theme.

https://demo.studiopress.com/infinity/

What a mess.

[detroitwidget]

You still need WooCommerce, but you won't need Genesis Connect any longer.

This may be incorrect. According to StudioPress support, the Genesis Connect plugin is still required.

[detroitwidget]

A "Genesis for Beginners" guide is available for download here:

http://my.studiopress.com/support/

[detroitwidget]

Welcome Jack.

I'm a big America's Cup fan and was mesmerized by the US team's comeback in 2013. It's a pleasure to meet someone involved in the event.

I'm not a millennial either. =8-)

Phil

[detroitwidget]

I recently updated to Infinity Pro v1.1.0 from v1.0.0. The new version created some odd front page behavior so I submitted a ticket to StudioPress support on Jan 28.

Infinity Pro has just been updated (as were a dozen other themes) to v1.1.1.

The latest version (1.1.1) seems to have fixed my issues. It may (or may not) solve the problems you are having.

[detroitwidget]

You appear to be using version 1.1.0 of Infinity Pro. Is that correct?

[detroitwidget]

Cemal,

I realize I'm a bit late to this conversation, but when you do a "search and replace" on the database, how EXACTLY do you accomplish this?

Some of the data (including domains and URLs) stored by PHP in the MySQL database is "serialized" and can be damaged by using a text editor (or similar) to do a simple search and replace. This can lead to all sorts of unexpected behavior.

[detroitwidget]

I see what you mean.

Something's not quite right on your home page. You may have somehow interfered with the "skip link" functionality.

For now, try disabling :focus in style.css (or the Chrome Inspector):

:focus {
    color: #000;
    outline: #ccc solid 1px;
}

Also, there's nothing magic about clicking the menu bar or browser address bar -- You're simply removing focus from the affected element. Click anywhere outside of front-page-3, it loses focus, and the text returns to white.

[detroitwidget]

Hi Alvin,

Are you using the Autoptimize plugin? If so, you might consider disabling it. That would make things much easier to diagnose. Besides, concatenating and minifying scripts should be a low priority at this point.

That said, I think Victor's correct, your solution lies in here somewhere:

.genesis-nav-menu .sub-menu:after,
.genesis-nav-menu .sub-menu:before {
    bottom: 100%;
    left: 50%;
    border: solid transparent;
    border-bottom-color: #000;
    content: " ";
    height: 0;
    width: 0;
    position: absolute;
    pointer-events: none
}

.genesis-nav-menu .sub-menu:after {
    border-width: 10px;
    margin-left: -10px
}

.genesis-nav-menu .sub-menu:before {
    border-width: 11px;
    margin-left: -11px
}

.genesis-nav-menu .sub-menu .sub-menu:after,
.genesis-nav-menu .sub-menu .sub-menu:before {
    display: none
}

I hope this helps.

[detroitwidget]

< Child themes are rarely, if ever updated. >

That may no longer be an accurate statement (if it ever was). The following five Genesis child themes had significant updates just two days ago:

Atmosphere Pro
Digital Pro
Infinity Pro
Smart Passive Income Pro
Wellness Pro

Updating child themes to better accommodate WooCommerce will become more and more commonplace.

As far as insight goes, there's plenty to be had by reading Brian Gardner's blog, his regular "StudioPress Notes" email messages, and the official Genesis Facebook page.

[detroitwidget]

Try a Google search for: Indirect modification of overloaded element of WP_Hook has no effect

There are a couple recent articles discussing a similar issue.

[Author]

Posts