- This topic has 6 replies, 3 voices, and was last updated 14 years, 7 months ago by
.
-
Posts
-
Help! The encrypted link in the post-purchase email and thank-you page is not working. It fills the screen with a bunch of binary nonsense and gives the following error:
Warning: Cannot modify header information – headers already sent by (output started at /home/jackiepdx/bettersmarterricher.com/wp-content/plugins/wp-cart-for-digital-products/download.php:85) in /home/jackiepdx/bettersmarterricher.com/wp-content/plugins/wp-cart-for-digital-products/download.php on line 88
Hi, I have replied to you via the email you sent me. Please see this email. If you do not receive the email please let me know.
Cheers,
Ivy
I got your email Ivy. Thanks for replying so quickly. I want to ask you here, though, whether it was actually you who sent me that second email asking me for my wordpress login and password info. It felt a little suspicious to me. I cannot imagine why a programmer would need that kind of access. I wanted to ask you on the forum in case the email was not legitimate. Have you had problems with people faking emails from you trying to get people’s passwords?
Emanuel
Ok I think I just fixed it. Basically, I deleted line 85 of the download.php file. THis line to be exact:
ob_flush();
Now it is working fine. I did this after spending a whole lot of time to no avail removing blank lines at the end of various php files that I thought might have been sending header information. When none of that worked I just decided to delete the offending line in the error message. Well it works now. My only question is whether this is going to screw something else up. What does that line do anyway? Is it needed for something important?
Emanuel
The function ob_flush() sends the contents of the output buffer (if any). It’s use varies depending on the server’s PHP configuration. In your case it will not make a difference.
Without going into too much detail, the key message to keep in mind is that the plugin is coded for a typical server setup meaning it will work on most servers out of the box but if you read my “How to get help” post from the following URL then you should know that I do not guarantee that the plugin will work on your server simply because there are too many variations of server configurations out there:
BTW, I do encourage everyone to read that post before they make a purchase.
I am glad I was able to fix this problem. So far the plugin seems great, and I am excited to use the affiliate plugin with it. I am also going to recommend to my client she switch her mailing list to aWeber or Mailchimp for better integration (do you recommend one over the other?). And if all this integration works, then I will likely be buying more copies from you for my other clients (both current and new).
I would jot down this particular problem so you are able to quickly help others. Basically, the ob_flush() was sending output to the server, which caused the header function a few lines later to screw up. Your tech people thought the problem was empty spaces in the file before or after the php start/end tags, which is a common cause of the “cannot modify header” error. But that was not the cause in my case. If you notice the error message I included above in my original post, it says:
“(output started at /home/jackiepdx/bettersmarterricher.com/wp-content/plugins/wp-cart-for-digital-products/download.php:85)”
This is an indication of where the problem was. It was on line 85 of the download.php file.
Emanuel
Cool… yeah in your case the line number did help but there are usually a few different variations whereby this can occur (sometimes the line number it comes up with is completely wrong):
1. If the FTP program that you used to upload the file didn’t transfer the files in binary mode it adds spaces after every line.
2. Of course the addition of space in the header is a common one.
3. Sometime the file format can get changed from UNIX to DOS (if you are on a Windows server – I am not even going to argue on the whole windows server and IE thing).
4. The ob_flush() that sends the buffer content can also cause that error depending on your server configuration.
Anyway, these happen rarely so it’s not a big deal.
- You must be logged in to reply to this topic.