Forum Replies Created

Viewing 15 replies - 1 through 15 (of 85 total)
  • Thread Starter Detective

    (@detective)

    That won’t work because the meta_key refers to a key in the usermeta table, and CIMY uses another table for its data.

    However, I think it’s possible to do what you need.

    First, register a view with a dummy key, like wp_user_level or something like that. Then, create a plugin wich adds a filter on the SQL query for users. There you can create a JOIN with the CIMY table and look for the value you need.

    It’s not perfect, but at least it should work.

    I’m working on a new version of the plugin, more flexible and extensible, and easier to use, but I have other projects with higher priority, so I can’t offer a better version yet.

    Thanks for your report, I will check it out. I’m already working in a new version, but it will be ready at least a month from now …

    Thread Starter Detective

    (@detective)

    What about the function aleph_the_user_email ? Try something like this (not tested):

    function display_user_email() {
    <dt>Email</dt>
    <dd><?php aleph_the_user_email(); ?></dd>
    <?php } ?>
    add_action('aleph_user_profile_fields', 'display_user_email');

    Yes, all your requirements need an additional plugin. The good news is that it is not hard to code it, because the only thing you need is to create a user loop in your widget.

    Unforntunately, that requires programming. I can’t help you right now, only point you to the function you need to use: query_users.

    Hi, it’s not hardcoded because you can create a filter and change the value from another plugin or from your current template 🙂 Just like this:

    function change_users_per_page($users) { return 99; }
    add_filter('users_per_page', 99);

    In this way, if you upgrade to the next version (currently in the works) you will not lose your changes.

    But I’m glad you got it working.

    Thread Starter Detective

    (@detective)

    That’s because the code sorts by login. To sort by another field (those not in the table wp_users, like display name) it’s harder, but not impossible. It could be something like this:

    add_action('users_queried', 'my_custom_order');
    function my_custom_order() {
    global $aleph_query;
    if (!is_user_view()) return;
    $users &amp;= $aleph_query->users;
    
    $sort_keys = array();
    foreach ($users as $key => &amp;$user) {
    $sort_keys[$key] = $user->display_name;
    }
    asort($sort_keys);
    
    $new_users = array();
    foreach ($sort_keys as $key => $display_name) {
    $new_users[] = $users[$key];
    }
    $users = $new_users;
    $aleph_query->queried_object = $users[0];
    }

    This is not tested, but it’s how I would code a quick solution for your problem. (if you use this you can remove the previous code).

    Thread Starter Detective

    (@detective)

    This is not tested, but you could add this to a file named aleph-tweaks.php in your plugins folder (don’t forget to activate it).

    <?php
    /*
    Plugin Name: aleph-tweaks
    Plugin Script: aleph-tweaks.php
    Description: Tweaks for Aleph
    Version: 0.1
    License: GPL
    Author: You
    */
    
    add_filter('users_order_by', 'my_users_order');
    function my_users_order($order_by) {
    global $wpdb;
    return " ORDER BY $wpdb->users.user_login DESC ";
    }
    
    ?>

    Please tell me if this works for you 🙂

    Detective

    (@detective)

    Hi,

    Currently Aleph doesn’t support overriding a page. Creating a page with the same slug works but there is no way to automatically highlight the “current page” item in the navigation menu.

    If the menu gets borked it’s probably a problem with your theme, because Aleph doesn’t interfere with that. The “news page” doesn’t get linked on profiles too…

    You can hardcode the link in the nav menu in this way:

    <li class="page_item<?php if (is_user_view()) echo ' current_page_item'; ?>">
    <a href="[your-members-url]">Members</a>
    </li>

    I’ll consider this for the next version. Thanks.

    Hi,

    Looking at your screenshots, I noticed that most of your changes require only css changes. Please check the generated profiles to see the corresponding classes to the elements you want to modify.

    Other changes require more template editing. The function aleph_user_lists and aleph_user_profile are helper functions, you could copy and paste their content into your templates and modify the output there. The problem is this won’t be future-proof as the behavior of the plugin could change.

    Thread Starter Detective

    (@detective)

    There isn’t a direct link, but you can browse the SVN repository at http://plugins.trac.ww.wp.xz.cn/browser/el-aleph?rev=55661

    However, that version doesn’t work with the latest WP.

    Thread Starter Detective

    (@detective)

    @zyrq: I’m glad it worked 🙂 Don’t forget to share your URL to see how the plugins works for you.

    @niska:
    Friends was a feature of Aleph some time ago. But i removed it because it wasn’t useful for all users (in the sense of the plugin users, no the site users).

    If you need to build a social network perhaps BuddyPress is for you.

    If you just need a simple friends system, the system could be reimplemented again as a complementary plugin for Aleph, but that would be custom development.

    Thread Starter Detective

    (@detective)

    Yes, “searching/people” is redundant because in the future I would like to have “searching/something_else” (like flickr).

    If you have few editors/authors/etc that need a custom rewrite rule, then you could just add their specific rewrite rules:

    add_filter('rewrite_rules_array', 'add_user_roles_rules');
    function add_user_roles_rules($rules) {
    $user_nicenames = array('zyrq', 'detective', 'other_user');
    $user_rules = array();
    foreach ($user_nicenames as $user_slug)
    $user_rules['editors' . '/' . $user_slug . '/?$'] = 'index.php?user=' . $user_slug;
    return $user_rules + $rules;
    }

    After adding that code to a plugin and flushing the rules, the url editors/zyrq should be working. The important thing here is that the query string that the rewrite rule has to point needs the user=user_nicename parameter.

    The situation becomes more complex when you change your team of editors frequently, in that case you should provide a function to get the editors (instead of hardcoding the array as in the example) and hook in some action in WordPress when a user role has been changed.

    Hi,

    You’re almost there. You need to compile the modified .po file into a .mo file. Check out this page: http://codex.ww.wp.xz.cn/Translating_WordPress#Translation_Tools

    I’m planning to add a feature to change the slugs in a admin page or a configuration file in the future. But that will be for version 0.9 … 🙂

    Thread Starter Detective

    (@detective)

    That should be straightforward to do. I don’t think it’s something that could be useful to most users so it seems to be more reliable to think about it as a separate plugin.

    I could add some hooks and template tags to make it easier to create a plugin like that.

    Thread Starter Detective

    (@detective)

    Could possibly integrate wp comments on profiles to behave as regular comments. Users can moderate their own from their subscriber accts.

    Sadly, it’s incredibly hard to do that, because the comment system is very post-specific and allows anonymous comments. It’s better (and much easier) to create a “user comments” plugin that behaves like regular comments.

    It is possible to create such a plugin and it doesn’t need to be part of Aleph, it could be made to work in author archives and with other plugins.

    Maybe I’ll look into it in the future. Currently BuddyPress handles this very well and soon it will be available for WP single.

    If profiles could behave as pages…integrating post views would be good too.

    Sorry, I’m not sure what do you mean. By post views do you mean showing a list of posts in a profile page? You can already do that, because in profiles you can use all WordPress’ template tags. So you can do things like:

    <?php
    query_posts("author=" . aleph_get_user_ID());
    if (have_posts()) {
    // do something, display posts
    } else {
    // whatever you want to do in case the user is not an author.
    }
    ?>
Viewing 15 replies - 1 through 15 (of 85 total)