Forum Replies Created

Viewing 15 replies - 76 through 90 (of 163 total)
  • Hi valuser,

    I think I have an answer for you: here’s how we can bring back categories as they were in versions prior to 1.4.0:

    http://wpguru.co.uk/2012/04/how-to-bring-back-post-categories-in-p2/

    I think you’re asking too much from the system as it is. Groups as such are not part of WordPress or P2 which makes it difficult to filter posts by user groups.

    You could try and install a WordPress network in which you’d run several instances of P2. All users would be registered on the network, but only certain users would have access to certain P2 instances.

    So you’d have yourdomain.com/site1 and users 1 and 2 could read and post to it, and yourdomain.com/site2 which can only be accessed by users 3 and 4. User 5 however may have access to both sites.

    You can always look into BuddyPress which has that functionality. Be warned though that BuddyPress is a rather complex beast with its own quirks. It supports posting from the front page, friend connections, groups and many other things without the need for users to go to the backend.

    It’s a free plugin, download it at http://BuddyPress.org

    Plugin Author Jay Versluis

    (@versluis)

    It’s got me stumped, I haven’t seen this error before and can’t reproduce it at my end. cron.php is a WordPress core file.

    Tell me, are you calling a real cron job from your server or are you relying on on the WordPress Cron function (i.e. not added anything special to your setup)? Have you upgraded from an earlier version?

    Hi there,

    take a look at the post-form.php file. In it you’ll find this block of code somewhere near the top:

    <div id="postbox">
    		<ul id="post-types">
    			<li><a id="status"<?php if ( $post_type == 'status' ) : ?> class="selected"<?php endif; ?> href="<?php echo site_url( '?p=status' ); ?>" title="<?php esc_attr_e( 'Status Update', 'p2' ); ?>"><?php _e( 'Status Update', 'p2' ); ?></a></li>
    			<li><a id="post"<?php if ( $post_type == 'post' ) : ?> class="selected"<?php endif; ?> href="<?php echo site_url( '?p=post' ); ?>" title="<?php esc_attr_e( 'Blog Post', 'p2' ); ?>"><?php _e( 'Blog Post', 'p2' ); ?></a></li>
    			<li><a id="quote"<?php if ( $post_type == 'quote' ) : ?> class="selected"<?php endif; ?> href="<?php echo site_url( '?p=quote' ); ?>" title="<?php esc_attr_e( 'Quote', 'p2' ); ?>"><?php _e( 'Quote', 'p2' ); ?></a></li>
    			<li><a id="link"<?php if ( $post_type == 'link' ) : ?> class="selected"<?php endif; ?> href="<?php echo site_url( '?p=link' ); ?>" title="<?php esc_attr_e( 'Link', 'p2' ); ?>"><?php _e( 'Link', 'p2' ); ?></a></li>
    		</ul>

    Here you can change the labels and categories that each button posts into. Hope this helps.

    Same here Michael,

    I’m using P2 1.3.3 and Firefox 10.0.2 and all runs fine. I’m on a Mac, wonder if that makes a difference.

    I think media uploading from the front page works for pictures and other media. It uses the standard WordPress media uploader – there’s a button in the top right of the posting window.

    That’s for posts and status updates only though, not for comments. I agree that letting commenters upload media would be an extremely cool feature, but since ordinary WordPress comments don’t allow for this I doubt it’ll be something that can be implemented.

    You can reference people just like on Twitter: @userhandle

    P2 will then create a link to all mentions, works great – just make sure you’re using Pretty Permalinks for this feature (set it under Settings – Permalinks to anything other than the default).

    Hi yuval83,

    add this to the bottom of your style.css file:

    .avatar {display: none;}

    It’ll remove the avatars, however leaves a gap on the left hand side where they were.

    … and this my friends is one of the most comprehensive guides you’ll find on the web about this extremely complex topic.

    Loving your work, Luke 😉

    Thanks for sharing, Luke! You’ve hit the nail on the head: the default value for FcgidMaxRequestLen is the culprit, it’s just too low by default for many applications and hence those upload errors.

    Adding something larger like you suggested solves these issues. For servers without such a nice control panel, this value can be changed in httpd.conf (the Apache configuration file). On CentOS this is in /etc/httpd/conf/httpd.conf.

    Once tweaked, restart Apache with ‘service httpd restart’ from the shh prompt.

    Plugin Author Jay Versluis

    (@versluis)

    Yes actually, I was just discussing this with someone yesterday 😉

    I’m thinking of Dropbox and Amazon S3 right now, but I’d like to add more services to the mix once the plugin is more solid.

    My biggest problem is that I’m not a PHP coder – I’m learning as I go along, but it doesn’t come easy to me. I’m ore like the “visionary” who would like to see this thing come to life.

    Plugin Author Jay Versluis

    (@versluis)

    Hey Bret,

    Sorry for the delay in pushing out the beta, life just got busier than I had expected. Bear with me 😉

    Plugin Author Jay Versluis

    (@versluis)

    Hi psalamon,

    Did you use the automation feature? There is an option which creates a new snapshot every two minutes, this is meant for testing. Was that switched on by any chance?

    Who are you hosting with?

    Hi Ron,

    think we’re on the same mission here – I too would like to know what’s the better option in WordPress. Here’s what I know:

    Apart from speed, if you run PHP as FastCGI (or CGI) the advantage is user isolation. Let me explain:

    Often enough you have to tweak file permissions because WordPress runs as the Apache user instead of the user who owns the files on your install. So a quick 777 will fix it – but that’s no good for security.

    The other option is to have files and folders owned by Apache, but that makes finding an exploit more difficult because 1000 sites could be owned (and compromised) by the same user i.e. Apache. In fact, if WordPress needs a new folder it will be created as owned by Apache, if you run PHP as Apache Module.

    So if you run PHP as FastCGI then it’ll be created as the “your user” rather than Apache. It also means WordPress has write permissions to all files because it’s executed as “you user” rather than Apache. All that together means FastCGI – on paper – sounds like the dream solution.

    However, the drawbacks are in fact your (and my) observations if you do that. I also get numerous spurious 500 Internal Server errors, and I’m experience upload problems with files larger than 300kB (despite how high my PHP memory limit is). I’m using Plesk 10.4.4 instead of cPanel on a dedicated server.

    I’ve written a post about my initial observations here: http://wpguru.co.uk/2012/02/the-problem-with-running-php-as-fastcgi-application/

    Food for thought. To make things work smoothly, I’m currently using the Apache Module option – but I FastCGI would make my life so much easier.

    Plugin Author Jay Versluis

    (@versluis)

    Hi Bret,

    Thank you for your feedback, I think something since WordPress 3.1 is causing this strange behaviour. Next week (after WordCamp Miami) I will have some time to look into this and finally give Snapshot a well deserved overhaul. I have a long list of things I want to do but this one is at the very top of the list.

    I’d love your input on the next beta release, let me know if you’re interested in giving it a spin before general release.

Viewing 15 replies - 76 through 90 (of 163 total)