Forum Replies Created
-
Posts
-
Daniel Bachhuber is no longer involved with Co-Authors Plus, and none of the other developers have been responding in the support forum for many months. My guess is that since Automattic took it over co-author functionality is going to show up in Jetpack at some point, and these plugins will languish unless someone else forks them.
The Genesis plugin for Co-Authors Plus is probably the more relevant place to seek support, so I posted my question there, but I see the developer, Jean Galea, has not been responding in those forums for many months either.
In my experience Co-Authors Plus has never worked very well, and this is largely because there is no standard for handling authors in WordPress themes. Every solution is essentially a hack because the WordPress core forces an inadequate de facto standard on us where Users=Authors. Without the ability to map more than one user to a piece of content and no way to quickly create new "dummy" users without email addresses or access rights, it would make the most sense to standardize non-user authors as a custom content type or a taxonomy as the Byline plugin does. This is an area where a well-supported solution would likely be well-received and profitable.
Hrrm, thanks.
Genesis support tells me that stickies are not generally supported in category archives by any themes, Genesis or otherwise. I guess I was mistaken about the typical way the sticky status is implemented? -- I've never actually used it until now.
Thanks, I'm familiar with the method and that plugin; I just wanted to know if Genesis themes typically use stickies for front page promotion only.
What I'd actually like to do at the moment is load sticky posts in the Genesis Featured Posts Widget. I haven't seen alternative post widgets as comprehensive and clean as GFPW. Only a few let you select sticky posts. Can't think of a good way to do this without forking GFPW.
@bamajr I'm the "samaritan" who gave Genesis to David while you were kicking dirt on him on Twitter and his forum. David scheduled a screensharing session a few days later, so we could have a pro/con discussion of the plugins. He also helped me diagnose other glitches I ran into and pointed me to gists and documentation to help me out with some questions I had. I'm quite happy using the Leads plugin now with Genesis themes handling landing pages, but given the work they are putting into it I expect the LP and CTA plugins will be in a lot better shape soon.
@Summer Studio Press, Woo Themes, and maybe a few others have such a large market the way they do things becomes standard and has at times influenced the WP core itself in big ways. Plugin developers have to accept that. What is "standard" in the WP core is often legacy stuff that should make you want to laugh or cry, not get upset with theme frameworks that override it; that is their job. That doesn't mean they can do no wrong or that their way of doing things won't cause problems for you. For example, I've never understood why a framework + child themes is seen as a good idea rather than parent themes that use a framework (like Hybrid). Genesis may "do things the WordPress way" by using child themes, but this leaves you no way to substantially modify the theme that will not become an obstacle to future upgrades.
I understood your point the first three times you shared it in two forums and on Twitter.
You're not helping by making it personal, by increasing the volume and repeating yourself. There's no need to browbeat people. They have names, and it's not hard to find out where they are. You don't have to let them on your server, but don't suggest they might be crooks. None of this will help motivate making plugins work better with Genesis.
There's no need to point fingers yourself. Trying to stir up some drama isn't funny; we're all just looking for solutions.
Thanks for posting the filter that needed to be removed. Was this from Genesis support?
Looks like we posted at the same time @bamajr.
David's fix results in a 502 Bad Gateway on the frontend with WP Engine/nginx.
To be more specific, according to David Wells (one of InboundNow's developers), the problem is that "Genesis does some non wp core actions to the title tags."
InboundNow Landing Pages uses wp_title() to generate the page title. If Genesis has a filter acting on wp_title() it seems to be doing so in a way that results in duplicate, nested title tags in the HTML output. This could be fixed by disabling the Genesis title filter just for the Landing Page CPT created by InboundNow Landing Pages.
It looks like people have reported this problem with other plugins in the past:
http://brimosoft.nl/2012/02/28/what-i-dont-like-about-the-catalyst-and-genesis-framework-themes/More from David:
https://github.com/inboundnow/landing-pages/issues/75
