Jump to content

Leaderboard


Popular Content

Showing content with the highest reputation since 11/11/2019 in Posts

  1. 4 points
    Jack_mcs

    HoneyPot Captcha

    A new version has been uploaded with these changes: Added a page in admin to find and delete suspected fake accounts. Original code supplied by @Chadduck . Added a page in admin to allow deleting an array from the tracking table and to view the log. Added an option to verify the submitted IP. Added an option to verify the postal code. Added an option to verify the state and country pair is valid. Added an option to check the time to submit a form. Added filesize to dislay of the cron job results. Changed the option for the Math Captcha to use an image or text. Changed the captcha.php file to include a missing parameter. Found by @puggybelle Changed the mysql command to work for non-standard database names. Found by @Chadduck. Changed the cron output to show the size of the file. Changed the IP List setting to include check TOR IP's. Changed the names used in the hidden fields in case hacker scripts scan for the common name of honeypot. Corrected a typo in the error messages. Found by @puggybelle. Corrected the session name in captcha.php. Found by @ecartz. Fixed problem with the cpatcha code so it now works correctly. Removed a line of test code that was overlooked. Removed the notification option. All emails are now sent using the log tracker option.
  2. 3 points
    Well meant advice; You have multiple hook files performing the catcha routine ... this can be done from one hook file. Take a look at the core bootstrap example where it is placing "stuff" in two different locations; https://github.com/gburton/CE-Phoenix/blob/master/includes/hooks/shop/siteWide/bootStrap.php#L23 & https://github.com/gburton/CE-Phoenix/blob/master/includes/hooks/shop/siteWide/bootStrap.php#L30 Having just one File with all the hooks (for a given "XYZ" [in this case captcha]) in it, is; simpler for you in terms of support simpler for user in terms of having to upload/delete etc let us say that the user wanted to not use your captcha anymore, and deleted the file that displays the form...the other files gets missed somehow...they have a broken site. Not good for them [loss of potential sales], not good for you [support issues], etc etc Hooks are a big part of Phoenix' future, so well done on being one of the pioneers of them.
  3. 3 points
    Not in the app's store just download from here. JcM index new products V1.0 Phoenix A simple add-on to let you display an index new products on your site This allows you to set the number of days from which the new products are selected. If no new products added in that period nothing is displayed. So you could set it to show new products added in last week, month or year. You can change the title to whatever you prefer “New products this week” It also make use of a small bit of code to allow you to have the image change on mouse hover (this is done using a small snip-it of code posted by @kgtee in the forum. To use the image change you need to add both the main image and one large image. As you will see the display has been changed to show a nice compact view with the product name disabled and the image set in the top of the card. The product name can be turned on again if required in admin. Again totally stand-alone with no core code change. Simply copy all files into relevant sections and go to admin and install. That's it Enjoy. Can be see working on this site JcM index new products Phoenix V1.0.zip
  4. 3 points
    burt

    Phoenix Announcements

    Phoenix 1.0.4.0 Demo Site: https://template.me.uk/phoenix/index.php v1.0.4.0 fixes a few bugs in the shop side as well as introducing database enabled hooks and the very first step towards a better template implementation, in addition the manufacturers class is now used in more places. On the admin side we have a better bootstrapped layout (header/footer) and a few more pages have been converted to bootstrap tabular layout. We have some more modules, particularly note the "testimonials" page in the shop side is now modular. If you are on v1.0.3.0, it's an easy update. If you are on an older Phoenix, you'll need to get to v1.0.3.0 first before attempting the below steps. A big thank you to everyone who made the release of v1.0.4.0 possible, especially to the Supporters as well as to @raiwa @ecartz and "F Figue". This release introduces a number of improvements; the foundations of an integrated Template System this has been asked for many times over the years, now it's becoming reality... more bootstrapping in admin with more to come in future releases... admin Boxes made 100% modular How to Update if on 1.0.3.0; Uninstall defunct modules;- Social Bookmarks BOX (main module + all installed child modules)- Card Acceptance BOX Delete defunct files (eg using FTP)- admin/includes/classes/rss.php- includes/modules/boxes/bm_product_social_bookmarks.php- includes/languages/english/modules/boxes/bm_product_social_bookmarks.php- includes/languages/english/modules/social_bookmarks/<all files in here>- admin/includes/modules/cfg_modules/cfgm_social_bookmarks.php- includes/modules/boxes/bm_card_acceptance.php- includes/languages/english/modules/boxes/bm_card_acceptance.php Download this Zip, unzip and upload + 1040.zip Run this SQL in (eg) phpmyadmin)+ https://pastebin.com/c7p4WtL2 How to Update if on earlier version; Find version you are on [admin > tools > version checker] Go back through this topic and perform updates to get to 1.0.3.0 Then follow "how to update if on 1.0.3.0 & after which" instructions - OR - You can download and install a brand new 1.0.4.0, obviously making sure not to overwrite your live shop; clicking the green "clone or download" button at https://github.com/gburton/CE-Phoenix or grab it direct from osCommerce at https://www.oscommerce.com/Products choose "download zip" unzip, upload, install - OR - You can diff your files; Find which version Phoenix you are on admin > tools > version checker go to this URL, changing a.b.c.d to your Phoenix version; https://github.com/gburton/Responsive-osCommerce/compare/a.b.c.d...1.0.4.0 Make code changes one by one it'll take you a while, but if it floats yer boat... - THEN - After Installation (whether NEW or UPDATE) is complete; Visit admin > tools > security checks and perform any needed actions Enjoy using 1.0.4.0 - Join the Phoenix Club - https://forums.oscommerce.com/clubs/1-phoenix/ you'll get to see some of the "behind the scenes" work and help to steer future releases.
  5. 2 points
    Thank you very much Matt @ecartz for your support !!! I already updated the PHP version to 7.1 and everything works correctly. You're a genius!!! One suggestion to @burt, if the user does not have the appropriate PHP version that work with Phoenix , the installation program should not let you proceed with the installation .... It is frustrating to reach the last stage of installation, go to ADMIN and find an error message Its only a recommendation, as a user I prefer to know that I can not move forward with the installation until I get the PHP version than reach the end on the instal and find an error. New users may not go to the forum to seek help, they will only stop using Phoenix. Best regards Valqui
  6. 2 points
    ecartz

    Error installing Phoenix 1.0.4.0

    Phoenix requires PHP 7+ If you want to fix the error, change $module_width = $ad->content_width ?? 6; to $module_width = isset($ad->content_width) ? $ad->content_width : 6; and that particular line will work again. But expect more problems if you try to run Phoenix on PHP 5.
  7. 2 points
    puggybelle

    HoneyPot Captcha

    @Jack_mcs I don't know what you did, but THANK YOU! All works perfectly now, with captcha enabled, in both create account and contact us pages. You're one of the best contributors of all time in this forum - thank you for all of your hard work and for sharing it with the community! - Andrea
  8. 2 points
    JcMagpie

    Update Order Emails

    This is not part of the stock code in osC so will probably be part of the add-on you installed. Check to be sure it's in the zip file you down loaded and has been copied over to the right path. Also many of the add-on's are no full packages! some only include the updated files so make sure you downloaded a full packeage. Also consider using the updated comunity version of the code. https://www.oscommerce.com/Products
  9. 2 points
    raiwa

    Display Tax Info V3.0

    Uploaded Update for Phoenix flagged for Phoenix: Display Tax Info Phoenix Changelog Version 4.0 - updated for Phoenix 1.0.3.x - moved currencies_mod class extension into siteWide hook. This allows to use it also for modularized shopping cart and other modularized pages with content module call in data section of the page.
  10. 2 points
    raiwa

    List of my Phoenix compatible Addons

    Uploaded: Points and Rewards Phoenix
  11. 2 points
    raiwa

    install 2.3 modules to Phoenix?

    Most modules will need the following updates: replace the class constructor name (first function in the module) to "__construct" for PHP 7 compatibility replace the path constants like "DIR_WS_INCLUDES" to hardcoded paths like "'includes/' FOr to know which have been removed compare the "includes/configure.php" files from your old store to the Phoenix files. The definitions which are not in Phoenix any more need to be replaced replace all database table names like "TABLE_CONFIGURATION" with hardcoded real names "'configuration'" if the module produces any html output, it might need to be updated to bootstrap 4. if the module uses any jquery script, it must be injected now in the footer script area. compare to some ht modules how it is done there Best is to have al look in the supplied core modules and compare
  12. 2 points
    mddel

    Product listing

    Annual subscription has been paid and we wish the team all success with the project
  13. 2 points
    Does adding a define('META_SEO_TITLE', 'Our GTCs'); help? May require ht_pages_seo to be installed in admin > Modules > Header Tags (if it is not already). You may also want to look at how ht_product_title.php works and adapt for your use. I'm thinking of copying that file to ht_heading_title.php, changing the class name and $code to ht_heading_title, replacing all instances of PRODUCT_TITLE with HEADING_TITLE, and replacing the contents of the execute function with something like function execute() { global $PHP_SELF, $oscTemplate; if (in_array(basename($PHP_SELF), [ 'attias_beratung.php', 'attias_impressum.php' ])) { $oscTemplate->setTitle(HEADING_TITLE); } } Adjust the list of file names as necessary for your shop. Remember that you have to install the module in admin before it will do anything. You want it to have a low sort order number, as you want it to act before other modules. And if it wasn't clear, change things like $this->title = MODULE_HEADER_TAGS_PRODUCT_TITLE_TITLE; to look like $this->title = MODULE_HEADER_TAGS_HEADING_TITLE_TITLE; throughout the file.
  14. 2 points
    Well, it's language specific, so I'd check the part of the language files that specifies that <htmldir="ltr" lang="de"> My guess is that you're missing a space in define('HTML_PARAMS', ' dir="ltr" lang="de"'); in the german.php file. Note that there should be a space before the dir entry. Your browser doesn't know what an htmldir tag is, so it assumes that it's part of the body. So your browser implicitly creates the html, head, and body tags. Then it removes the ones that template_top.php created.
  15. 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
  16. 1 point
    We have a big problem with spam and fake accounts on Phoenix sites, so what can we do? Well found some time to hook Google reCAPTCHA V2 for Phoenix 1.0.3.0 so everyone can make use of it. I have installed and tested on Phoenix 1.0.3.0 but as this is critical to comunincation with your customers I'm not going to post in the app's untill it's been tested by a few others. So here we go. JcM Google reCAPTCHA V2 Phoenix V1.0 A simple add-on to let add the Google reCAPTCHA V2 to any form in Phoenix 1.0.3.0 that has the hooks added to it. It is a no core change add-on and uses site-wide hooks. Simply copy all the files over. You will need your Google reCAPTCHA so you can add them to the following file includes/languages/english/google_recaptcha.php Just open it in your editor and add the comment and keys into it //google define('MODULE_CONTENT_RECAPTCHA_ERROR','Sorry you need to prove you are human first please complete the google captcha'); define('MODULE_CONTENT_RECAPTCHA_SITEKEY','Place your site key here'); define('MODULE_CONTENT_RECAPTCHA_SECRETKEY','Place your Secret key here'); That’s it it should just work. When you go to your contact_us page you should see the Google reCAPTCHA Enjoy. Can be see working on this site Thank's to @Gyakutsuki for helping to debug this. JcM Google reCAPTCHA V2 Phoenix V1.0.zip
  17. 1 point
    ecartz

    Error installing Phoenix 1.0.4.0

    I made the edits at https://github.com/ecartz/CE-Phoenix/blob/warn_php_version/install/templates/pages/index.php if you want to try to convince Gary to integrate them.
  18. 1 point
    raiwa

    Product listing

    It's just the sense to specify width and height, so all images independent of their proportion will occupy the same space. KissIt image thumbnailer adds therefore background to create equal thumbs and avoids like this stretching. It works best using square proportion, so mixing landscape and portrait images will still result in equal sized product cards and a nice aligned product listing. I believe @ecartz wanted to explain more or less the same.
  19. 1 point
    ecartz

    Product listing

    It makes the layout harder to calculate. Because if the width is set, then the height can change. Or if the height is set, the width can change. Consider specifically the situation where the canonical value is set to 300, considering a 300x300 image. On some products, the image might be 300x60 and on others 300x2100. Will it look good to mix products where some are 35 times as tall as others? Or 50x300 and 2000x300. Some products are most of the width of a screen while others take up just a fraction. If you specify width and height, you can make all the images fit into that box and automatically extend the ones that need it. So a 300x60 image will get 240 rows of padding. While the 300x2100 will be resized to something like 43x300 and receive 257 columns of padding. This gives each product a predictable size in the display.
  20. 1 point
    highly recommended
  21. 1 point
    Have updated the invoice file to fix small error on total layout and link to terms. invoice.php
  22. 1 point
    JcMagpie

    Column Width Issue

    All depends on how you are achiving the out put but this should help, "block" https://getbootstrap.com/docs/4.0/utilities/display/
  23. 1 point
    Dan Cole

    Generated link Concept

    Brilliant idea and coupled with your original suggestion of changing the access point of pages like create_account I think it would go along way to solving the bot issue. 👍 Dan
  24. 1 point
    Today I finished with the migration of my old Website to the Phoenix plattform. This is the result, see: https://www.attias.ch/ I am happy now, it was a lot of work. Thank you all for the help
  25. 1 point
    Uploaded Versión 1.0.2.3 for OSCOM CE Phoenix 1.0.2.3 Español para OsC CE https://github.com/raiwa/OSCOM-CE-Phoenix-Spanish-language-idioma-espanol
×