Forum Replies Created

Viewing 15 replies - 1 through 15 (of 116 total)
  • Love the Search Regex plugin, but I agree: Being able to search custom posts types would be helpful. Also to restrict posts by custom post type.

    You could offer these features by adding a filter in /searches/post-content.php, within the find(} function, right under $sql =…, allowing us to modify that SQL statement. Like:

    if ( has_filter( 'searchregex_sql' ) ) {
        $sql = apply_filters( 'searchregex_sql', $sql );

    Use the latest v2 of the API:

    I switched to that and the error went away.

    * Manually made that change to our protect.php file.
    * Activated Protect module.
    * Logged out then logged in: successfully and mathlessly.

    Thanks for the fix.

    Installed and activated v2.2 and behavior is the same: Using the Categories “Permalink” selection does NOT change the value of the existing the _category_permalink meta upon Update, and if a post doesn’t have a _category_permalink CF, selecting a cat Permalink does NOT create a new CF.

    Deactivated all plugins (it’s a test site) then reactivated only WP Category Permalink: same problem.

    Reverted back to v1.6: all works again.

    Thanks for sticking with this. Tell me if you have any more tests you’d like me to run. Just made a donation to help pay for all the stimulants you’ve likely consumed recently trying to track this bug.

    Not sure this issue is resolved yet. Using 1.6, all works well, retaining the Category box “Permalink” selection after a save/update. But w/ v2.1 Permalink changes are not saved.

    I’m monitoring the value of the CF: '_category_permalink'. In 1.6 the ID of the cat of the Permalink selection gets written to this CF.

    In 2.1 changing the Permalink selection doesn’t change the CF value. And if there was no CF for a post, selecting a Permalink does not create a new ‘_category_permalink’ CF.

    The permalink structure at this site is: /%category%/%postname%/

    Using latest Chrome browser (Mac). Site runs PHP 5.4. (Tested this on another site at same webhost w/ same results.)

    Thanks for the great plug. For now I’ll stick w/ 1.6 tho.

    Perhaps unrelated, but v1.7 and v2.0 would not activate. Error messages:
    Warning: require(wpcp_settings.php): failed to open stream: No such file or directory in /{path-to}/wp-content/plugins/wp-category-permalink/wp-category-permalink.php on line 18

    Fatal error: require(): Failed opening required ‘wpcp_settings.php’ (include_path=’.:/usr/local/lib/php:/usr/local/php5/lib/pear’) in /{path-to}/wphw/wp-content/plugins/wp-category-permalink/wp-category-permalink.php on line 18

    Same issue, not on wp-login.php but a custom login page. After entering credentials we now get a new page w/ the jetpack_protect_process_math_form. When you correctly enter the math you are redirected to the homepg, you are not logged in, not do you get any error from the JP form.

    Go back to the custom login page and the same thing happens.

    However, on the wp-login.php page the math appears in the form and works when correctly answered.

    This happened after updating JP this morn, which came w./ Protect default on (then auto-deactivated Bute Protect. I deactivated Protect and ll works well. Maybe all that needs doing is adding the math turing to the custom login page: which uses the wp_login_form() form. Is there a filter or method for adding jetpack_protect_process_math_form to the output of wp_login_form()?

    Or can I just re-activate Brute protect to get login security?

    Yes, themes often add their own image sizes.

    OK, there’s your problem. I don’t have time to track this all down for you, but your vars determining pagination are either NULL or 0. You’ll need to do some tests figure out why. You may need to set the $paged var (to 1) too, like:
    $paged = ( get_query_var( ‘paged’ ) ) ? get_query_var( ‘paged’ ) : 1;

    That’s how you do it for a posts query, not sure if a user query works the same. If not, maybe this works:
    $paged = ( $paged ) ? $paged : 1;

    oops, forgot the opening ?:
    <!– <?php echo “total_users: $total_users, offset: $offset, paged: $paged”; ?> –>

    Add this somewhere to your code — outside of the foreach loop:
    <!-- <php echo "total_users: $total_users, offset: $offset, paged: $paged"; ?> -->

    You’ll need to view the page’s source to see it: I put it in an HLTM comment so it wouldn’t display publicly on the page. No need for commenting tho if the site’s still in dev.

    Perhaps the math of your vars is not working as expected. Print out (eg, w/in and HTML comment, the view source): $total_users, $offset, and $paged to make sure you’re getting the values you want.

    Here’s more on paginating a users list:

    Can you figure out what the order is that of your list of users? Maybe if you know that, it’ll help you find out why your orderby argument isn’t applying.

    The default is 'login' (username). If that the way it’s sorting now, then maybe you have a syntax problem in your arguments, so your orderby choice isn’t getting to the query.

    Not sure, but try a different orderby to make sure the that argument is getting to the query; orderby=ID should do what you want too (as each new user gets a higher-number ID). If that doesn’t affect the sort, try another orderby, here’s the list:

    If that doesn’t change it, then maybe somethings wrong w/ your argument syntax or something else is overriding your orderby.

    By the way, the URL you posted is a WordPress page, and so that’s page’s post ID is what gets displayed in the HTML here: <article id="post-<?php the_ID(); ?>"...

    So that ID gets printed for each user: <article id="post-602"...

    But in CSS an ID value must be unique, whereas on your page you have multiple IDs w/ the exact same value. To meet CSS standards you could remove the id="post-<?php the_ID(); ?>, or change id to class, or use something like id="author-<?php echo $user->ID; ?>.

    Right, 4:3. That’s something you’ll want to start doing regardless of the source of the cropping.

    I notice the WP RSS Aggregator plugin has a “” premium add-on, perhaps that’s what’s setting your 480×360 image size and cropping:

    If your problem is solved, please mark this forum topic as Resolved (w/ the checkbox under the text box or the dropdown in the sidebar) — it’s how we know you no longer need our help on this issue, so we can move onto other’s topics).

    Sounds like you’ve already learned lots: congrats on making the gif animation and the video.

Viewing 15 replies - 1 through 15 (of 116 total)