Forum Replies Created

Viewing 15 replies - 31 through 45 (of 155 total)
  • Thread Starter Ron Strilaeff

    (@ronstrilaeff)

    Good, I’m glad that helped someone.

    This is a very good plugin since I can actually control what the text search does and it has an intuitive admin interface.

    And the resulting search url looks normal (readable, shareble) without a long string of special query args (mosty empty) which I’ve seen on some sites.

    Thread Starter Ron Strilaeff

    (@ronstrilaeff)

    I see … good idea. Unfortunately, I couldn’t get any modal login scheme working in time for our release date so I just went back to the standard wordpress login functionality with a custom logo and a redirect back to where they were when they decided to (or were required to) login. Thanks, Ron

    Forum: Fixing WordPress
    In reply to: Add New Tag Error
    Thread Starter Ron Strilaeff

    (@ronstrilaeff)

    As usual, I make my own problems and sometimes solve them 🙂

    In what seems like a completely unrelated php file, I had entered two newlines at the end of a program file that added a meta box to the post edit form.

    So the rule of thumb here is there is no need for the closing ?> and if you do stop and restart the php code in order to insert some literal html or script, do not insert any blank lines. Apparently they get returned in ajax responses and can screw things up in seemingly unrelated code.

    mikeschinkel describes the issue well here

    Here is what worked for me to get things back to normal:
    – deactivate and remove the plugin (delete files)
    – delete all pages it created (approx 8-10)
    – use phpmyadmin to find and (carefully) remove all options and metadata containing ‘%tml%’ or ‘%theme_my_login%’
    – visiting the permalinks admin page (and saving the changes … not sure if that is necessary)

    Thread Starter Ron Strilaeff

    (@ronstrilaeff)

    Ok I think I figured out most of this:
    – weird chars are stuck in there for accessibility but get formatted by css in a strange way. Easy to strip out of post-ratings-control.php
    – this css gets rid of the extra detail to the right of the stars without messing up any calculations

    .ratings .meta {
      display: none;
    }

    – the page needs to be refreshed to see what I rated. (I thought the ajax part of this plugin would make a refresh not necessary.)
    – the ip address and/or cookie determines if someone is eligible to vote, so I can’t test this with two users on the same computer. I will disable/modify that so it is at most one vote per post per userid (I only care to get votes from logged in users).

    Does anyone have an idea how I can show the partial stars instead of the %score so the display is more compact? In my application I don’t think I need the details of how many votes etc. Just a nice graphic to indicate how much the post or whatever is liked.

    One more thing, is there a way that a user can change their vote? Surely I’m not the only person to ever click on the wrong star or change my mind later.

    Thread Starter Ron Strilaeff

    (@ronstrilaeff)

    they may see the login page but will not be able to log in

    Not so in this case… 🙂
    I did this test for a subscriber and contributor:
    – logged them out
    – login as admin
    – enable MM
    – logout from admin (see UMM screen)
    – login as test user (using their saved bookmark to mysite.com/wp-login.php
    – subscriber is now logged in and able to navigate site

    This is not a contrived scenario. Our site wants to keep people logged in so they can see their favorites, share links to posts on social media, leave comments, etc. In fact we installed the “Remember Me Controls” plugin with “remember me forever” to encourage that behavior, and make it easy for people to stay connected to us and make new contributions without having to re-login everytime. Our users are either admins(2) or contributors(3142).

    No problem though, if I need to actually block the site I’m sure (as you say) there are many ways.

    Thanks for putting together this very attractive and easy to use plugin.

    Any ideas about finding the conflict? Do you know any likely candidates before I go through the painful process of deactivating ALL plugins?

    In case it helps, the firebug console shows this when I refresh the settings page on my installation.

    ReferenceError: postboxes is not defined
    (?)($=function())option...ettings (line 56)
    a(t=[Document options-general.php?page=wps-seo-booster-settings, [function()]])jquery.min.js (line 2)
    a(e=Document options-general.php?page=wps-seo-booster-settings, t=[Document options-general.php?page=wps-seo-booster-settings, [function()]])jquery.min.js (line 2)
    a(e=undefined)jquery.min.js (line 2)
    a()jquery.min.js (line 2)
    [Break On This Error] 	
    
    postboxes.add_postbox_toggles( 'settings_page_wps-seo-booster-settings' );

    Thread Starter Ron Strilaeff

    (@ronstrilaeff)

    My apologies to the user-meta crew. I had forgotten that I had posted here before I contacted them directly.

    They responded the very next day and politely with no questions asked refunded me in full. There is nothing wrong with the plugin or the publishers, it was just not what I needed.

    (Also I can’t see how to delete this post so if a wordpress.org moderator reads this, maybe you can just delete this post).

    Thread Starter Ron Strilaeff

    (@ronstrilaeff)

    I emailed them through their website contact form with the same message and here is the dialog:

    ===============
    Hello Ron,
    You’ve just installed Wysija for the first time right?
    If so, can you try to reinstall Wysija from scratch from Wysija > Settings > Advanced > Reinstall now
    Try that and let us know,
    Cheers,
    Ben support@wysija.com

    =============================

    I had tried it a couple of months ago but removed it, so maybe there was some corrupted option left behind.

    Because your advanced re-install worked

    Thanks!

    Thread Starter Ron Strilaeff

    (@ronstrilaeff)

    Mikko,

    I’m sure this is a great plugin for many people and you really are giving outstanding support. However, as I usually discover with big plugins like this, they are usually overkill for what I want to do and I end up adding a function/filter/action hook to my child theme’s functions.php file or modifying a much simpler plugin to get the results I need. So I’m choosing NOT to use this plugin and would really like an clean uninstall utility that completely removes all traces of options, metadata, database tables, files, etc. No offense, but it’s just not right for me.

    I think I’m really good at creating or revealing bugs or incompatibilities among plugins. 🙂 So, for what it’s worth, I re-activated the plugin, (without the mod you suggested above) saved the settings (using minimal indexing) and then pressed the big green “Build the index” button. Well, it completed (after about a minute) with no errors but even after refreshing the settings page, there are no values in the “state of the index” section and there were no database tables created. Weird huh? So I obviously broke something.

    I hope my feed back helps you be even more successful!

    Thread Starter Ron Strilaeff

    (@ronstrilaeff)

    Update
    === working patch! ===
    modify lines 784, 790, 795 in function se_terms_join

    FROM:

    784: if ( $this->options['se_use_category_search'] )
    790: if ( $this->options['se_use_tag_search'] )
    795: if ( $this->options['se_use_tax_search'] )

    TO:

    784: if ( "Yes" == $this->options['se_use_category_search'] )
    790: if ( "Yes" == $this->options['se_use_tag_search'] )
    795: if ( "Yes" == $this->options['se_use_tax_search'] )

    It seems the $this->options[…] returns true if any value is stored (it was a “No” btw so that’s good). This patch makes sure that the join clause is only added to if the relevant option value is explicitly “Yes” as expected. This same logic error might exist elsewhere but I don’t have time to test everything. That part of it works now for me.

    @dan Cameron, if you are still around can you look into this please 🙂

    Thread Starter Ron Strilaeff

    (@ronstrilaeff)

    My proof is that in version Version: 6.9.4.1 of this plugin, I changel line 35 to

    var $logging = true;

    then do a search with “search every tag name” set to blank (not Yes)

    Then look at the file wp-content/plugins/search-everything/logfile.log which shows the full constructed query on the last line. That line includes the clause

    ... LEFT JOIN sv_term_taxonomy AS ttax ON (  ( ttax.taxonomy = 'category' OR ttax.taxonomy = 'post_tag' OR ....

    But the logic of search-everything.php wants to obey the blank means “No” … so I’m going t into debugging mode to fix this, even if I have to comment out some of Dans’s code.

    Hi Drew,

    I love small plugins like this that do a well defined job and do it well. Thanks for putting it together.

    However, I think that feature of hiding the admin tool bar for non-admin users has a natural and welcome place in your plugin right under the User Profile Access: checkbox.

    I don’t need it since I just now added that add_filter( 'show_admin_bar'.... code to my child theme, but I would have liked to see that checkbox in this plugin in case I ever needed to enable it easily.

    Thanks again, Ron

    Jeff, I’m sure this plugin is great for some people, but it tries to do way too much for my needs. I would like a clean uninstall utility that gets rid of all those special pages, options, tables and hidden redirects.

    It has my login / logout behavior really screwed up now and I can’t seem to untangle it.

    Please!?

    Thank You, Ron

    Here is a barebones example (which I just tested on my site):

    add_filter( 'wp_nav_menu_items', 'asv_add_usermenu', 10, 2 );
    
    function asv_add_usermenu( $items, $args ) {
      if (is_user_logged_in() && $args->theme_location == 'primary-menu') {
        $items .= "<li class='sub-menu'><a href='" . wp_logout_url()  . "'>Log Out</a></li>";
      } elseif (!is_user_logged_in() && $args->theme_location == 'primary-menu') {
        $items .= "<li class='sub-menu'> <a href='" . wp_login_url() . "'>Log In</a></li>";
      }
      return $items;
    }

    The ‘primary-menu’ text is from this admin page (whatever name the theme registered that menu as). http://yoursite.com/wp-admin/nav-menus.php It is one of the menu names in grey italics in the top left box.

    I gleaned the above from http://codex.wordpress.org/Function_Reference/wp_get_nav_menu_items
    and http://codex.wordpress.org/Function_Reference/wp_nav_menu
    and I think the ‘primary-menu’ is the only thing environment specific.

Viewing 15 replies - 31 through 45 (of 155 total)