Jump to content

Leaderboard


Popular Content

Showing content with the highest reputation since 10/20/2019 in Posts

  1. 4 points
    burt

    CE-Phoenix v1.0.3.0

    This release introduces a number of key improvements: the foundations of a bootstrapped admin (more to follow...) revamped categories/products page in admin with product tabs and pre-placed hooks much improved checkout pages layout with pre-placed hooks modernisation of Reviews system new Password Forgotten module flags for inactive modules in admin removal of deprecated code, redundant pages, functions and features bug fixes and other minor code improvements LEANER. SIMPLER. FASTER. Download: https://github.com/gburton/CE-Phoenix/archive/master.zip
  2. 4 points
    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
  3. 4 points
    raiwa

    List of my Phoenix compatible Addons

    Reuploaded all Phoenix compatible Addons flagged for Phoenix
  4. 3 points
    raiwa

    AJAX Attribute Manager support

    I had a look and the attributes manager can be hooked in the new categories.php => no more file editing. Coming soon.
  5. 3 points
    burt

    Phoenix Announcements

    Phoenix 1.0.2.8 Demo Site: https://template.me.uk/phoenix/index.php Thank you to all who found and reported bugs. This Update; fixes installation bug in "upcoming products" updates reviews box to fix display bug updates bug in "admin/orders.php" removes cache system removes defunct pieces from installation SQL Update version to 1.0.2.8 How to Update if on 1.0.2.7; Download this Zip: 1.0.2.8.zip Unzip it Upload it Run This SQL: https://pastebin.com/XMf0zqHg After which; Uninstall AND Reinstall Reviews Box Module (aka bm_reviews) Delete un-needed files; - admin/cache.php - admin/includes/languages/english/cache.php - includes/functions/cache.php How to Update if on earlier version; Find version you are on [admin > tools > version checker] Go back through this discussion and perform updates to get to 1.0.2.7 Then follow "how to update if on 1.0.2.7 & after which" instructions - OR - You can download and install a brand new 1.0.2.8; clicking the green "clone or download" button at https://github.com/gburton/CE-Phoenix 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.2.8 Make code changes one by one - THEN - After Installation (whether NEW or UPDATE) is complete; Visit admin > tools > security checks and perform any needed actions Enjoy using 1.0.2.8 - 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.
  6. 3 points
    I provide a fairly regular, small updates; With actual step by step instructions on exactly what to do to perform the update; upload X uninstall Y delete Z I also provide a zip file of just the changes. I also link to diff (comparison) files. I also provide direct SQL as and when needed. With a large update, say once a year...you'd get none of that. This way...you have a choice; You can perform the small updates as they come out, or you can ignore them and just do a large update when that comes out. It makes no sense, to me, that anyone would be upset by having more choice.
  7. 2 points
    JcM Header Banner Carousel V1.2 Phoenix As the latest version of Phoenix has removed the stock banner manager from core the original version of this will not work. This is a new version that works without the stock banner code. It has most of the main functionality as before. This is a header add-on that lets you place a carousel banner at the top of your site. It will show up to 8 banners. It has been updated to allow start and finish dates to be set for the banners. This can only be done for the last 7 as the first must always be active for carousel to run. Banner will only show when start date is reached and will turn off on end date. The date must be entered in correct format. Simply copy over all files install and turn on like any other add-on. The overlay text for each banner and images can be set in the language file. You can also select which pages it is to be shown on. The default install will show Halloween banners 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 banner display dates are set in admin
  8. 2 points
    Before anyone starts I am fully aware of the PI modules available to some supporters, but some may not be supporters and may want a different layout to their product_info.php pages. For ease the PI modules should be obtained by becoming a supporter of Phoenix by paying either monthly or annually. I spent a while trying to change the look of my product pages in Phoenix but could not get the effect that I had in Edge. This is down to a change in BS4 compared to the older BS3. In BS3 it was easy to place modules next to each other in the product info pages just by using the sort order and content widths, but that functionality was removed with BS4. What this mod does is to replace the content block of code found in product_info.php from one to four blocks. One full width across the top, two in the centre side by side and one full width across the bottom of the page. Different widths of the centre two blocks can be altered in the product_info.php page code. It does change the code in the core product_info.php page and there is a need to create some new folders in the product info modules and languages folders. Once done any new module created for the standard product info page can be used with no changes. To fill the full width of the two centre blocks you should use a content width of 12. New blocks can easily be added to create greater page variation by adding similar blocks to those now found in the product_info.php file, and creating the new folders needed. Existing new blocks can also be moved around the page by changing product_info.php. Totally stand alone with one core code change to product_info.php. Has been tested on Phoenix 1.0.2.5 only but may work on other versions. Will not work on pre Phoenix code. Some of the modules in the images may not be available to non supporters. Available at https://apps.oscommerce.com/wilqp&better-product-info-page-layout-phoenix
  9. 2 points
    piernas

    Ultimate Seo Urls 5 Pro

    Fine I meant I fixed after uploading the file. Will update later.
  10. 2 points
    Stephan Gebbers

    CE-Phoenix v1.0.3.0

    Ok, got it working. thanks.. and i have installed the admin editor hook now too
  11. 2 points
    I believe that it's if (!file_exists(DIR_FS_CATALOG . 'includes/modules/payment/'. $payment . '.php')) and require_once(DIR_FS_CATALOG . 'includes/modules/payment/'. $payment . '.php'); Here's the commit. It says that the following were removed define('DIR_WS_IMAGES', 'images/'); define('DIR_WS_ICONS', DIR_WS_IMAGES . 'icons/'); define('DIR_WS_INCLUDES', 'includes/'); define('DIR_WS_FUNCTIONS', DIR_WS_INCLUDES . 'functions/'); define('DIR_WS_CLASSES', DIR_WS_INCLUDES . 'classes/'); define('DIR_WS_MODULES', DIR_WS_INCLUDES . 'modules/'); define('DIR_WS_LANGUAGES', DIR_WS_INCLUDES . 'languages/'); define('DIR_WS_DOWNLOAD_PUBLIC', 'pub/'); So anything with DIR_WS_MODULES should be replaced with 'includes/modules/' and then you can concatenate neighboring strings. DIR_FS_CATALOG and $payment should stay the same. If you continue to have trouble, try replacing $payment with $GLOBALS['payment'] and output both (either to log or screen; preferably log if a live site).
  12. 2 points
    OK, in the demo site...I think one line of code to add into the checkout_confirmation page and you have the same there. No big deal, no need for so much core code change. As below;
  13. 2 points
    According to the European law, the general conditions of sale applicable are those which are in force at the time of the sale. If the general conditions of sale have been modified after registration (I have clients registered for 13 years and my Terms have been modified to adapt to European laws 2 times since), how can he be aware if he don't have knowledge of it at the time of purchase? I know that the majority of customers do not read them, but officially they have to do it.
  14. 2 points
    burt

    Phoenix Announcements

    Phoenix 1.0.2.7 Demo Site: https://template.me.uk/phoenix/index.php This Update; makes payment icons a bit more flexible adds flag to (in)active modules TY @bonbec fred for the cool idea Update version to 1.0.2.7 How to Update if on 1.0.2.6; Download this Zip: 1.0.2.7.zip Unzip it Upload it After which; Uninstall AND Reinstall Payment Icons Module (aka cm_footer_extra_icons)and configure it appropriately How to Update if on earlier version; Find version you are on [admin > tools > version checker] Go back through this discussion and perform updates to get to 1.0.2.6 Then follow "how to update if on 1.0.2.6 & after which" instructions - OR - You can download and install a brand new 1.0.2.7; clicking the green "clone or download" button at https://github.com/gburton/CE-Phoenix 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.2.7 Make code changes one by one - THEN - After Installation (whether NEW or UPDATE) is complete; Visit admin > tools > security checks and perform any needed actions Enjoy using 1.0.2.7 - 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.
  15. 2 points
    @vanzantz those two exploit reports are from the same bloke and they are not verified. I think they are wrong, he doesn't understand what a boolean-based sql injection attack is or for that matter how to test for a sql injection vulnerability of any kind. FWIW I am confident your tool is reporting a false positive and the code is perfectly safe. I can find no report anywhere that integer casting is not proof against injection. You always end up with an integer, so you can never get anything but found or not found for a match to the review_id and you can't add anything to the sql statement. Of course it's possible he's just a better hacker than I am a coder 😉
  16. 2 points
    I believe it is intentional to ensure customers spear ahead to checkout and not to be distracted by other things. 😀
  17. 2 points
    raiwa

    Ultimate Seo Urls 5 Pro

    @peterpil19, I tested my updated version from the 2018 EDGE shop on Phoenix 1.0.2.5. It works error free (error reporting set to ALL) The last uploaded package R2.09 (october 2018): throws errors. I believe my version is based on Release 2.08 Some update for the href lang tags of the latest version have been added, all seems to work correct. But I didn't do a very exhausted testing. Here the package including the modified files for Phoenix 1.0.2.5: Ultimate_SEO_URLs_5_Phoenix_beta.zip Here the link to the GitHub repository of the complete shop: https://github.com/raiwa/Responsive-osCommerce/tree/Ultimate-Seo-URLs-5 The instructions are not updated, just upload the "drop on top" and "compare_files" modified files. If you have a test shop and would like to give it a try and others too. The href lang tags need a multilanguage store with at least 2 languages. I'll try to contact the author to see if he would like to upload this as an update. I really have no time to give support for this.
  18. 2 points
    If you join the club and look through that thread someone might have commented about using it on EDGE...I'm just not sure. You could always ask there as well. Phoenix is just an improved version of EDGE so my guess is that it would work or could be made to do so fairly easily. Dan
  19. 2 points
    Most users I think do not wish to become a slave to a constant upgrade merry go round. As before most will just pick a point in time and install it, make the mods they need to make a usable working live shop and stick with it. It's wonderfull news that supporters are getting aditional code and early access to new versons. I'm sure they are very happy with this. However I don't see the point of you constantly posting this out side the closed club! It's of no use to anyone who is not part of the closed club. If they are part of the club then they will already know about it. osC forum has never been a place for hard selling! I'm sure people can make desisions without it beeing constantly pushed into their faces. This second hand cars sales (chugging) approach is not a nice look for osC 😊 but if that's the route chosen then so be it.
  20. 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
  21. 1 point
    Fiber

    TinyMCE

    Yes thanks for that, it works fine in the testshop...handy 🙂
  22. 1 point
    Dear nrlatsha, Please get in touch with us at MaxMind (info at maxmind.com) if you would be interested in collaborating on updating your plugin for more advanced minFraud features. We'd be happy to work with you. Jason
  23. 1 point
    Yes sorry my mistake. It's a security issue as it's running in admin. I have an image in my files which links to my website, remove that in your files and make sure the image you use is in your admin/images and it should work fine. Sorry just an oversite by me. it's around line 50 ish, just a cross origin security issue. <div class="col"> <a target="_blank" href="https://jcmagpie.com"> <img src="images/jcmagpie-2.png" data-holder-rendered="true" />
  24. 1 point
    Exactly! I think he said he installed 2.3.4 but it's a moot point. Both are out of date and if end users don't push back and alert their ISP's nothing is likely to change. Dan
  25. 1 point
    Phoenix users - please get Better Together for Phoenix here: https://apps.oscommerce.com/Apps&amp;XpyA1&amp;better-together-for-phoenix
×