Forum Replies Created

Viewing 15 replies - 1 through 15 (of 36 total)
  • Thread Starter jrcwp

    (@jrcwp)

    tks

    This does stop the plugin from using odd upload directories, but all files are loaded in the main upload folder, not sorted into year month folders as they should be.

    Thread Starter jrcwp

    (@jrcwp)

    Issue resolved?

    Detected and removed “byte order mark” (&#65279) being inserted in one or more files (cleaned a bunch so not sure exactly which file had it).

    This resolved a display bug on the visitor side, and also FooGallery started working too.

    Will now test the Pro version, as that is where we need to be anyway.

    Thread Starter jrcwp

    (@jrcwp)

    Issue #1 solved

    Detected and removed “byte order mark” (&#65279) being inserted in one or more files (cleaned a bunch so not sure exactly which file had it).

    This resolved a display bug on the visitor side, and also FooGallery started working too.

    Still having issues with bug #2.

    Thread Starter jrcwp

    (@jrcwp)

    1) What Functions are not working:

    On the “Edit Gallery” Page > Gallery Items/Manage Items Box

    Click “Add Media” opens the “Add Media to Gallery” box:

    — “Media Library” tab — No thumbs get loaded, and the “loading” spinner spins on forever.

    — “Upload Files” tab — results in this error when uploading a new image: “An error occurred in the upload. Please try again later”

    2) Re the Warning:

    The console “Warning” below only appears when in the FooGallery admin sections. It does not appear for any other WP admin menu items, including the WP Media Library.

    “The specified value “!” does not conform to the required format. The format is “#rrggbb” where rr, gg, bb are two-digit hexadecimal numbers.”
    http://www.domain.com/wp-includes/js/jquery/jquery.js

    Thanks for the help.

    Thread Starter jrcwp

    (@jrcwp)

    Thank you Joy. It does seem to arise only when accessing the FooGallery plugin. I’ll dig there.

    Thread Starter jrcwp

    (@jrcwp)

    bradvin:

    Thanks for the ideas. Debug has been activated. Neither it nor Chrome console detect errors. As noted previously, I have tried deactivating plugins etc — but had no effect.

    • This reply was modified 6 years, 11 months ago by jrcwp.

    I have the same problem, and hope someone can assist. No errors are being logged in Chrome console. I can create a new gallery, but when clicking the “add media” button the image loading screen never loads any thumbs, just spins. Tried Foogallery free ver 1.7.6 and then pro ver 1.7.7. Also activated FooLightBox, but this had no effect. Set concatenation to false. Deactivated plugins etc with no improvement. Am using WordPress 5.1.1. Had previously worked fine on another site having the same plugins and versions.

    This is a code error that Foo has never corrected. Try this to fix it.

    open ‘includes/class-foogallery-attachment.php’ and find:

    if ( ! empty( $this->alt ) ) {
        $attr['alt'] = $this->alt;
    }

    replace it with:

    # fixed: validation issue - missing alt-argument 
    if ( ! empty( $this->alt ) ) {
        $attr['alt'] = $this->alt;
    } else {
        $attr['alt'] = '';
    }
    # added: set title-argument 
    if ( ! empty( $this->title ) ) {
        $attr['title'] = $this->title;
    }
    Thread Starter jrcwp

    (@jrcwp)

    Thanks, but..

    1) the mouse over tip does pop up when the calendar shows an available day (dark gray), but the calendars do not show days available where it should.

    2) No cache plugins running.

    3) site is local. I’ll have to send pics.

    Thread Starter jrcwp

    (@jrcwp)

    The offender was located. Styles being added by plugin “Bootstrap for Contact Form 7.”

    Thread Starter jrcwp

    (@jrcwp)

    This is the code being added during the wp_head action:

    
    <style type="text/css">
    div.wpcf7 .screen-reader-response {
      position: absolute;
      overflow: hidden;
      clip: rect(1px, 1px, 1px, 1px);
      height: 1px;
      width: 1px;
      margin: 0;
      padding: 0;
      border: 0;
    }
    div.wpcf7 .form-inline img.ajax-loader {
      display: inline;
    }
    div.wpcf7 .ajax-loader {
      visibility: hidden;
      display: inline-block;
      background-image: url('https://......./wp-content/plugins/contact-form-7/images/ajax-loader.gif');
      width: 16px;
      height: 16px;
      border: none;
      padding: 0;
      margin: 0 0 0 4px;
      vertical-align: middle;
    }
    div.wpcf7 .ajax-loader.is-active {
      visibility: visible;
    }
    div.wpcf7 div.ajax-error {
      display: none;
    }
    div.wpcf7 .wpcf7-display-none {
      display: none;
    }
    div.wpcf7 .placeheld {
      color: #888;
    }
    div.wpcf7 .wpcf7-recaptcha iframe {
      margin-bottom: 0;
    }
    div.wpcf7 input[type="file"] {
      cursor: pointer;
    }
    div.wpcf7 input[type="file"]:disabled {
      cursor: default;
    }
    div.wpcf7 .form-inline .form-group {
      max-width: 250px;
    }
    div.wpcf7 .input-group-addon img {
      height: 100%;
      width: auto;
      max-width: none !important;
      border-radius: 5px;
    }
    div.wpcf7 .input-group-addon.input-group-has-image {
      padding: 0;
    }
    </style>
    
    Thread Starter jrcwp

    (@jrcwp)

    Takayuki:

    Thanks for the idea. The Contact Form 7 is the plugin that is adding styles in the head. As I indicated, the add_filter codes provided do remove the enqueued file links, but the plugin is adding simple <style> tags in the head, not as a link to a stylesheet.css. I only want that code for when the contact form is included, not on all other pages.

    John

    Thread Starter jrcwp

    (@jrcwp)

    Solved — there must have been an incompatibility. The original test that failed was on wordpress 3.3.1. When all else fails, get things up to date and try again. Now with wordpress 4.2.2 the scan is working fine and it has no trouble with any of the themes – children or no. Thanks for all the ideas.

    Thread Starter jrcwp

    (@jrcwp)

    the last issue was resolved. our spam blocks in htaccess blocked a word used in WP’s admin query string. Now all is fine with 4.1.1. Thanks to all who helped.

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