[Gary Jones]

3) Instead of displaying the excerpt on archive pages (e.g. /blog/), she'll be displaying he full post content and then inserting a More tag (there's a button for it on the tool bar).

What you'll end up with is something like:

 

Blah blah blah...all this will appear on the archive page, and will end with a "Read more" (by default).

<!--more-->

This bit of the post is only shown when you click through to the single post - the Read more link will usually jump the page down to this point so the reader can carry on from where they were reading before they clicked.

 

One not-very-known tip, is that you can customise the "Read more" text for each and every post to make it more contextually enticing. Just add the text you want into the more comment tag:

<!--more Find out how this funny story ends-->

 

If you don't include a more tag, then the whole post content is shown.

Since the archive is showing the first part of the content, then the formatting is carried through as well.

You can change what the blog archive displays, via the Genesis Theme Settings.

---

WordPress Engineer, and key contributor the Genesis Framework | @GaryJ

[Gary Jones]

Bit of a hack, but add the selector:

.post-type-archive-portfolio .menu-item-107 a

to the highlighting ruleset.

---

WordPress Engineer, and key contributor the Genesis Framework | @GaryJ

[Gary Jones]

I think we're done here then - ultimately, it wasn't a change in Genesis created the issue, but a change in the child theme that had a created a different setup which a previous version of Genesis would also have responded to.

Thanks for continuing the discussion.

---

WordPress Engineer, and key contributor the Genesis Framework | @GaryJ

[Gary Jones]

I think we're done here then - ultimately, it wasn't a change in Genesis created the issue, but a change in the child theme that had a created a different setup which a previous version of Genesis would also have responded to.

Thanks for continuing the discussion.

---

WordPress Engineer, and key contributor the Genesis Framework | @GaryJ

[Gary Jones]

Also, "Search this website" is not in the .pot file, as I suspect that esc_attr__() got missed from the list of marker functions in POEdit.

---

WordPress Engineer, and key contributor the Genesis Framework | @GaryJ

[Gary Jones]

(re-opened so that Posh John / Bill can reply. Fellow Mods, please leave open)

---

WordPress Engineer, and key contributor the Genesis Framework | @GaryJ

[Gary Jones]

Bill,

> This change was poorly documented. You won’t find it anywhere in the release announcement for 1.9, but for existing customers with live sites to maintain, it’s an important issue.

If it's the change I'm thinking of (hence my question above), this change was made in 1.8.2 - looks like it got missed from the official announcement, but it is (now) present on (my) http://genesischangelog.com/1.8.2

The hiding of the Header setting when genesis-custom-header theme support is present has been since G 1.7.0.

---

WordPress Engineer, and key contributor the Genesis Framework | @GaryJ

[Gary Jones]

Posh John - what version of Genesis were you running before updating to 1.9.*? Was it earlier than the previous release of 1.8.2? (That's when the Header settings were made to hide when theme support for custom-header was present.)

---

WordPress Engineer, and key contributor the Genesis Framework | @GaryJ

[Gary Jones]

Something like api.studiopress.com/themes that returns JSON data of the SP themes, version number, last updated etc.?

---

WordPress Engineer, and key contributor the Genesis Framework | @GaryJ

[Gary Jones]

The thread pagination links are incredibly close together, making them tricky to use from a touch device.

Equally, the same could be said for the post moderation links.

---

WordPress Engineer, and key contributor the Genesis Framework | @GaryJ

[Gary Jones]

The main content of the home page is unviewable on an iPad.

---

WordPress Engineer, and key contributor the Genesis Framework | @GaryJ

[Gary Jones]

As much as an I'm an advocate for following the coding standards, they do leave some holes within common examples of code, which means that inconsistency is introduced as different coders fill those holes with their own preferences. Multi-line function call arguments is an obvious one. It also doesn't cover items in PHP that are introduced in a version of PHP later than the required minimum, which again leaves developers who make the minimum requirement of their code to be 5.3 or later end up with inconsistent coding.

My advice, would be to have PSR-2 as the common coding standard, except for where the WordPress Coding Standards explicitly define how the code should be formatted. A lot of packages and libraries outside of WordPress are tending towards PSR-0, PSR-1 and some to PSR-2, so for the sake of having those holes filled with someing, it makes sense to use a common modern standard from outside of WordPress.

---

WordPress Engineer, and key contributor the Genesis Framework | @GaryJ

[Gary Jones]

The profiles allow the addition of the usual WordPress links - Yahoo, Aim, Google Talk etc., but no Twitter? Could this extremely common one be added, and be automatically shown on the profile page?

---

WordPress Engineer, and key contributor the Genesis Framework | @GaryJ

[Author]

Posts