Forum Replies Created

Viewing 12 replies - 1 through 12 (of 12 total)
  • Forum: Plugins
    In reply to: [WP Post Rating] Post type
    DevonHarper

    (@devonharper)

    Just throwing my 2 cents in, I would also really like the ability to enable or disable this plugin for custom post types.

    Thanks mobilewebexpert for pointing out the correct way to find the name and value strings. That saved me a bit of a headache. Also remember to address the attribute by its name not its ID. This was a mistake I made at first as well.

    Thread Starter DevonHarper

    (@devonharper)

    Just installed version 1.4.8 and the shortcode with a custom template is working again. Thank you for the attention and quick fix!

    It would be very nice if you would add a shortcode argument for the YouTube embed attribute “controls” and maybe even “showinfo”.

    A filter build_embed function might be another way to allow users to add unique arguments to video urls.

    For now, I have hacked my copy of the plugin to remove the controls and video information on youtube videos. I have edited advanced-responsive-video-embedder\public\class-advanced-responsive-video-embedder.php at line 855 by adding:

    'controls'       => 0,
    'showinfo'       => 0,

    This seems to work… until the next plugin update 😉

    Thread Starter DevonHarper

    (@devonharper)

    I am using My Content Management ver 1.4.2

    I think I have found the issue in mcm-view-custom-posts.php on lines 160-164:

    if ( is_array( $value[0] ) ) {
    	foreach( $value[0] as $val ) {
    		$cfield[] = ( $is_email )?apply_filters('mcm_munge',$val,$val, $custom ):$val;
    	}
    	$p[$key] = explode( ", ", $cfield );

    I’m not sure if $value[0] is ever an array. In my instance it is always a string, and I end up with $value[0], $value[1], etc. I have hacked my copy of mcm-view-custom-posts.php to change lines 160-164 to:

    if ( count( $value ) > 1 ) {
    	$cfield = array();
    	foreach( $value as $val ) {
    		$cfield[] = ( $is_email )?apply_filters('mcm_munge',$val,$val, $custom ):$val;
    	}

    And my shortcode and template now seem to be working, but I am not sure if there are any other effects of this code change.

    @shazahm1,
    Thank you for suggesting the second option. Te gettext filter was working wonderfully for me. It is still working on the front end of the site, but I have just noticed that it is no longer replacing the text on the back end of the site, when I am managing an entry. Here is my code:

    add_filter( 'gettext', 'child_rename_cn_field_labels', 20, 3 );
    function child_rename_cn_field_labels( $translated_text , $text , $domain )  {
    	if ( $domain == 'connections' && $translated_text == 'Department' ) {
            $translated_text = 'Booth';
        }
        return $translated_text;
    }

    Any suggestions? Thanks again for your help!

    Thread Starter DevonHarper

    (@devonharper)

    BTW… I declared $geo_mashup_custom as a global on line 115 of render-map.php and my custom styles are now loading again.

    Thread Starter DevonHarper

    (@devonharper)

    Thanks for the reply. Unfortunately we do not have a test installation on the server because of the server setup.

    I have enabled FirePHP on the site and did a little poking around. I noticed that on line 128 of render-map.php, isset($geo_mashup_custom) was returning NULL. I think this is because $geo_mashup_custom is not declared as a global variable at the begining of the GeoMashupRenderMap::enqueue_styles function. Is this intentional?

    I am having the same problem as well.

    Genesis 1.9.1, WordPress 3.5.1, GFWA 0.8.1, Firefox 18.02

    On Firefox, I have noticed the problem with all dropdown options on the widget. The dropdowns seem to work, but they loose focus after 1 second. So if I am very quick, I can make a selection.

    I suspect their is something screwy happening with the jQuery on the widget editor that makes the dropdowns lose focus before we make our selection.

    The transient entries for the widget are entries in the wp_options table of the database. I found 4 entries in my database that I had to manually delete in order for the widget to update itself and fix the errors I was having.

    _transient_stc_followers_TWITTERACCOUNT_count
    _transient_timeout_stc_followers_TWITTERACCOUNT
    _transient_stc_followers_TWITTERACCOUNT
    _transient_timeout_stc_followers_TWITTERACCOUNT_count

    Where TWITTERACCOUNT is the twitter account name for your configuration.

    I uploaded the changes to the stc-followers.php to the server, deleted the 4 entries from the database, and then refreshed the blog page.

    I am having the same problem with the plugin on my site. I was seeing the following errors:

    Warning: array_rand() [function.array-rand]: Second argument has to be between 1 and the number of elements in the array in /public_html/wp-content/plugins/simple-twitter-connect/stc-followers.php on line 109

    Warning: implode() [function.implode]: Invalid arguments passed in /public_html/wp-content/plugins/simple-twitter-connect/stc-followers.php on line 116

    Warning: shuffle() expects parameter 1 to be array, object given in /public_html/wp-content/plugins/simple-twitter-connect/stc-followers.php on line 137

    Warning: array_slice() expects parameter 1 to be array, object given in /public_html/wp-content/plugins/simple-twitter-connect/stc-followers.php on line 138

    Warning: Invalid argument supplied for foreach() in /public_html/wp-content/plugins/simple-twitter-connect/stc-followers.php on line 146

    I was able to trace the problem down to one simple fact, the twitter account I was testing with had less than 100 followers. I was able to fix the problem by updating line 107 of stc-followers.php to:

    $num_req = (count($fols)<100) ? count($fols) : 100;
    $fols = array_rand(array_flip($fols), $num_req);

    I also had to clear out the transient entries for the widget from my database. But it is working for me now.

    I was having the same problem on my site, but I did manage to get it to log out eventually. What I did was:

    1. Logged out from WordPress
    2. Logged out from Twitter
    3. Deleted “Domain Cookies” using the Web Developer Toolbar in Firefox
    4. Deleted browser cache

    After reloading the page, I was then logged out from Twitter and had the default view of my comment form.

Viewing 12 replies - 1 through 12 (of 12 total)