Forum Replies Created

Viewing 15 replies - 1 through 15 (of 19 total)
  • Yes, thank you. Was looking for a simple plugin that inserted the tracking code with analytics id and perhaps some wordpress optimized event tracking.
    I prefer to use the google analytics built in reports and do not need the backend CMS reporting in my sites dashboard.

    Yep, the culprit was a “No Right-Click” plugin. We disabled the plugin and the problem went away.

    Thanks for your help!

    Ah, good catch! I think the blog owner has installed some measures trying to prevent her content being plagiarized. I imagine that’s the root of the issue.

    Thanks!

    The pinterest images are set for the default of 800 x 1200 uncropped. We are using the W3 Total Cache plugin, but I didn’t realize we needed to exclude the Pinterest agent. Wouldn’t the same meta tags in the header be included in the cached copy?

    The error happens on the next step after your last screenshot. When you select a board and then click “PinIt!”

    http://www.awesomescreenshot.com/image/1153025/7bb014f1f6c76b29aa7f732544dd44c9

    Hi Jason,

    Sorry for the delay. I just tested your updated version and everything worked for me!

    Thank you!

    Jason helped me to troubleshoot my problem, and in my case it turned out to be a character encoding issue with the multi-lingual greeting line in the test email template.

    To resolve it I did a search operation on the word Bonjour and there were three places in the plugin where the greeting line is located. I deleted the special characters from all three of those places and the test email now works correctly.

    Hi Jason,

    Yes, I would be happy to. I will also email you the two transcripts, one of the blank test email, and the other of the non-blank woo commerce email.

    I did notice that in the advanced settings, it shows “Invalid” next to the Temporary Directory. Is the temp directory necessary?

    When I try to post the entire transcripts the forum isn’t publishing the post for some reason. But I can see the content in the Woo Commerce email’s transcript is complete, but the test email the body content portion seems to be missing. Even though the content still shows up in the Log if I click View instead of transcript.

    I am having the same issue. Emails sent using the Settings -> Postman SMTO are delivered but the body content is blank. But Emails sent using the Woo Commerce backend are sent with the HTML body content still intact. In case it matters, I am running a Windows webserver with IIS.

    I am having the same issue. Emails sent with the Settings -> Postman SMTP test feature are delivered, but the body content is blank. Emails sent using the backend of Woo Commerce do contain the HMTL content though. In case it may be relevant, I am using a Windows webserver running IIS.

    Transcript for delivered but blank test email:

    220 email-smtp.amazonaws.com ESMTP SimpleEmailService-1207641145 jyToMe4Pth5u0tPUle4w
    EHLO localhost
    250-email-smtp.amazonaws.com
    250-8BITMIME
    250-SIZE 10485760
    250-STARTTLS
    250-AUTH PLAIN LOGIN
    250 Ok
    STARTTLS
    220 Ready to start TLS
    EHLO localhost
    250-email-smtp.amazonaws.com
    250-8BITMIME
    250-SIZE 10485760
    250-STARTTLS
    250-AUTH PLAIN LOGIN
    250 Ok
    AUTH PLAIN
    334 Ok
    AEFLSUFJQ1FESUQ2TkVHRlozNVJBAEFtc2VXSjlid0pGREp4MWRPWFIyWG5scjVmaHVhYmszdXA0andaZTRYODFx
    235 Authentication successful.
    MAIL FROM:<development@redacted.com>
    250 Ok
    RCPT TO:<mark@redacted.com>
    250 Ok
    DATA
    354 End data with <CR><LF>.<CR><LF>
    Content-Type: multipart/alternative;
     boundary="=_d663dc61b3312d1ff4cd6a5b4637c9a9"
    From: BVT Development <development@redacted.com>
    Sender: development@redacted.com
    To: mark@redacted.com
    Subject: Postman SMTP Test (howtocookthat.redacted.com)
    Date: Fri, 02 Oct 2015 21:39:39 +0000
    MIME-Version: 1.0
    
    --=_d663dc61b3312d1ff4cd6a5b4637c9a9
    Content-Type: text/plain; charset=UTF-8
    Content-Transfer-Encoding: quoted-printable
    
    --=_d663dc61b3312d1ff4cd6a5b4637c9a9
    Content-Type: text/html; charset=UTF-8
    Content-Transfer-Encoding: quoted-printable
    
    --=_d663dc61b3312d1ff4cd6a5b4637c9a9--
    .
    250 Ok 000001502a7c1091-8fe36112-9212-464c-9e46-7ec4c375ab27-000000

    We are seeing the same problem. We have a role for comment moderators and as soon as we activate this plugin, they can no longer moderate wordpress comments, even though they still have the “moderate_comments” permission still applied.

    We may have to de-activate this plugin until a solution is found. : (

    My issue is resolved, and probably not the same one as the others posting here. In my case we had a varnish proxy installation that was stripping cookies without our knowledge.

    Thanks!

    wp-login.php did work correctly.

    I finally figured out the problem. The webhost people on the production server had configured varnish to strip cookies on all pages except the ones with specific exclusions. The new login / logout pages did not have exclusions, so they had their cookies stripped by the varnish proxy.

    Once we had them add exclusions everything worked as expected.

    Thank you!

    Here is the response header from the development server running the same code. You can se the response cookies are being sent:

    HTTP/1.1 302 Found
    Date: Fri, 24 May 2013 02:18:23 GMT
    Server: Apache/2.2.22 (Ubuntu)
    X-Powered-By: W3 Total Cache/0.9.2.11
    Expires: Thu, 19 Nov 1981 08:52:00 GMT
    Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
    Pragma: no-cache
    X-Pingback: http://domain.com/blog/xmlrpc.php
    X-Frame-Options: SAMEORIGIN
    Set-Cookie: wordpress_548d950a57c83d7fc5c2eb781062ef26=SubscriberTest%7C1369534704%7C08d4578ca9049beadffa39e0be0ea941; path=/blog/wp-content/plugins; httponly
    Set-Cookie: wordpress_548d950a57c83d7fc5c2eb781062ef26=SubscriberTest%7C1369534704%7C08d4578ca9049beadffa39e0be0ea941; path=/blog/wp-admin; httponly
    Set-Cookie: wordpress_logged_in_548d950a57c83d7fc5c2eb781062ef26=SubscriberTest%7C1369534704%7Cc41eb224ebec7f57982d0f93e70f7cff; path=/; httponly
    Set-Cookie: wordpress_logged_in_548d950a57c83d7fc5c2eb781062ef26=SubscriberTest%7C1369534704%7Cc41eb224ebec7f57982d0f93e70f7cff; path=/blog/; httponly
    Location: http://domain.com/
    Vary: Accept-Encoding
    Content-Length: 0
    Keep-Alive: timeout=5, max=100
    Connection: Keep-Alive
    Content-Type: text/html; charset=UTF-8

    The upgrade path may be a key to the issue. I have development server that works and a production server that does not.

    One difference is that I upgraded the development server from 6.3.6 all they way up to 6.3.8 (I can’t recall if I did the intermediate 6.3.7 update or not) while I was working on a major site update. The production server did not use the plugin prior to this major site update, so when I went to deploy I installed 6.3.8 directly in the backend, and then copied the dev server files over it. I have since tried to revert just like admintiger mentions (deactivating, uninstalling plugin and data, and then installing 6.3.6) but the log off behavior refuses to work. In my case the sign-in behavior is broken also.

    I am trying to dig through the packet logs with a sniffer to see if I can find the differences between my two servers. The code appears to be identical, so I suspect there is a DB issue.

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