Forum Replies Created

Viewing 12 replies - 1 through 12 (of 12 total)
  • Thread Starter oiler

    (@oiler)

    Well, I didn’t test my suggested logic before posting… but the point stands… there should be a better option for fallback if the queue is left empty. Maybe have ‘posts_per_page’ use the default instead of -1 ?

    Thread Starter oiler

    (@oiler)

    It’s a theme we’re building for a newspaper’s blog.
    We’re definitely sold on using the_excerpt for standard post-formats but we’re trying to cover our bases for what we’ve seen from a wide variety of bloggers.

    It seems the problem we’re having comes from the lack of parameters / args available for the_excerpt()

    Thread Starter oiler

    (@oiler)

    Exactly, I get all that.

    And as theme developers, we are deciding to use the_excerpt()

    But nothing is stopping a blog author from adding <!–more–> into their post.

    Here’s a link to a screenshot example of what I’m talking about.

    http://s164.photobucket.com/albums/u28/oiler1039/?action=view&current=Screenshot2011-10-31at112409AM.png

    The first post, ‘Bears’, is using the_excerpt() and we are customizing the read more text and length.

    The second post, ‘War & Peace’, is also the same code as ‘Bears’ but in the post editor, the author has added <!–more–> after the first sentence. So you see a shorter excerpt and no read more link.

    Hope this helps clarify what I’m getting at.

    We want to automate excerpts for standard post-formats, but if the author goes in and adds their own (using <!–more–>) we’d like to at least standardize the Read More link.

    Thread Starter oiler

    (@oiler)

    Thanks for your reply, but that function only works when using the_content()

    But when using the_excerpt() it just cuts the post off and adds no read more.

    Please remove inline styles from the plugin’s $tweetHTML variable!
    Please and thank you!

    Thread Starter oiler

    (@oiler)

    Yeah, I did leave a comment on his plugin page but it wasn’t answered. So after waiting an appropriate amount of non-stalking time, I wrote him an email yesterday.

    Looks like I got what I needed and am hacking his plugin to be applicable to our needs.

    Thread Starter oiler

    (@oiler)

    That’s sort of a case where you’re kinda using MultiSite for the wrong thing.

    MultiSite is for separate, not connected, sites. Which is why it’s made the way it is. And why you’re going to have a headache.

    Trust me when i say that these people treat their blogs as separate, not connected sites!

    Either way, how we set it up doesn’t expose the fact that the is_site_admin boolean doesn’t offer the granular capability options that it probably should.

    Thread Starter oiler

    (@oiler)

    Yes, because if you let per-site admins install themes and plugins, they can destroy your whole network. It’s a huge risk, especially on an open network.

    Agree 100% and that’s actually why we’re investigating all of this.
    We don’t want site admins to be able to install themes and plugins but they DO still need to be able to manage/add blogs and users across the whole Network, not just for a single blog.

    The scenario is…. a newspaper has a set of blogs that run on a Network.
    The newspaper’s dev team manages the blogs. They are the Founder and do all the heavy lifting. But the newspaper’s editors and managers handle all the day to day add blog, edit blog, assign users, etc. We, the developers want to give the editors and managers that ability but don’t want them also installing plugins and themes.

    So these managers and editors need to work across the Network as site admins, but can’t be allowed to do things that the developers can do.

    Thread Starter oiler

    (@oiler)

    Right… that may help.

    I understand the Network vs Site clarification… but when you’re in a Network, certain admin capabilities – like install plugins or themes – get sucked up out of the Site admin and into the Network admin.

    Specifically, we’re looking for something that can work similar to how the Founder works in phpbb. A super admin over all super admins.

    The Founder, then in this scenario, is able to do everything the super admin can now do. And the revised super admins have the ability to manage the Network blogs and users (add, delete, assign, etc) but not install-edit-update plugins or themes or update core.

    Thread Starter oiler

    (@oiler)

    That’s fine, but why not offer capabilities for the super admin inside at least in sitemeta?
    It’s not even something that’s pluggable. The ‘is_super_admin’ function is in includes/capabilities so it’s purely a on/off switch.

    This plugin comes close, http://ww.wp.xz.cn/extend/plugins/extended-super-admins/ , but is buggy and just can’t pull off what we need it to.

    Anyhow, thanks for responding.

    Thread Starter oiler

    (@oiler)

    Yes I was. And I later found it.
    Much to my disappointment, there doesn’t seem to be anything capabilities assigned to the super admin. It’s just a boolean yes or no. Why not make it a part of the regular Roles.

    Thread Starter oiler

    (@oiler)

    wp_sitemeta table

    site_admins meta_key

Viewing 12 replies - 1 through 12 (of 12 total)