Forum Replies Created

Viewing 15 replies - 1 through 15 (of 18 total)
  • Plugin Author Matt Royal

    (@themattroyal)

    Hi Jon

    Thank you for the thorough feedback.

    The preview modes were developed for testing of the popup windows or notices to preview the content and visuals of these.

    But I like your suggestions and will give some more thought to your ideas and some other possible improvements here.

    Ultimately the best is always just to test in an incognito window but some users aren’t as clued up and get confused, forgetting they are still logged in and then functionality seems broken when infact its not.

    I will release an update shortly increasing the z-index to prevent the notice falling under any other notices.

    Thanks again for the feedback, its really cool of you to take the time to this 🙂

    Plugin Author Matt Royal

    (@themattroyal)

    Hi Rich99

    I am happy to support my plugin and assist in resolving issues however when its a compatibility issues (as in your case), further investigation is required to determine if the issue is on the theme side or the plugin side.

    Your review is thus incredibly unfair and misleading to other WordPress users coming to this page/plugin and I would appreciate if you removed it and raised your issue in the support thread (or even contact me directly via my personal site) so I can look at how I can assist you.

    Thank you kindly.

    Plugin Author Matt Royal

    (@themattroyal)

    Lovely, always happy to help and thank you for your time in writing a positive review 🙂

    Happy new year!

    Cheers,
    Matt

    Plugin Author Matt Royal

    (@themattroyal)

    Hi Peter

    Thank you for making me aware of this.

    I have pushed up a fix for this bug and released version 2.0.1 of the plugin. You should be able to update it from with your WordPress Dashboard or download and install the latest version from scratch again.

    Last but not least, please rate the plugin and your experience with it, I would really appreciate it as I feel it has received a few unfair reviews that could be remedied by some good ones 🙂

    Many thanks

    Cheers,
    Matt

    It really doesn’t pay to be in a rush… I see it now, thanks for pointing it out 🙂

    Cool, thanks Chad.

    Just submitted the PR, very basic, for a new filter on the widget title.

    The scenario I had, it could not just be changed via the CMS.

    Thanks

    Plugin Author Matt Royal

    (@themattroyal)

    Hi guys

    Thank you for the feedback. Due to work and other community commitments over the last year I have not had much time to update & improve the plugin.

    I will be allocating some time to this plugin over the next few weeks and I will address this issue that has been raised here and push up a new release.

    Keep any eye out 🙂

    Yes, use CSS to target the specific li elements you wish to change and use Unicode for the icons.

    Here is the cheatsheet for all the icons: http://fortawesome.github.io/Font-Awesome/cheatsheet/

    Your CSS will look something like this:

    li:before {
    	font-family: FontAwesome;
    	content: '\f105';
    	padding: 0 10px 0 0;
    }
    
    li {
    	list-style-type: none;
    }

    You may need to clear your browsers cache if assets such as stylesheets are being cached.

    The Easiest way to do this is add a query string to the end of your stylesheets URL or you can just increment the version number in your themes stylesheet as well.

    I have updated the snippet for you replacing your JavaScript with double quotes in the syntax so it wont break the PHP string like it did last time you tried it. Give it another go and see if that works for you.

    add_filter( 'the_content', 'royal_inline_body_js', 20 );
    
    function royal_inline_body_js( $content ) {
    
    	// Check your on posts
        if ( is_single() )
    
            // Add your inline JS to the variable
            $royal_custom_js = '<script type="text/javascript">document.write(unescape("%3Csc"+"rip"+"t type="text/javascript" id="cafenews.pl#c73707e940ccd580dc9afd40852ff083"%3E%3C/s"+"cri"+"pt%3E%3Cdiv id="cafenews.pl#cvb64mnc8vg4jd8gksd653jkadg7j6"%3E%3C/div%3E"));setTimeout("var d=new Date();document.getElementById("cafenews.pl#c73707e940ccd580dc9afd40852ff083").src="http://webservices.cafenews.pl/mpl/Static/Static.js?id=cafenews.pl#cvb64mnc8vg4jd8gksd653jkadg7j6&d="+d.getFullYear()+d.getMonth()+d.getDate();",250);</script>';
    
            // Append before existing post copy
            $content = $content . $royal_custom_js;
    
        // Returns the content.
        return $content;
    }

    Its likely breaking because of the syntax of your JavaScript. You will need to make sure your JavaScript snippet is formatted using double quotes and not single quotes.

    Can you supply your JavaScript snippet so I can see it…

    Your are missing closing </div> tag for your #main Div element.

    In your page.php file, add:

    </div><!-- #main -->

    Below:

    </div><!-- #content -->
    </div><!-- #container -->

    So it looks like:

    </div><!-- #content -->
    </div><!-- #container -->
    </div><!-- #main -->

    If it has to be within your pages body then I would try using the_content filter to dynamically add your JavaScript snippet before the actual post content.

    You could place this in your theme or even better, child theme functions file.

    add_filter( 'the_content', 'royal_inline_body_js', 20 );
    
    function royal_inline_body_js( $content ) {
    
    	// Check your on posts
        if ( is_single() )
    
            // Add your inline JS to the variable
            $royal_custom_js = '<script type="text/javascript">...code...</script>';
    
            // Append before existing post copy
            $content = $royal_custom_js . $content;
    
        // Returns the content.
        return $content;
    }

    Disabling pingbacks in your settings will only affect posts and pages you create after changing this setting, NOT any existing ones!

    You can manually go in and change each one or you could try adding this to your themes function file…

    // Disable Comments in Old Posts
    add_filter( 'the_posts', 'royal_close_comments' ); 
    
    function royal_close_comments( $posts ) {
    	$posts[0]->ping_status    = 'closed';
    	return $posts;
    }
    Plugin Author Matt Royal

    (@themattroyal)

    Hi Matteo

    I think because I have tried to cater for a few various scenarios that users of the plugin might need, the configuration of the plugin may be what is confusing.

    If you could help me get to the bottom of it, that would be great 🙂

    I have written down a step by step guide to configuring the plugin correctly.

    Give it a try and let me know. Perhaps this will help some others and then I can add some better documentation for it. (If it is still not working please send me a private message so I can assist further and get it patched for you and everyone else. thanks)

    • Step 1 – Switch on Maintenance mode
    • Step 2 – Set an end date. If the date is before or equal to the current date, redirects or messages will not fire. Currently an end date must be set!
    • Step 3 – Set message intervals. By default it is set to 0, this will make your redirect or message fire every time someone accesses your websites WooCommerce page. Make sure yours is set correctly to the frequency you wish and when changing this, make sure to use the ‘Delete all cookies’ button before setting your new value. (Remember cookies are stored in the browser so if using a different device/browser to test, the already set cookies will need to expire naturally on that device/browser first, or you will need to login to your Dashboard from that device/browser and then use the ‘Delete all cookies’ button to manually delete them from there.)
    • Step 4 – Display Options. NB!! Use the dropdown list to select the type of display or redirect you are using. It is not enough to just type in a redirect url, a message or select a page option, you must use this drop down to specify which one you are using!!

    Important! When testing, you must make sure you are not loggedin or else it will appear to not work. I have done this plenty times during development.

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