Saqib Ali

I had a similar issue, so I changed browsers and voila it worked again. The browser I was having difficulty with was EDGE.

Weird can’t seem to find that <p> element.

Appreciate the help though @sterndata thank you very much!

Thank you @rossmitchell, I’ll just update the style sheet, for now, I just like seeing able to see live edits whilst I’m changing the CSS.

It’s ok, worked it out, adjusted height and width settings, duhhh

fyi, I’m embedding the timeline into my primary sidebar.

This suggests they’re on to it https://salferrarello.com/catchable-fatal-error-argument-1-passed-genesis_admin_cpt_archive_settings/

Turning off the DS-CLI developer plugin worked like a charm, cheers @damiansaunders

Cheers

Appreciate the info guys.

The developers have got back to me and have advised on taking the PHP route. Let’s see how long this rabbit hole goes on for…

I’ll be taking the PHP approach to insert HTML into your navigation menu.

RE separating ARIA and touch functionality, the W3C site begs to differ –

https://www.w3.org/TR/wai-aria/states_and_properties#aria-haspopup

Strictly speaking the navigation menu is responsive for most mobile devices. I was wondering how people have tried to tackle the issue of touch enabled pc’s and navigation menus in WordPress.

For example if I had access to an index.html file on a non-cms website, I’d just include the html <li><a href="#" aria-haspopup="tru">About Us</a>

I targeted these divs also but unfortunately, it didn’t work:

div.span12.post-1658.post.type-post-status-publish.format-standard.hentry.category-uncategorized

div.row

div.span12

div.main-content

The theme is a bespoke one loosely based off the standard 2012 WordPress theme created by another designer

Thank you for replying Tara.

It’s fine, I’ve found the answer.

Hello everyone

I’m having the exact same problem did anyone find a solution to this problem??

Thank you