Forum Replies Created

Viewing 15 replies - 1 through 15 (of 115 total)
  • Thread Starter Wootie

    (@wootie)

    yeah logically I know what I’d need to do to create it myself…was just hoping I wouldn’t have to do that ??

    Thread Starter Wootie

    (@wootie)

    So…I got the Better Search Replace and ran through on the things I could think of that might have changed – the only thing that appeared to need a change was the actual database name. Nothing else came up with any changes.

    Nothing has changed though with regards to Page Builder…is there something else I should do with Better Search Replace?

    Thread Starter Wootie

    (@wootie)

    I did not in fact…since the domain name didn’t change, I didn’t think I’d have to do that…just changed the config file for the new database reference and otherwise everything popped up…

    I’ll go take a peek at those things…thanks!

    Thread Starter Wootie

    (@wootie)

    yeah…I’m just trying to dial back how much time I have to babysit a site (that makes me no money, but provides a valuable service).

    Hoping for some miracle unicorn, but not holding my breath.

    Thread Starter Wootie

    (@wootie)

    Thanks for that…but the issue is that typically these things only track “actions” like making a new post or installing a new plugin. I don’t see any information on them about showing that a logged-in user simply viewed a page, which is what we really need…

    Do you happen to know of any that record page views by users?

    Thread Starter Wootie

    (@wootie)

    Awesome. Thanks!

    Thread Starter Wootie

    (@wootie)

    That’s great, thanks Steve!

    Do you happen to have a name or two of a plugin that would create pages in that way, pro version or not?

    Thread Starter Wootie

    (@wootie)

    …actually, found I could do this in the Additional CSS:

    .w_footer {
    display:none;
    }

    Would like to know if there was a more “official” way to deal with that section though.

    Thread Starter Wootie

    (@wootie)

    I just upgraded the theme, and it does indeed appear to be fixed – thanks!

    Thread Starter Wootie

    (@wootie)

    I also did the WP_DEBUG thing…turned that on and performed the tasks of deleting one of those photos, re-uploading it, and going back to that page to re-add the photo as the featured image – same behavior in terms of using the downsized image.

    The log file only contains 3 error messages…apparently WP really doesn’t like the RSS reader plugin I use – this error is in there a LOT:

    [30-Jan-2017 17:07:44 UTC] PHP Notice: The called constructor method for WP_Widget in super_rss_reader_widget is deprecated since version 4.3.0! Use

    __construct()

    instead. in /home/trmc/thunderridgemc.org/wp-includes/functions.php on line 3891

    Then there’s these 2 bits:

    [30-Jan-2017 17:07:44 UTC] PHP Warning: Cannot modify header information – headers already sent by (output started at /home/trmc/thunderridgemc.org/wp-includes/functions.php:3891) in /home/trmc/thunderridgemc.org/wp-admin/post.php on line 197

    [30-Jan-2017 17:07:44 UTC] PHP Warning: Cannot modify header information – headers already sent by (output started at /home/trmc/thunderridgemc.org/wp-includes/functions.php:3891) in /home/trmc/thunderridgemc.org/wp-includes/pluggable.php on line 1179

    That’s all that was in there. And naturally if it was a problem caused by the RSS reader then things would have worked when I had it (and everything else) turned off. Not sure what the bits about header information are about…

    • This reply was modified 7 years, 9 months ago by Wootie.
    Thread Starter Wootie

    (@wootie)

    System Info:

    // Generated by the Send System Info Plugin //

    Multisite: No

    SITE_URL: https://www.thunderridgemc.org
    HOME_URL: https://www.thunderridgemc.org

    WordPress Version: 4.7.2
    Permalink Structure: /%postname%/
    Active Theme: Exoplanet 1.5.7

    Registered Post Stati: publish, future, draft, pending, private, trash, auto-draft, inherit

    Platform: Windows
    Browser Name: Chrome
    Browser Version: 55.0.2883.87
    User Agent String: Mozilla/5.0 (Windows NT 10.0; WO
    W64) AppleWebKit/537.36 (KHTML,
    like Gecko) Chrome/55.0.2883.87
    Safari/537.36

    PHP Version: 5.6.29
    MySQL Version: 5.6.25-log
    Web Server Info: Apache

    WordPress Memory Limit: 40MB
    PHP Safe Mode: No
    PHP Memory Limit: 256M
    PHP Upload Max Size: 64M
    PHP Post Max Size: 65M
    PHP Upload Max Filesize: 64M
    PHP Time Limit: 30
    PHP Max Input Vars: 1000
    PHP Arg Separator: &
    PHP Allow URL File Open: Yes
    WP_DEBUG: Disabled

    WP Table Prefix: Length: 10 Status: Acceptable

    Show On Front: page
    Page On Front: Home (#29)
    Page For Posts: News (#31)

    WP Remote Post: wp_remote_post() works

    Session: Disabled
    Session Name: PHPSESSID
    Cookie Path: /
    Save Path: /tmp
    Use Cookies: On
    Use Only Cookies: On

    DISPLAY ERRORS: On (1)
    FSOCKOPEN: Your server supports fsockopen.
    cURL: Your server supports cURL.
    SOAP Client: Your server has the SOAP Client enabled.
    SUHOSIN: Your server does not have SUHOSIN installed.

    ACTIVE PLUGINS:

    Embed Any Document: 2.2.5
    Form Maker: 1.10.5
    Official StatCounter Plugin: 2.0.1
    Page Builder by SiteOrigin: 2.4.21
    Photo Gallery: 1.3.27
    Postman SMTP: 1.7.2
    Send System Info: 1.2
    SiteOrigin Widgets Bundle: 1.7.2
    Super RSS Reader: 2.5
    UpdraftPlus – Backup/Restore: 1.12.32
    Wordfence Security: 6.3.0
    WP Edit: 4.0
    WP Lightbox 2: 3.0.6.2
    Yoast SEO: 4.1

    Thread Starter Wootie

    (@wootie)

    …and just for giggles I decided to do the same thing with all plugins disabled, with the exception of SiteOrigin Page Builder – pretty much all my pages are built with Page Builder, and I was afraid I’d corrupt them by editing them with that disabled.

    Still got the same issue.

    Thread Starter Wootie

    (@wootie)

    Well, I gave that a shot…

    To be sure, first I went and deleted those images from the media library. Then I deactivated those two plugins, and re-uploaded the images.

    Re-set them as the featured images on those pages…still the same thing – when I look at the page source, they’re all referenced like ‘https://www.thunderridgemc.org/wp-content/uploads/2017/01/trophies_2-1024×512.jpg’.

    So I’m still at a loss as to what is cutting them into 1024×512 sizes, and then assigning that cut-down version to the hero image.

    Oddly enough, I’ve discovered that if you don’t have a featured image on the pages for the hero section, and just let it default to the one image you can set in customization, the photo shows up perfectly – it’s not using a resized version.

    So, for whatever reason, there’s a different process occurring between what happens with the default hero image specified in the customization, and what happens with the featured image on a page that’s added to the hero section…

    Thread Starter Wootie

    (@wootie)

    All of the pages are using the original 2000×1000 photos as the Featured Image – and there’s not any options there to change the size of the Featured Image.

    Nor are there options to change it in your Customize options…or in the WP Media options, or anywhere else that I can see.

    So…at what point, where, and why, would those lower-res versions have been inserted in there? I don’t see any reference anywhere that can explain that.

    Thread Starter Wootie

    (@wootie)

    Verified that the CSS and new version for headers work ??

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