Jump to content

Leaderboard


Popular Content

Showing content with the highest reputation since 08/23/2019 in Posts

  1. 6 points
    peterpil19

    Ancient Coin Traders - Phoenix

    Dear All, My website has been upgraded to Phoenix (latest version). www.ancientcointraders.com It was previously Edge BS3 (pre-frozen). Main improvements are: 1. much faster 2. new features in Phoenix (sitewide hooks, modular shopping cart, product_info pages, improved modules etc.) make life easier. 3. Bootstrap 4 has much neater ways of doing things than Bootstrap 3. Shorthand classes in particular make things cleaner and simpler. Bootstrap 4 is also mobile first. A special thank you to @burt for accepting my request to assist me with what was a very quick 'migration' to Phoenix. This involved starting off fresh with Phoenix, making change and cleaning up all my blundered custom 'coding' from my BS3 installation. Thank you also to @burt for keeping the project alive. I have done a lot of comparisons recently against other open-source and commercialised shopping cart software. I also habitually look closely at any website I am on as I am sure many others here do. Phoenix holds its own against most others. You can get a nice-looking website up and running fairly quickly from scratch. Happy as always for any feedback or areas of improvement. Regards, Peter Note: I could not edit my original post on this board for some reason, so happy of course for them to me merged if a moderator obliges.
  2. 5 points
    puddlec

    TinyMCE

    this is what i managed to achieve. With my first attempt at using the hook system i'll possibly tidy it up a bit on Sunday. and upload it as an addon basically it just works just like the hooks on the shop side. works on all category description, and product descriptions textareas, regardless of how many languages you use. in regards to the themes / plugins / toolbar you can just add / remove them as you see fit (the settings you see in the file are the ones i use myself) it does with work the tinymce CDN (if you got an API KEY), loading locally, or via another CDN (using an CDNJS just to show it works), you can use whatever source you want. the same basic idea can also be used for ck editor, or any other javascript library you think you may need within the admin. tinymce hook.zip
  3. 4 points
    JcM CKEditor V1.0 A simple add-on to let you place a WYSIWYG HTML editor onto your site’s admin. CKEditor 4 Proven, enterprise-grade WYSIWYG HTML editor with wide browser compatibility, including legacy browsers. Paste from Word and Excel, spell check, accessibility checker, tables. Autocomplete, @mentions, widgets, code snippets, emoji 😊 plugins. Full control over content: HTML filtering, view source mode. Great accessibility: WCAG 2.0 AA and Section 508 compliant. Long-term support (LTS) until 2023. For Phoenix simply copy new files into the required places and your done. You can if you like do it the old fashion way as in the frozen method below. For frozen it’s a simple edit of one template file, open :- public_html/admin/includes/template_bottom.php and just before the </body> add this code, <script src="https://cdn.ckeditor.com/4.12.1/standard/ckeditor.js"></script> <script> CKEDITOR.replace( "products_description[1]" ); CKEDITOR.replace( "manufacturers_description[1]" ); CKEDITOR.replace( "categories_description[1]" ); </script> That’s it your done. If you go to admin and edit a product you will see the WYSIWYG HTML editor on the product description box. This is just a simple application of the editor you can expand it as much as you like. It has been tested on Phoenix 1.0.2.0 only. It should however work on other versions and frozen Enjoy.
  4. 4 points
    puddlec

    TinyMCE

    @René H4 this is my current amount of progress. tinymce hook v2.zip
  5. 4 points
    burt

    Product Page Layout

    Product Page Layout is in finalised testing; https://template.me.uk/phoenix/product_info.php?products_id=3 This all-new system allows millions (that is not an exaggeration) of layout possibilities, all easily set up by shopowner.
  6. 3 points
    puddlec

    TinyMCE editor for admin

    This addon adds support for the TinyMCE editor within the admin section. what does this addon do? it will add the editor to the following textarea's category description, manufacturers description, product description works with multi languages stores. requirements Phoenix How to install Upload the files yes it is easy as that. no files need to be edited it uses the hook system, to add the code needed. How to change what appears on the toolbars, and plugins used Just go to the tinymce.php hook file located at catalog\includes\hooks\admin\siteWide\ you will see a block of code for plugins (line 61) and for toolbar 1 & 2 (line 67 & 68) the settings provided are what i use myself. Got an TinyMCE API key? just change the script source (line 53) How to add extra textarea's example add TinyMCE to the order comments box add orders.php to (line 44) like so var $good_pages = ['categories.php', 'manufacturers.php', 'orders.php']; then add the name of the textarea (comments) to the selector (line 52) selector: 'textarea[name^="products_description"], textarea[name^="categories_description"], textarea[name^="manufacturers_description"], textarea[name^="comments"]', // what textarea's do we want to load TinyMCE on
  7. 3 points
    burt

    TinyMCE

    Great stuff @puddlec This addon shows one of the first uses of the Hooks, chapeau! Hooks are incredibly powerful.
  8. 3 points
    puddlec

    TinyMCE

    now available for download https://apps.oscommerce.com/1VCAj&tinymce-editor-for-admin support thread
  9. 3 points
    burt

    Phoenix Announcements

    Phoenix 1.0.2.3 Thank You to Phoenix Club members for making the hard work much easier. https://forums.oscommerce.com/clubs/1-phoenix/ Demo Site: https://template.me.uk/phoenix/index.php This Update; align items in form TY @raiwa add extra siteWide hook call TY @raiwa modernise radio modernise tickbox Disallow non-buyer ability to write review TY @Heatherbell Update FontAwesome to latest version Add New Password Forgotten Module Fix Manufacturer Info sidebox Allow Shopowner to choose layout of Sub-Category List Fix output of category description TY @Moxamint Minor updates to some boxes Update version to 1.0.2.3 SQL to run prior to update INSERT INTO configuration (configuration_title, configuration_key, configuration_value, configuration_description, configuration_group_id, sort_order, set_function, date_added) VALUES ('Allow all Reviews?', 'ALLOW_ALL_REVIEWS', 'false', 'Allow customers to leave reviews on all products (true) or only on products they have purchased (false)', '1', '22', 'tep_cfg_select_option(array(\'true\', \'false\'), ', now()); How to Update if on 1.0.2.2 Download this Zip: 1.0.2.3.zip Unzip it Upload it Go to admin > tools > security checks and correct any listed problems How to Update if on earlier version Find version you are on Go back through this discussion and perform updates to get to 1.0.2.2 Then follow "how to update if on 1.0.2.2" instructions After Update Install new "Forgot Password" content module (login) Uninstall AND then Re-Install "Sub Category List" content module (index_nested) Visit admin > tools > security checks and perform any needed actions Enjoy the hard work that went into this update - OR - You can download and install a brand new 1.0.2.3 clicking the green "clone or download" button at https://github.com/gburton/CE-Phoenix choose "download zip" unzip, upload, install After New Installation is complete Visit admin > tools > security checks and perform any needed actions Enjoy the hard work that went into 1.0.2.3
  10. 3 points
    asro2004

    Stripe v3 module for SCA

    Many thanks for the feedback. I've made changes which I think address all issues raised so far: update all SQL to use actual table name instead of string constant add javascript to 'footer_scripts' template block, so loaded after jQuery in Phoenix and remove $ undefined error javascript error add Bootstrap classes to form controls to improve appearance in Phoenix, and fix card element not being visible in Phoenix hide 'add card' prompt in payment form when token save configuration is false stop logging to event table when configuration logging setting is false set module public title to 'Credit Card (Stripe SCA)' so enabling multiple credit card modules is less confusing fix save card icon display in Phoenix 'my account' page remove configuration option to validate CVC, as card fields are managed by Stripe The updated module is attached. It has been tested on both an old Bootstrap osCommerce site and a current Phoenix, 1.02, site. If you do not see the card number, expiry and CVC in the order confirmation payment form, please check the browser console for any javascript errors. jQuery must be loaded before the payment module script in the page source. If you enter card details and the page hangs with the payment button disabled, please check the browser console for any javascript errors. If that's ok, check the latest rows in the stripe_event_log table. If there is not an entry for the action 'ajax retrieve', that suggests that the server hook https://yourstore.url/ext/modules/payment/stripe_sca/payment_intent.php is not accessible. Check the URL in your browser for any errors. It should show the response ' {"status":"fail","reason":"No intent id received"} '. If the payment is processed, and the checkout success page is displayed, but the order is not complete, first check the Stripe dashboard to see if the payment was processed. If ok, check the webhook events in the stripe Developer page. It will show the response received for each webhook attempt, and may show PHP errors in the response. You may need to copy and paste to a notepad to view the messages more easily. Also check the latest rows in the stripe_event_log table. There should be a series of rows for the actions: 'webhook', 'webhook process payment', 'webhook processOrder', 'webhook updateOrderStatus', plus messages for 'webhook createCustomer' and 'webhook saveCard' if token saving is enabled and the 'save card' check box was ticked in the payment form. Check that the server hook https://yourstore.url/ext/modules/payment/stripe_sca/webhook.php is accessible. If you enter the URL in your browser, you should get a blank page displayed with no errors. stripe_sca_v1.0.1.zip
  11. 3 points
    Denkster

    Phoenix - Dutch Language Set

    Check this: https://github.com/Denkster/OSCOM-CE-Phoenix_Dutch_language_Nederlandse_taal
  12. 3 points
    Updated PWA Purchase without account 4.0.0
  13. 2 points
    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
  14. 2 points
    JcMagpie

    Ancient Coin Traders - Phoenix

    😂 a little harsh me thinks?
  15. 2 points
    mfleeson

    Royal Mail shipping module

    Hi I have a two versions of the Royal Mail, one for UK and one for Airmail both which work with 2.3.4 BS. I'll be looking to port them to phoenix once I'm up and running development again. Let me know if you're still interested in this being available. Cheers Mark
  16. 2 points
    peterpil19

    TinyMCE

    I could not agree more! @puddlec I'm really looking forward to using this app once available. Thanks for making the time to work on it! Peter
  17. 2 points
    puddlec

    TinyMCE

    Update So I now got it to load on the manufacturer description. And it will only load on the pages where it is needed.
  18. 2 points
    @Chadduck 1) As you have identified, there is no shipping_usps.gif file in the add-on bundle. Fortunately, you already had one from a prior live store. For anyone else trying to get this to work with Phoenix, here's the file: 2) In the stock installation of Phoenix, there is no /images/icons folder. With that, there is also no DIR_WS_ICONS definition in the configuration file(s). To correctly use the shipping_usps.gif file, you need to: a) Create a /images/icons folder b) Copy the shipping_usps.gif file into this folder c) In includes/modules/shipping/usps.php , find $this->icon = DIR_WS_ICONS . 'shipping_usps.gif'; and change it to: $this->icon = 'images/icons/shipping_usps.gif'; Obviously, you could use any other folder you want to store the .gif file. Just update the path to point to the file's location. If you did not have a copy of the shipping_usps.gif file, you could try to use the font awesome icon. The link Zahid gave above is wrong. His is a link to the UPS icon, not the USPS icon. The correct link is: https://fontawesome.com/icons/usps?style=brands However, the USPS module stores everything in an array (including the location of the icon), and I could not just substitute the Font Awesome link for the location of the .gif file. HTH M
  19. 2 points
    The code in Phoenix has been updated, but the functionality is the same. The USPS module uses arrays to store the values you are having problems with. Stock osC does not handle arrays, so we need to make some changes to make that happen. The change to modules.php is a key part of that. In Phoenix, find this code: if (tep_not_null($action)) { switch ($action) { case 'save': foreach ($_POST['configuration'] as $key => $value) { and add this line immediately after that: if( is_array( $value ) ) $value = implode( ', ', $value ); That should fix the problems on the Admin side. You will need to uninstall and reinstall the module for this to work. I haven't tested this module with Phoenix, so there may be other changes needed. Regards Jim
  20. 2 points
    burt

    Product Page Layout

    Quite out of date as this was v1 of the system. But it shows the general idea.
  21. 2 points
    set error reporting to "ALL" in appplication_top.php (both, store and admin) replace filename constants with hardcoded filenames. Example: FILENAME_DEFAULT => 'index.php' replace path/directory constants with hardcoded paths. Example: DIR_WS_INCLUDES => 'includes/' update class constructor names to '__construct'. Example: class cod { var $code, $title, $description, $enabled; function cod() { update to: class cod { var $code, $title, $description, $enabled; function __construct() { Update while....each functions to foreach. Example: while (list($key, $value) = each($define_list)) { Update to: foreach($define_list as $key => $value) { That's for the beginning. Then observe displayed errors and fix them.
  22. 2 points
    Uploaded update for Phoenix: Purchase without account 4.0.0 Changes Version. 4.0.0 - Updated for Phoenix 2 versions included: Phoenix 1.0.2.0 and lower: old review write page "reviews_write_pwa.php" Phoenix 1.0.2.1 and higher: new reviews module "ext/modules/content/reviews/write_pwa.php" Older CE BS versions please use PWA for BS 3.0.5 Older 2.3.4.(1.) versions please use PWA for BS 2.5r2
  23. 2 points
    YePix

    Duplicate order mail

    I found the error . in the email class the addresses were not cleaned up
  24. 2 points
    burt

    Phoenix Announcements

    Phoenix 1.0.2.1 Join the Phoenix Club https://forums.oscommerce.com/clubs/1-phoenix/ This Update Fixes bug in one of the product listing files - TY @raiwa for heads up Deprecate custom.css - A few HTML changes in some files to accommodate this Fixes bug in data-price in a couple of places - TY @raiwa for heads up Adds RU language fileset link in Readme - TY @Fredi Update FA - To 5.10.1 Fix Sort By Bug in products_new.php - TY @Heatherbell for heads up Modernise Reviews - Deprecate reviews.php - Deprecate product_reviews_info.php - Remove links to the above pages - Prettify and Pre-install Reviews module on product_info.php - Move "write review" into /ext/ - Make stars "gold" Update Version - To 1.0.2.1 Special Thanks to Forum members for constructive feedback and bug hunting to Phoenix Club members for constructive feedback on the new Layout to @cupidare @raiwa @Fredi for maintenance of language filesets Notes for Language Maintainers @cupidare DE @raiwa ES @Fredi RU /includes/languages/english.php /includes/languages/english/modules/boxes/bm_reviews.php /includes/languages/english/modules/content/footer_suffix/cm_footer_extra_copyright.php /includes/languages/english/modules/content/product_info/cm_pi_reviews.php /includes/languages/english/modules/content/reviews/write.php How to update ZIP FILE, easy upload. Find out what version you are on now; admin > tools > version checker, then perform the necessary updates; Make sure you have applied the 1.0.0.1 hotfixes Make sure you have applied the 1.0.0.2 hotfixes Make sure you have applied the 1.0.0.3 hotfixes Make sure you have applied the 1.0.0.4 hotfixes Make sure you have applied the 1.0.1.0 hotfixes Make sure you have applied the 1.0.1.1 hotfixes Make sure you have applied the 1.0.1.2 hotfixes Make sure you have applied the 1.0.1.3 hotfixes Make sure you have applied the 1.0.1.4 hotfixes Make sure you have applied the 1.0.2.0 hotfixes All previous hotfix zips are listed in this thread. EG, if you are on 1.0.1.0, you must perform 1.0.1.1 hotfix to the latest listed hotfix, then; Apply the 1.0.2.1 changes -> 1.0.2.1.zip Read and perform the "if updating an existing phoenix" section DOWNLOAD AND INSTALL FULL VERSION You could simply download & install the latest full v1.0.2.1 https://github.com/gburton/Responsive-osCommerce/tree/1.0.2.1 COMMIT BY COMMIT (MANUAL CHANGES) 1.0.2.0 to 1.0.2.1: https://github.com/gburton/CE-Phoenix/compare/1.0.2.0...1.0.2.1 WHAT IS SIMPLEST I suggest the simplest way (assuming you are on 1.0.2.0) is to grab the 1.0.2.1 zip, unzip it, and upload the files. If Updating an Existing Phoenix Make sure that you have first updated fileset to 1.0.2.1 (by either manual commit, or uploading zip), then, doing this in order; 1. Install New Modules There are no NEW modules to install 2. Uninstall Existing Modules Completely turn off (uninstall), if you have them installed Admin > Modules > Content > Reviews Button Admin > Modules > Navbar Modules > Review Link 3. Reinstall Existing Modules Completely TURN OFF (uninstall) and THEN TURN ON (reinstall) the following module(s); Admin > Modules > Boxes > Reviews aka bm_reviews Admin > Modules > Content > product_info > Reviews aka cm_pi_also_purchased 4. Delete Obsolete Files includes/languages/english/modules/content/product_info/cm_pi_review_button.php includes/languages/english/modules/navbar_modules/nb_reviews.php includes/languages/english/product_reviews.php includes/languages/english/product_reviews_write.php includes/languages/english/reviews.php includes/modules/content/product_info/cm_pi_review_button.php includes/modules/content/product_info/templates/tpl_cm_pi_review_button.php includes/modules/navbar_modules/nb_reviews.php includes/modules/navbar_modules/templates/tpl_nb_reviews.php product_reviews.php product_reviews_write.php reviews.php custom.css 5. Run SQL There is no SQL that needs to be changed. Enjoy!
  25. 1 point
    mhsuffolk

    Store Mode BS

    Thanks @raiwa for your great contributions. On a finer point: In includes/languages/english/modules/content/header/cm_header_store_mode.php line 24 you have "Sorry, you have tried to access a temporary closed area" In my opinion temporarily is the correct word. English heh, what a language! define('MODULE_CONTENT_HEADER_STORE_MODE_CUSTOM_MESSAGE_SHORT', 'Sorry, you have tried to access a temporarily closed area.');
×