Jump to content

Leaderboard


Popular Content

Showing content with the highest reputation since 11/05/2019 in all areas

  1. 4 points
    burt

    What is the best way to learn webdesign?

    You might like to speak with Rezoyen who, it appears...sits right next to you... <cough>spammer alert</cough>
  2. 3 points
    JcM Modal reCaptcha Contact V1.0 Phoenix A simple add-on that allows you to replace the stock footer information block with one that has a new simple contact form within a modal with Google reCapture. It also displays the information links in a modal window so customer is never taken away from the page they are on. It’s a simple no core change add-on so just copy files over go to admin and install and setup. Turn off the stock information block. To use the contact form you will need you google site keys. Add the secret key to the mail.php file along with the email address you wish to use. Line 6. $secretKey = 'put your secret key here'; Line 15. $mail_to = "your email here"; Then in the language file add you site key, cm_footer_jcm_modal_information_recaptcha_contact.php Line 75. <div class="g-recaptcha" data-sitekey="put your site key here"></div> That’s it enjoy. Has been tested on Phoenix 1.0.3.0 only. Can be seen working on this custom test site
  3. 1 point
    Dan Cole

    How can i automate a SQL update query?

    I don't know if it's appropriate for your application or not but you could always trigger it on a page call...ie someone visits one of your store pages and the call gets executed. Dan
  4. 1 point
    ArtcoInc

    PHP and the newest cPanel

    I have two live shops. One is running the Community Edition osC v2.3.3.4 (yes, it's that old). The other is running the pre-gold Community Edition osC v2.3.4. I am working on a new site using Phoenix, but that's still in development. I had configured my host to use PHP v5.6 on my shops, and everything was running fine. My host recently did an unannounced upgrade to the cPanel tool set which, unfortunately, upgraded all of my shops to PHP v7.3. Needless to say, there were problems. The first issue I noticed was that I could no longer run the Security Check module in Admin for either shop. I verified that the code against a backup to make sure that it hadn't been hacked. It wasn't until I ran the Server Info module in Admin did I notice that the version of PHP had been changed to v7.3. I logged into my host's cPanel, and discovered that the oldest version of PHP available was v7.0. I rolled back to v7.0, but that did not fix the issues I was having. I contacted tech support through their chat function <grumble, grumble>. I explained the problem, and asked if my sites could be rolled back to PHP v5.6. Yes, but not through cPanel. The new version of cPanel only supports PHP versions 7.0 and up. The tech support person was able to roll back my sited to PHP v5.6 by editing the .htaccess file(s) for all of the sites. They are back up and running now. Server Info shows I'm running PHP v5.6, even though cPanel says I'm running PHP v7.0. I hope this info may assist someone who may run into a similar issue. Malcolm
  5. 1 point
    JcM Modal reCaptcha Contact V1.0 Phoenix A simple add-on that allows you to replace the stock footer information block with one that has a new simple contact form within a modal with Google reCapture. It also displays the information links in a modal window so customer is never taken away from the page they are on.
  6. 1 point
    Jack_mcs

    HoneyPot Captcha

    I'll rewrite the code in the next version. For now, if it causes problems then don't use it for that page.
  7. 1 point
    Jack_mcs

    HoneyPot Captcha

    The intention of the honeypot_verify_contact_us.php was meant to be a catch-all for all of the pages except create account. But I didn't revisit that code in this version since I was concentrating on the create account changes. Looking at it now, I can see some changes are needed but I think it will work. I checked the file you mentioned but don't see the code you mentioned. In general, any page that submits a form will have a line like this if ($error == false) { There may be multiple lines like that. The verify line of Honeypot should go right above the one before the code that accepts the input . Include the verify contact us file should work but any failures will report it is the contact us page where they occurred. That is not a problem with the code but can be confusing. For all such form pages, be sure to put the display line right above the submit button code and to check the page in the Honeypot settings. Please give it a try and let me know if it doesn't work.
  8. 1 point
    Jack_mcs

    HoneyPot Captcha

    No needed at all. I would rather have the suggests than not have them.
  9. 1 point
    Add the buttons to account_history_info, this allows the customer when logged in to print off or save as pdf any orders in the account. Just backup the old file and replace with this. It's for Phoinex 1.0.3.0. account_history_info.php
  10. 1 point
    JcM Prod Info Delivery Note V1.0 Phoenix This is a simple add-on that will allow you to place delivery note on your product info page.
  11. 1 point
    JcM Prod Info Delivery Note V1.0 Phoenix This is a simple add-on that will allow you to place delivery note on your product info page. It requires NO core changes so just copy over the files provided. Once it’s installed simply go to admin and install and turn on. You can change the styling in admin it uses stock BS Class’s. You can also select the placing of the text within the container it’s added to. The symbol used can also be changed. Why would I use this you may ask? Well delivery charges top the polls in the UK: they’re the most common reason for not completing an online order. With this add-on let your customer know at an early stage what the costs are so no surprises at checkout. That’s it enjoy. It has only been tested on Phoenix 1.0.3.0 only. Can be seen working on this custom test site
  12. 1 point
    asro2004

    Stripe v3 module for SCA

    I have created a fork of the standard Stripe payments module to provide support for SCA. I tried uploading it to the market place, but it does not seem to be accepting it. A copy of the zip is attached. Stripe SCA Payment module Stripe SCA is a refactored version of the standard Stripe payments to update the Stripe API to v3 and support the SCA process flow. Other than using different Stripe API calls to set up and process payments, the main change is to defer order fulfillment to a web hook called by Stripe after the payment has been authorised. This module is installed as a separate payment method from the standard Stripe module and can be run in parallel. Note that it shares the customer_stripe_tokens table created by the standard Stripe module, and cards saved using the standard Stripe module can be reused by the Stripe SCA module, however, cards stored by the Stripe SCA module cannot be reused by the standard Stripe module. They will be rejected by Stripe with a message 'You cannot create a charge with a PaymentMethod. Use the Payment Intents API instead.' Install Copy the contents of this zip to the root osCommerce folder of your store. Login to the osCommerce Admin page of your store and go to Modules > Payment. - Click on the Install button at the upper right of the page - Choose 'Stripe SCA' from the module list and select Install Module. If you are allowing cards to be saved, add the cards management page: - go to Modules > Content - click on the Install Module button at the upper right of the page - select 'Stripe SCA Cards Management Page' and select Install Module. That will add the 'Manage saved payment cards' link to the customers' My Account page. Configuration The basic configuration of the Stripe SCA module is the same as the standard Stripe module, requiring Publishable and Secret API keys, however as the order fulfillment has been moved to a webhook, you need to add the address of the Stripe SCA webhook at your store to your Stripe account dashboard, and add the webhook signing secret it generates to the Stripe SCA payment module configuration. Login to your account at the Stripe web site, and select Developers > Webhooks - select '+ Add endpoint' at the upper right of the page - set the URL to: https://yourstore.url/ext/modules/payment/stripe_sca/webhook.php - select version as 'Latest API version' - select event 'payment_intent.succeeded' and 'payment_event.payment_failed' - click 'add endpoint' to save the webhook endpoint. Then select the new endpoint URL from the list of end points, and then 'click to reveal' to see the Signing Secret. Copy and paste the text of the signing secret to the Webhook Signing Secret in the Stripe SCA module configuration form. The Stripe SCA module adds a log table, stripe_event_log, to the database, and if you select 'Log events?' in the Stripe SCA configuration, it will record each Stripe API call with the parameters that are passed to Stripe and the response received. As the process flow has changed to use a web hook, the order has to be created in a pending state, and then updated to completed status after the payment has been authorised. Consequently, you need to set the new order status to 'Preparing [Stripe SCA]', and the order status is set to the status the order is to be set to, after the payment is authorised. Technical Notes The current stripe-php library, as at module publish date, has been included in in the module install. Calls to the Stripe library functions have replaced directly sending transactions to the Stripe gateway. You should be able to replace the includes/modules/payment/stripe_sca folder with the complete contents of the stripe-php library when Stripe releases updates to their library. If you do so, set the new API version in includes/modules/payment/stripe_sca.php. The Stripe v3 process flow now requires a PaymentIntent to be created before the payment page is displayed, and a 'data secret' it generates to be included in the HTML form. If a saved card is used, the Stripe customer id and payment method id has to be added to the PaymentIntent. During coding, it was found that a payment method could not be removed from a PaymentIntent, so rather than update the PaymentIntent with a server call as the saved card/new card is selected, the adding of the customer and payment method is deferred until immediately before submitting the payment to Stripe in a Javascript call when the form is submitted. The payment_intent.php server hook is also used to save the value of the 'save card' check box in the PaymentIntent so it is accessible to the webhook called after the payment is authorised. Stripe v3 provides UI elements to collect card details. A 'card-element' element is required for the new card to show card number, expiry and CVC fields, but is also required for saved cards in order to provide a place holder that Stripe can use to display authorisation prompts if required. Consequently, two occurrences of the 'card-element' element were created with the name of each toggled depending on whether a saved card or new card is selected. Otherwise, trying to reuse the same element for both purposes block the authorisation of saved card when the new card details was hidden. All order fulfilment and card saving code has been moved to ext/modules/payment/stripe_sca/webhook.php. Note the DIR_FS_CATALOG constant should be set to a path string, rather than the value dirname($_SERVER['SCRIPT_FILENAME']) . '/' because the includes/modules/payment/stripe_sca.php has a require that references the stripe-php library, and is executed at different locations in the directory structure and fails when the DIR_FS_CATALOG value varies with location. stripe_sca_v1.0.zip
  13. 1 point
    asro2004

    Stripe v3 module for SCA

    Security issue There can be a security problem for anyone who installed version 1.0.3 of this module, with some obsolete values being left in the configuration table when the modules is updated to a later version. Please run the following SQL to remove the obsolete values: DELETE FROM configuration WHERE configuration_key IN ('MODULE_PAYMENT_STRIPE_SCA_PUBLISHABLE_KEY','MODULE_PAYMENT_STRIPE_SCA_SECRET_KEY','MODULE_PAYMENT_STRIPE_SCA_WEBHOOK_SECRET')
  14. 1 point
    piernas

    Ultimate Seo Urls 5 Pro

    It's ready. - Latest oscommerce (phoenix 1.0.3.0) compatible. - Fixed more cache issues. Now sqlite and memcache are only enabled if system supports the methods. - Moved admin edits to hooks. Now only two files on catalog needs to be modified. - Removed database table constants. - TODO: Allow to processs links outside root folder (ie. ext/directory). This is useful for addons like Twitter typeahead. Can someone test the atached files before uploading to addons? USU5_210.zip
×