ivovic

perhaps what you need is a contact form, which will just email instead…

it’s not exactly what you want, but it’s easy. If you need to use that regularly, and it should be accessed by multiple people, then make a gmail account specifically for the purpose, so you can all dive in there and access the mails.

you mean this question? http://wordpress.org/support/topic/177494?replies=9

the only thing you did wrong was misplace your thread 😉 – click the word “member” under your name here, or the “view your profile” link in the blue section up there ^^^ to find all the threads you’ve participated in.

if you want either of those things on pages, then you’re just not doin’ it right.

use posts. put them on pages if you need to, but use posts.

just to let you know… I’ve managed to halve the amount of spam on my blog by ip-banning the major repeat-offenders. It is effective, but it’s not super-effective and you have to keep an eye on it.

not by default… you might find a plugin to do that, though.

you could code it reasonably easily in the template – based on custom fields, for example. How’s your PHP?

http://wordpress.org/support/topic/176345?replies=3

wordpress user-level security is not really intended for this sort of thing, but it can be done fairly well, as long as you’re not doing it for the pentagon or something… as I said, it’s fiddly, so you really have to want to use wordpress, because other CMSs make this a lot easier. Of course, once it’s done, it doesn’t need doing over and over.

keeping in mind, this is a hack in progress still…

using one of the many plugins that allows you to specify additional meta fields for your users (I’m using register plus), specify a field called ‘company’

You can then use that to determine which categories that user will have access to.

I also suggest installing the Role Manager plugin, so that you’re not relying only on a text field for your security – instead, you’ll have to give each new user not only a company name in their profile, but you’ll also have to assign them a new ‘ability’.

In my case, I’ve called that ability “access customer portal”.

in your theme’s functions.php, put a little helper function which takes the company data and works out which category IDs your customers should have access to.

function get_companydata($company_name = '') {
  if (empty($company_name)) {
    global $user;
    $company_name = get_usermeta($user->ID, 'company');
  }
  $cleanup = array(' ','-','_','\'','+','#','@');
  $slug = strtolower(str_replace($cleanup,'',$company_name));
  foreach(get_categories('hide_empty=0') as $category){
    if("$slug-privatecat1" == $category->slug) $company->privatecat1 = $category->cat_ID;
    if("$slug-privatecat2" == $category->slug) $company->privatecat2 = $category->cat_ID;
  }
  if ($company->privatecat1 && $company->privatecat2) return $company;
  else return FALSE;
}

this will take the company name and sanitize it, so if you enter “Joe’s Seafood” in the company field, it will turn it into “joesseafood”. It will then run through your categories and find the one’s you’ve created for this company, with slugs like “joesseafood-privatecat1” and “joesseafood-privatecat2”, and will pull the IDs of those categories for use later.

complicated? naaa… lets move on.

now make yourself a page template for your customers… assign it to a page like… oh I dunno… /customer

put this in it:

<?php
  global $user;
  $user = wp_get_current_user();
  $company = get_companydata();
  if ($company && current_user_can('access_customer_portal')) :
?>

   [ put your get_posts stuff in here,
     and finish the template with: ]

<?php else : ?>

   [ put the code for your favourite
     login-form plugin here, because whoever
     sees this either doesn't have a company
     specified or is not logged in. ]

<?php endif; ?>

This uses the previous function to pull the company data, and checks whether the current user has the appropriate privileges to view the page.

If so, the page is displayed, if not, they’re presented with either an error message of your choice, or a login form… or really anything you like in that last bit.

now, in that top section of your template, you can use get_posts or query_posts to pull posts from a specific category into the current view.

where you would normally hard-code a category ID, here you can use $company->privatecat1 (you’ll call it whatever you like instead of “privatecat1” to return the ID of the category corresponding to the company.

so now your template looks like:

<?php
  global $user;
  $user = wp_get_current_user();
  $company = get_companydata();
  if ($company && current_user_can('access_customer_portal')) :
?>

  <?php
    $readposts = get_posts('numberposts=10&category='.$company->privatecat1);
    foreach ($readposts as $post) : setup_postdata($post);
  ?>
      <div>
         <h2><?php the_title(); ?></h2>
         <?php the_content(); ?>
      </div>
  <?php endforeach; ?>

<?php else : ?>

   [ put the code for your favourite
     login-form plugin here, because whoever
     sees this either doesn't have a company
     specified or is not logged in. ]

<?php endif; ?>

ok… so now your /customer page works… how to stop the sneaky bastards from finding posts via your category archives?

Well, you’ll have to create all your customercompany-privatecat1/2 categories under a top level category, called… lets say ‘hidden’

then jam this into your functions.php

function is_hidden($catid) {
  if (is_category('Hidden')) return true;
  if (is_category()) {
    $post = $wp_query->post;
    $categories = explode('|',get_category_parents($catid,false,'|'));
    if ($categories[0] == 'Hidden') return true;
  }
  else return false;
}

then just put this in your category archive template…

<?php if (is_hidden($cat)) : ?>

   You shouldn't be here, go to the customer page

<?php else : ?>

   [ regular cat template stuff here ]

<?php endif; ?>

this will handle the Hidden category, and any children of the hidden category.

I’m going to intentionally cripple my date-based archive template because I actively don’t want that functionality… but this gives you a pretty good idea of how to start looking at securing the date-based stuff as well.

Like I said, this is really only a recent hack in its infancy… perhaps you’ll find some hints here to do what you want to do.

If anyone has any better ideas, I’d love to hear em.