Forum Replies Created

Viewing 15 replies - 571 through 585 (of 3,596 total)
  • The first thing to try for the WSOD (White Screen of Death) is setting WP_DEBUG to TRUE in wp-config.php. That will usually provide you with an error message.

    As for why it would not work, I don’t have any experience in that area.

    There are more issues than that with this code.

    Here is a rewrite of your single line of code, into several.

    Your line:

    echo '<meta property="og:image" content="<?php $featuredImage = get_field('featured_image'); echo esc_url( $featuredImage['url'] ); ?>" />';

    How you should be writing it:

    echo '<meta property="og:image" content="';
    $featuredImage = get_field('featured_image');
    echo esc_url( $featuredImage['url'] );
    echo '" />';

    To turn off the ability to Comment on Pages or Posts, you have to do two things: one for future Pages/Posts; one for currently-existing Pages/Posts.

    For future (new) Pages/Posts, in the WordPress Admin panels, go to Settings-Discussion and remove the checkmark from “Allow people to post comments on new articles”.

    For existing Pages/Posts, you can turn off Commenting for each one separately by list All Pages or All Posts, mousing over the Page or Post, clicking on Quick Edit when it appears, remove the checkmark from Allows Comments field and click the Update button.

    If this is too much work, you can try a plugin like this: https://wordpress.org/plugins/disable-comments/

    I’m not sure if you are interested, but the Akismet plugin does a good job of identifying Spam Comments.

    As explained here, we are not in a position to support Paid Themes like Kleo: http://codex.wordpress.org/Forum_Welcome#Commercial_Products

    Part of what you paid for the Theme goes to provide you with support, so you should either contact the Theme Author directly or ThemeForest support. Some Paid Themes offer their own community support through Forums.

    This is known as the WordPress Screen of Death (WSOD), which is explained here: http://codex.wordpress.org/Common_WordPress_Errors

    In my experience, the first thing to do is to set WP_DEBUG to TRUE in wp-config.php, which is explained here: http://codex.wordpress.org/Editing_wp-config.php#Debug

    That should give you an error message so you know where to start solving your problem.

    This is not to be considered a set of tested solutions, but just my best shot at giving you my thoughts on the subject.

    I got the impression from the plugin user who had trouble with my plugin’s Settings not saving that he solved it by making changes to W3’s settings. My first guess would be excluding all /wp-admin/ pages from Caching.

    Cookies can still be a problem in a non-MultiSite installation. The way WordPress works is that, if you are logged on to www.example.com, you are NOT logged on to example.com, example.org or www.example.com/anothersite. Even if you used Parked Domains, Redirection or whatever. Likewise, if you logoff www.example.com, you are still logged on to example.com, if you have previously logged on to example.com within the WordPress timeout period.

    I haven’t proven it, but one of my plugin users claims to have to actually delete all WordPress cookies after logging off before he can accurately view his site with my plugin and the W3 plugin. I don’t know enough about CDN to know where it fits in the mix.

    An easier approach, in my opinion, is to have another Windows username or browser THAT HAS NEVER LOGGED INTO WordPress, and use it to reliably test visibility of your site with my plugin turned on.

    As for BuddyPress, another plugin user and I have both confirmed that, if you install BuddyPress for the first time while the WordPress Settings-General “Membership” checkbox is NOT checked, whatever Page is eventually assigned to the Register function of BuddyPress will never work correctly with my plugin. Even a Delete and Re-Install of BuddyPress will not solve the problem. Only a WordPress re-install will solve it, because BuddyPress does not properly clean up its Settings in the WordPress Database Options Table. This is such a painful problem that I am contemplating creating a new plugin called jonradio BuddyPress Cleanup to delete these settings that BuddyPress does not when it is deleted.

    Admittedly, this problem seems to be one where the standard WordPress Register page does not get redirected to the BuddyPress Register page. I was not clear on whether this problem was related to the same user reporting visibility of some other BuddyPress pages. Perhaps not.

    About all I can think of to help is to speculate that there is a quiet time of the day for your web site, and then would be an acceptable time to deactivate W3 for 60 seconds or less while you set the Settings in my plugin that have not been saving properly.

    A lot of verbiage without any definite answers. Mainly, because I’m out of my depth here. I do want to wish you success with this.

    In the interests of giving a complete answer, the alternative to Plugins for WordPress is to write your own PHP code to add the functionality you want.

    Ironically, the best way to do that is by writing your own (private) plugin. The WordPress Plugin API is meant for exactly that: adding your own code.

    Thanks so much for the update!

    Yes, I ended up reinstalling WordPress like you did, because simply deleting and reinstalling BuddyPress did not clear up the problem of missing BuddyPress pages.

    This is definitely a WooCommerce issue. And WooCommerce is a “world of its own”, so you are best to see what you can find in the existing documentation and support info at https://wordpress.org/plugins/woocommerce/

    If you cannot find an answer there, post on their support forum: https://wordpress.org/support/plugin/woocommerce

    My own plugin takes a different approach: block the site from anyone not logged on, and let WordPress handle the Registration and Login in the normal function: https://wordpress.org/plugins/jonradio-private-site/

    I’ll need a little time to think about where we can go from here. It may take me up to 24 hours to respond.

    Thanks for your patience!

    Compared with, say, Microsoft Office, WordPress has limited functionality. WordPress is Open Source and free of charge to use, and support is free, too. Office is not.

    The Plugin approach allows additional functionality to be provided without burdening the WordPress Core development team with thousands of additional pieces of functionality to worry about, which would otherwise increase the manpower required to keep WordPress moving forward.

    Different mindset.

    As a user, it is an investment in time to determine which Plugins are going to be needed. I talk about those choices in a WordCamp presentation I did a year ago: http://jonradio.com/wordcamp/2013.pdf

    The answer to this depends on the Theme, so it is best to talk to the Theme authors about this. This Theme is not part of the WordPress Theme directory, so you should be looking for help on the web site where you got the Theme.

    I’m not going to be able to figure this out, as GoDaddy has a lot of different types of control panels, and different ways to install WordPress. Too many possible combinations of different possibilities to give you accurate advice.

    I suggest that you talk to GoDaddy support and get them to explain to you how to “Flush the Cache” for your WordPress site. Basically, you will have to do that each time you change a Setting in my plugin. And probably sometimes when you change settings in other plugins, or even just activate and deactivate them.

    In addition, I never use Caching myself because my sites are low enough traffic not to need it. So, my experience with Caching is limited, at best.

    Now we are getting somewhere. Must-Use and Drop-ins are plugins that are always activated. The Drop-in is definitely a Caching plugin.

    I’ll do a little research on the godaddy site and get back to you.

Viewing 15 replies - 571 through 585 (of 3,596 total)