Forum Replies Created
-
Posts
-
Was it your intention to use the PayPal “sandbox” for a test transaction? And if so, did you setup a sandbox account per these directions?: https://www.paypalobjects.com/en_US/ebook/PP_Sandbox_UserGuide/access.html
I did, but when I go to look at “My Favorites,” it says that I currently have no favorites. It also talks about a custom RSS, and not e-mails.
Because pages are “static,” you must generally wait for them to be crawled by search engines, or stumbled upon by users. Thus, if you have a catalog of items that generally doesn’t change much; use pages. Also, pages are easier to categorize and arrange.
On the other hand, posts get more exposure. Whenever I publish a post, it usually shows up in Google within 3 minutes. Customers who subscribe to your RSS feed will also get faster notification of products. The disadvantage, is that posts are chronologically arraigned, and you run the risk of users thinking certain products are outdated. You also run the risk of pushing too much product via RSS, making your feeds look like Spam.
Yeah, pages it is for selling, and posts for hot product announcements seems a good compromise. Why not use this Tips & Tricks site as an example of how to setup things? They use Posts for product reviews and announcements, and pages for the actual sales.
Post vs Page @ WordPress Support:
It’s **supposed to be** click “activate” in your profile, and then click “Add to favorites” on each post you want notifications on. But, nothing seems to happen when I try adding to favorites 8(
If you install WP in a subdirectory, then your URL will be mysite.com/blog or whatever subdirectory you place it in. If you are comfortable with that ides, then it’s ok to install WP in a subdirectory; and when the time comes to switch sites, do a 301 redirect to the new WP site.
If you want WP in the root directory, there are a couple of ways to go…
1. Setup WP in a subdirectory and then move it to root when ready. Only recommended for new setups. You first setup the minimal number of pages and posts you need; and then transfer the site to the root directory. The reason for having “just enough” setup is that there are some things that have to be adjusted in MySql whenever you move WP. See this…
http://codex.wordpress.org/Moving_WordPress
2. Setup your WP site on a USB stick, using XAMPP. When the time comes to convert, upload the USB version of your WP site to your server. Less things to change, but it’s like running with scissors. You’ll **will** have problems with license keys having to be reactivated after the move.
3. I haven’t tried it yet, but you might get away with it… Move your static site into a subdirectory and then put WP in the root. Use a combination of 301 redirects and a WP plugin similar to Quick Page/Post Redirect to shunt traffic to the old site:
http://wordpress.org/extend/plugins/quick-pagepost-redirect-plugin
Personally, my vote is for #2, because I can do whatever I want to WP without worrying about my production system. Also, you can always hand the USB stick over to a more qualified person, who you only have to pay for transferring the contents of the stick and making the final adjustments.
I think, that because eStore records the squeeze page form data in the customer database, it is not inconsistent to pass the form information on to PDF Stamper. Particularly, in the situation I just described.
In any case, if you don’t think it’s worth doing for the main code; I’d like to get your thoughts on how I might approach the problem myself. I’ll be deliberately high level, so as to prevent others from trying to run with scissors
Modify wp_eStore1.php so that when performing an eStore_free_download, instead of using eStore_includes2.php to generate the link, it uses code similar to that found in eStore_manual_gateway.php to create pseudo $payment_data that can be passed to the link generator in eStore_post_payment_processing_helper.php
Thoughts on this approach?
Okay. Maybe I should explain what I’m trying to do…
I have a post, and at the end, a conditional content display. If the user does not have a certain membership level they see a “Buy Now” button. If they are of a certain membership level, they see a “Free Download” button,” because they are entitled to it as part of their membership.
I would like to have the downloaded file stamped, regardless of if they paid for it or not; because it is licensed material.
Is there some kind of API for PDF Stamper I can use, in which I can pass along the e-mail address of the paid user?
P.S. before deleting the entries from the “Managed Stamped Files” database, I think you should test to ensure the unlink() was successful. Otherwise, in case of failed unlink() like in this situation, the database and the directory will be out of sync.
Sigh, you’re still going to have to code an abolute path to/from URL conversion function…
When trying to delete files under “Manage Stamped Files,” I get:
Warning: unlink() [function.unlink]: http does not allow unlinking in /home/content/44/477758054/html/wp-content/plugins/wp-pdf-stamper/manage_stamped_files_page.php on line 0
I figure it’s because it’s trying to unlink files based on their URL.
Well, now that I know to to tippy-toe around these issues, I can at least move forward; and you get a wee-bit more space in order to properly fix PDF Stamper, LOL.
As for the original problem with the fssek() I kind of suspect that it can only be recreated on a clean installation, that has never had PDF Stamper installed.
Now this is getting weird…
After I got it to work, using absolute paths for everything; manual stamping is suddenly working with URLs.
Perhaps there is some kind of uninitialized database or variable situation going on here? Wil do some more testing and will report back…
Just “for the fun of it,” I replaced the URL of the source file I was trying to manually stamp, with the absolute path and got yet another error:
Warning: fopen(url-of-output-file-goes-here) [function.fopen]: failed to open stream: HTTP wrapper does not support writeable connections in /home/content/45/4753628054/html/wp-content/plugins/wp-pdf-stamper/lib/fpdf/fpdf.php on line 0
I then changed the “Destination Directory of Stamped Files” to the absolute path of the output directory. Note, the default was a URL path.
Now, manual stamping works!!!!!!!!!!!!!!
Okay, so now I’m going to see if I can make this work with eStore. I don’t mind if I have to use the absolute path of the “stamped file directory,” but I’d sure hate having to change the eStore file URLs into absolute paths.
Perhaps, since we now know how to workaround the issue, you could maybe code some kind of function that would convert URL to & from absolute paths?
It’s been awhile since I last used Outlook, but there are 2 things that come to mind…
I seem to remember that Outlook had some kind of security setting to disable links. The other thing I remember is that Outlook had the ability to force all messages into plain text mode, thereby not presenting the user with links that can be clicked on or any other rich text.
