Forum Replies Created

Viewing 15 replies - 1 through 15 (of 18 total)
  • I think there is a ‘diff’ option for unknown files that are human readable – e.g., .txt, .php, etc. I was able to display the difference between a ‘known’ and ‘unknown’ readme.txt file – curiously, the only the difference was a couple of inconsequential comment lines that had been removed.

    I’m more worried about image, exe files, and .cur??? (what it that?) for which there is no good diff option. How to know what to delete without messing things up? Some of these files appear to be related to plugins that are in use and necessary…

    Beyond annoying… Unless fixed ASAP I’m out hours of work to switch to an alternative – how can I back off to previous release?

    Thread Starter jack96161

    (@jack96161)

    Thanks for the quick reply – I’ll look at the theme I’m using more closely. Great plugin, by the way!

    The big question is — are all the failing sites hosted with the same company? I have a dozen sites that are running the latest WordPress and Contact-7 releases with no problems whatsoever.

    The only ones that failed were hosted on servers that use the Qmail email system, as many hosting companies do… In every one of those cases, updating the class-phpmailer.php file to the version that will be included in WordPress 3.7 solved the problem. If problems still persist, it’s most likely a plugin or template problem involving misuse of the current jQuery library installed by WordPress 3.6.

    Contact-7 is not at fault. Either blame WordPress for releasing 3.6 with the previous version of class-phpmailer.php… or, the hosting company for running Qmail — however, Qmail, a Unix based replacement for the older Unix sendmail, has many advantages over sendmail, especially superior security measures, which is why Qmail is more prevalent in serious security conscious hosting companies.

    There is actually a bug in the 3.6 release that causes Contact-7 forms to fail to be emailed – but it only affects those hosts using the Qmail based email systems. It appears that WordPress used a few month old version of class-phpmailer.php one where a bug had been introduced for Qmail based email systems, the Authors of phpmailer.php had already issued an update for the file but WordPress issued the 3.6 upgrade with class-phpmailer.php version 3.5.4 (version 3.5.5 had already been fixed). In any event they are now aware of the issue and have already indicated that a more current version of class-phpmailer.php (one that is fixed for Qmail) will be included when WordPress 3.7 is released.

    Meanwhile, If you go to this link:
    https://github.com/PHPMailer/PHPMailer/blob/master/class.phpmailer.php
    And copy the actual file contents starting with:
    <?php
    /*~ class.phpmailer.php

    Then replace the contents of your wp-includes/class-phpmailer.php with the code from the above file, that should correct the issue if related to the Qmail bug. NOTICE!!! the name of the file is class(dash)phpmailer.php, not (dot) as it appears in the second line comment of the source.

    Thread Starter jack96161

    (@jack96161)

    Yup, so I discovered… Thanks.

    Thread Starter jack96161

    (@jack96161)

    You’re right about one thing — I’m not the intended clientele for a tool that cannot be used with a widely used class of shared server hosting companies. However, to call then “low-end” because they don’t care to expose their customers to potential abuse by other customers sharing the same server is unfair. I don’t deal with the widely popular $5-$10/mo services that provide very uneven service on rarely monitored, frequently unbalanced shared servers. Incidentally, I prefer the more accurate term “el-cheapo” to “low-end”. As you probably know, some of them do allow the kind of encroaching user access this application requires, but that doesn’t make me want to use or recommend them.

    Truth is, I’m (mostly) retired, and the few dozen sites I maintain do not require a tool like this, but it looked interesting and it’s limitations were both not described in the introductory information and did not become apparent until after I had downloaded and installed it. I reported this to the developers and since I haven’t checked their site since then, they may have corrected this by now.

    Given the very large and complex server level software I am able to install and make good use of on the shared server hosts I make use of, I find it hard to believe that this application could not be developed to function efficiently in these environments. I maintain some quite high volume sites, including several large eCommerce operations and do beta testing for a number of emerging SAAS applications. I’ve encountered a number of cases where I had to upgrade to a higher level of service because of high volume requirements, but this is the first time I’ve run into these somewhat petty requirements.

    A bit of up-front honesty on the part of the developers to explain these limitations and simply recommend that this is not a tool for the users of shared server technology would have saved all of us some trouble as well as this far too extended dialog. Let’s turn off the email follow-up post option for this thread and leave it at that…

    Thread Starter jack96161

    (@jack96161)

    I do understand all of what you are describing here (50+ yrs in the computer profession and 46 yrs experience with the Internet, starting as a staff member in Stanford Research Institute working on the ARPAnet project, cica 1967).

    However, it is not just “low-end” hosting services that that restrict these questionable practices. I make use of very reliable, competent services and pay the price for that service. My favorite service provider, who I have had impeccable service from for 8 years or more, disallows some of these shared user “freedoms” for the very reason you acknowledge — open ended security risks. I’ll stick with their experience and history.

    The WilderNet has become a dangerous enough place to work and play without exposing my clients to additional risks — this package is not worth it until I have cause to move to dedicated servers.

    Thread Starter jack96161

    (@jack96161)

    Actually, note that I dealt only with shared service hosts — allowing you to alter settings that allow you to consume more resources for yourself and reduce the services I’m paying for, and/or introduce security risks that jeopardize my site doesn’t make me want to use that service or recommend it to others.

    I repeat, their unwillingness to make their software run on shared hosting services I can recommend to my clients makes it unusable for me — and I have been told by others they share the same problem. If you can afford and are willing to self-manage your own dedicated servers, more power to you — but leave me off your system. There are other solutions out there.

    Thread Starter jack96161

    (@jack96161)

    I tried that at first, but the designer had other constraints – different headings on different pages, and may make “adjustments” later, so a fixed background would have been a nightmare to keep modifying. This works great and is much more flexible.

    Great plugin BTW, and the new responsive version came just in the nick of time — thanks.

    Thread Starter jack96161

    (@jack96161)

    Got it — had to change the .meteor-clip class position to static…

    Besides the multiple gallery problem, I had a number of issues with the GalleryView addon plugin which worked with previous releases. The ScrollGallery plugin seems to be more stable, but NextGen is getting to be seriously complicated and heavy-weight for most uses.

    I’m open to other solutions that allow a selection of images from a scrollable set of thumbnails that is supported and compatible with latest releases of WordPress.

    sammond7 — I need a solution to the problem with multiple nextgen galleryview galleries on one page. Any suggestions?

    Thanks

    Thread Starter jack96161

    (@jack96161)

    OK, found the option in 4.2.4 — works, but would like to push

    _gaq.push([‘_link’, ‘http://drmiller.pinnaclecart.com’%5D); return false;

    instead of

    javascript:_gaq.push([‘_trackEvent’,’outbound-article’,”]);

    Thread Starter jack96161

    (@jack96161)

    Thanks Daniel — I missed the “Add New” button to set up a new job. It did create the files and looks like it’s working fine.

    Danke Vey viel!… both for developing this plug-in and the quick response!

    Jack

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