Forum Replies Created

Viewing 15 replies - 76 through 90 (of 116 total)
  • Seems to be a 98% setting hardcoded:
    $Ihrss_sliderwidth = 98;
    line 140 of image-horizontal-reel-scroll-slideshow.php
    If I modify that to 100 I get full screen width: see https://www.bikefun.org/

    BTW your plugin is the only one that allows images to have different widths, that’s why I use it!

    Thread Starter nikdow

    (@nikdow)

    Thanks, I identified the plugin by comparing the earliest time of this error in the logs with plugin file dates on the server.
    The plugin that had updated just before this warning started appearing also had a bug which I had notified, and I received reply that this was hot-fixed, so I’ve updated that plugin, and both errors are now gone.

    Thanks for the hint, which pointed me in the right direction.

    Thanks, fixed, and it also fixed a warning coming from WooCommerce,
    [25-Jul-2019 03:33:27 UTC] WC_Log_Handler_File::get_log_file_path was called incorrectly. This method should not be called before plugins_loaded. Backtrace: WooCommerce->log_errors, WC_Logger->critical, WC_Logger->log, WC_Log_Handler_File->handle, WC_Log_Handler_File->add, WC_Log_Handler_File->should_rotate, WC_Log_Handler_File::get_log_file_path, wc_doing_it_wrong. This message was added in version 3.0.
    Which seemed to be unrelated but apparently was triggered by this error.

    I’m seeing a PHP error in the log, coming from this line:

    wppa_update_album( array( ‘id’ => $alb, ‘cats’ => $mycats . $cats, ‘modified’ -> time() ) );

    Looks like a syntax error
    should be
    ‘modified’ => time()

    Worse still, I’m loading woocommerce.css via CDN OK, using AWS CloudFront, but that file requests .ttf and .woff files using a relative address, so they are requested from the CDN, and aren’t supplied, probably because of CORS.

    The plugin isn’t requesting the font files, they are relatively addressed from the CSS which is fetched from the CDN. Therefore excluding the font files doesn’t solve it.

    So currently I have to exclude the specific CSS file from being service via the CDN.
    – or –
    CORS headers have to be handled on the server running CDN enabler.
    https://tecadmin.net/set-access-control-allow-origin-cors-in-apache/ shows how to set headers.
    Also had to enable /mods-available/headers.load in the apache config.

    Amazon has help on passing the header through CloudFront: https://aws.amazon.com/premiumsupport/knowledge-center/no-access-control-allow-origin-error/
    and https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/header-caching.html

    Still didn’t work, even after invalidating the files on CloudFront.

    I can verify that my server is including a Access-Control-Allow-Origin header to the font file when CloudFront requests it.

    I’m a bit puzzled by the instructions from AWS about request headers. Should the Access_Control header be in the request headers made when the font file is requested?

    Anyhow still didn’t work so back to plan A and don’t serve the CSS file via CDN.

    Thread Starter nikdow

    (@nikdow)

    Now closed this Topic, thanks for your help which pointed me to the solution.

    Thread Starter nikdow

    (@nikdow)

    Thanks for your help.

    The error is occuring in a page that is provided by a plugin written by us some time ago. Our plugin uses Angular 1. I had to review our plugin to solve this problem. It contained this code:

    var ajaxurl = $scope.data.siteurl + "/wp-content/plugins/wp-photo-album-plus/wppa-ajax-front.php?action=wppa&wppa-action=render&wppa-cover=0&wppa-album=" + $scope.item.album + "&wppa-occur=1&wppa-size=640";
    wppaDoAjaxRender( 1, ajaxurl, '' )

    I replaced this with

    var ajaxurl = $scope.data.ajaxurl + "?action=wppa&wppa-action=render&wppa-cover=0&wppa-album=" + $scope.item.album + "&wppa-occur=1&wppa-size=640";
    wppaDoAjaxRender( 1, ajaxurl, '' )

    The problem was solved.

    The JS variables are provided by the plugin PHP:

    $data['ajaxurl'] = admin_url('admin-ajax.php');
    $data['siteurl'] = get_site_url();
    Thread Starter nikdow

    (@nikdow)

    Could you do some fall-back error handling and check $_SERVER[‘DOCUMENT_ROOT’] if the include fails?

    /** Load WordPress Bootstrap */
    $inc = dirname( dirname( dirname( dirname( __FILE__ ) ) ) ) . ‘/wp-load.php’;
    if (file_exists($inc) && is_readable($inc)) {
    require_once( $inc );
    } else {
    require_once( $_SERVER[‘DOCUMENT_ROOT’] . ‘/wp-load.php’ );
    }

    Same problem, Wp 4.9.4
    Gallery was working until recently.
    FooGallery Plugin is 1.4.15
    Lots of JS errors like:
    foogallery.min.js?ver=1.4.15:9 Uncaught TypeError: a.Deferred is not a function
    at foogallery.min.js?ver=1.4.15:9
    at foogallery.min.js?ver=1.4.15:9

    JQuery is https://ajax.googleapis.com/ajax/libs/jquery/1.4.2/jquery.min.js?ver=1.4.2

    Thread Starter nikdow

    (@nikdow)

    Thanks for your help and thanks for the awesome font plugin!

    Thread Starter nikdow

    (@nikdow)

    HI thanks for quick answer. We have plugins on auto-update so it would have been running 1.7.0 previously.

    I downgraded to 1.7.0 after the upgrade and the plugin started working again. But I forgot to turn off the auto-upgrade, so 1.7.1 came back a few hours later. This time it worked OK, which has me very puzzled.

    So it’s working now with 1.7.1. I can only guess that it was a problem with the file upload somehow.

    nikdow

    (@nikdow)

    Arghhh, I even know about screen options, thanks for the pointer. Working great now.

    nikdow

    (@nikdow)

    I’ve done all the above, and followed the FAQ:
    A: This is set via the Attribute Title field in the menu item editor in the admin area.

    However there is no Attribute Title field in the menu item editor, only a Navigation Label.

    The source code via the browser’s “show source” for the search field is:

    <input type=”search” class=”search-field” placeholder=”” value=”” name=”s” title=”” />

    I have “Search” as the Navigation label. Website if you have time to take a look is currently at http://olosweb.cbdweb.net/ it’s under development and will move in a week or so to it’s live domain name.

    Thread Starter nikdow

    (@nikdow)

    Forgot to add, this happened to every successful order from April 14th 18:45 onwards.

    I tested a free product (download) on my own test account and the site sent me hundreds of emails until I restarted Apache, which stopped the emails.
    There appear to be two emails sent, one shorter (based on size shown in postfix log) and the other 1000 or so are longer.
    Then downgraded to release 3.0.2 and orderer a different free product.
    Only got one email, problem appears solved.

    Looks like a BUG in WC 3.0.3.

    Site is running latest release of WP on Ubuntu linux, coincidentally upgraded from Ubuntu 14.04LTS to 16.04LTS and simultaneously upgraded HP from 5.5 to 5.6. This did not change the bug behaviour as it occurred both before and after.

    Thread Starter nikdow

    (@nikdow)

    More clues.

    This started happening after April 14th 18:45 Eastern Australian Time
    First occurrence was April 14th 22:22

    WC 3.0.3 was released on github 4 days ago, looks suspicious.

Viewing 15 replies - 76 through 90 (of 116 total)