MountainMan

I prefer NOT to get credit card info on my website. For years have been using 2CheckOut.com (they have gotten really lousy, so need to dump) and PayPal. Both of these payment options collect credit card info on their respective websites, and then return to mine. Is there a way to use the Stripe add-on like this. Or perhaps (easily) mod the code so that it does?

Thanks. Which version(s) are the latest and greatest has gotten confusing. Can you school me on that?

Answering my own questions: 1. The single "=" is required because there is in fact an assignment to the variable $error going on there 2. $error['title'] is assigned in the get_error() functions found in the order total modules 3. Above my pay grade The reason the error messages were not showing up was because I left off a "return" in the get_error() function I was repurposing.

Error message is not displaying in checkout_payment. Am looking for tips in how to diagnose. This bit of error handling code has been around a long time. In OSC 2.3.4.1, it starts at line #130 in checkout_payment.php if (isset($HTTP_GET_VARS['payment_error']) && is_object(${$HTTP_GET_VARS['payment_error']}) && ($error = ${$HTTP_GET_VARS['payment_error']}->get_error())) { First question I have, is: Why is there a single "=" instead of a "==" for the "$error = $" in the line above Second question is: Where does "$error['title']" come from? I am assuming it is an array element...but where created and loaded with data. I know these error messages come from payment or order total modules, but I cannot find any code referencing "title". echo '<strong>' . tep_output_string_protected($error['title']) Third question: Why is OSC 2.3.4.1 still using $HTTP_GET_VARS ? Thought we were past that.

Got this error trying to login into Facebook: Facebook has detected xxxxx isn't using a secure connection to transfer information. Solution seems to be add SSL osc style to line 22 in login_with_facebook.php. $ezsocial_uri = tep_href_link('login_with_facebook.php', '', 'SSL');

Hi there, Is this still an active and recommended addon? Am testing an initial install. Using Google to login, it throws me back to my website an my error handler, showing me a 403 error. Dont even know where to start with that.... BTW, the Google account I am using contains an email address that should flag me as a new customer to my osC shop. I am assuming this addon can handle that...right?

Updated my site to PHP 7.1 and osC CE by porting over my mods. Lost functionality of MailBeez, and now trying to sort it out. Am stuck on this error: Declaration of config_queen::update($installed_version) should be compatible with configbeez::update($installed_version = NULL) in ...../mailhive/configbeez/config_queen.php on line 23

Well, thanks for the info. Hopefully someone can give me clue as how the module works and in what file the changes to the URL occur.

Thanks for the info. Can you tell me where to look, in order to fix? I have looked at product_listing.php itself, including past SEO versions, and dont see anything about UltSEO there.

Am wondering if I have this installed/working correctly, maybe I am missing something, or maybe its working properly. Within a list of products generated by product_listing.php (for a category), the links visible in the lower left corner of the browser by hovering the cursor over the Product Name seems to be the regular OSC type, like this: /catalog/product_info.php?cPath=5_11&products_id=121 . Whereas when I click on the link and go to the product, I see a URL up top that says something like: /catalog/great-product-p-121.html ... ....which I presume is generated by the Ultimate SEO module...and I also presume this is what I would rather see (when hovering) generated by product_listing.php instead of the cPath version. Yes, no, maybe. Totally not necessary. Hey, a good idea and I will whip that up in a sec. ???

How does one doublecheck and/or view the sitemap(s) created for accuracy and errors?

That's always an option.

Live vs sandbox is obvious, I was confused by the API credentials, partly because I was used to the older PP Standard setup in Admin (which was simple), and also because "API" is often used for different/direct/programming access on other platforms. I initially thought I should only be concerned with Live or Sandbox setup. Also adding to the confusion was nothing was working as advertised, because, of course, its a bastardized port over. The three "buttons" - I was seeing the PP App Start page with three "panels" for retrieving the Live, Sandbox and API credentials. I did not find it clear, should I setup the API first? In any case, I slugged threw the code, and also had to make some manual entries in the configuration table because they werent saving, but am now finally seeing PayPal as a payment option and can click thru to PayPal to make payment, and am just about to see if a test payment will work. Thanks for your response. The community is much appreciated.

Hi there from the USA. Have been porting an OSC 2.3? site over to BS\GOLD. (Started a while back, and now coming to finish it, I see "frozen". Drat, more more more work.) FYI, I harvested the PP App 5.018 (which did not come with Gold) from github, and copied it over to my new work. The App would not do an update from 5.10, so I tried the manual approach. So far, so good. Except for the PayPal app. Previously was using PayPal Standard, which is still setup in the configuration table. Firstly, its confusing about retrieving the credentials - Live vs API. Do I need both? If yes, which first? Secondly, my credentials are not being retrieved. When I press any of the buttons, the page just reloads. In desperate need of insight...

Can anyone tell me where/how the variable $customer_discount is initialized?