Leaderboard

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.

Reuploaded all Phoenix compatible Addons flagged for Phoenix

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.

@Demitry You'll find additional information about it in the Phoenix club...sign up there if you haven't already and you'll find a thread describing what it does and an explanation of how it works. Basically Gary has split the product information pages up into modules that you can control the placement of from the admin side....in addition to the normal sort order you can select whether something is placed at the top, left, right, perhaps center and bottom of the page. You can also control the width the item occupies. It in effect gives you total control over the placement of items on the product information page. It's a must have and should give you a good idea of how to achieve what you want. You'll need to become a supporter to get the actual code but you can at least have a look to see if it is the sort of thing you're trying to achieve. Supporting Phoenix is something everyone using osC, in it's various forms, should do. If it's not in a shop owners budget it needs to be. Dan

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.

@puggybelle Hi Andrea, Phoenix is a fully-functional product based on a code base that has evolved over many many years. I am using it (as others are) for my live shop. Point releases are optional and you can wait for more significant releases instead (i.e. 1.3.0) but I would always recommend keeping your shop software up to date. It us up to you when you update. I reckon I am forced to install updates to Windows / MacOS /iOS and other software on my mac, work pc and iphone almost every week. If you sometimes hit the equivalent of the ‘Snooze’ button you can install later but at your own risk of missing out on improved features and addressing security risks. Properly maintained software gets maintained, and we are fortunate to count on @burt to not just do that, whilst improving the code base. The number of point releases should be seen as being directly proportionate to the level of support Phoenix is getting (at no charge to shopowners). This should give your greater comfort, not cause for concern. I wouldn’t want to invest in a shop whose software gets touched only once a year or less frequently

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

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;

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.

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.

@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 😉

I believe it is intentional to ensure customers spear ahead to checkout and not to be distracted by other things. 😀

@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.

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

Phoenix users - please get Better Together for Phoenix here: https://apps.oscommerce.com/Apps&XpyA1&better-together-for-phoenix

So you want to go to https://www.attias.ch/angebot.html and have it look like https://www.attias.ch/ishop/conditions.php (with different text of course)? If you're OK with changing the name to angebot.php, you could just make copies of the conditions page files. angebot.php from conditions.php includes/languages/german/angebot.php from includes/languages/german/conditions.php In the new file, change require('includes/languages/' . $language . '/conditions.php'); $breadcrumb->add(NAVBAR_TITLE, tep_href_link('conditions.php')); to require('includes/languages/' . $language . '/angebot.php'); $breadcrumb->add(NAVBAR_TITLE, tep_href_link('angebot.php')); and in the language file, change define('NAVBAR_TITLE', 'Conditions of Use'); define('HEADING_TITLE', 'Conditions of Use'); define('TEXT_INFORMATION', 'Put here your Conditions of Use information.'); to reflect what you want to show, e.g. define('NAVBAR_TITLE', 'Unser Angebot'); define('HEADING_TITLE', 'Unser Angebot'); define('TEXT_INFORMATION', <<<'EOTEXT' <h2>Briefmarken</h2> <p>Schweiz ab 1850 Einzelmarken/Sätze ab 40 % SBK</p> <p>Rayon, Strubel, Sitzende Helvetia, Stehende Helvetia, Ziffermarken, Tellknaben und Brustbild, Freimarken, Werbemarken, Pro Juventute, Pro Patria, Blocks, Zuschlagsausgaben, Automaten-Marken, Rollenmarken, Porto Marken, Zusammenhängende, Zwischenstege, Kehrdrucke, Dienstmarken, Stempel Neuheiten, Schweizer Neuheiten, Schweizer Spezialitäten, Jahreszusammenstellungen, Abarten, Postfrisch , Gestempelt, FDC's, Vollstempel, Ersttag Vollstempel, Frankaturware etc... Diverse Länder</p> <p>UNO Genf, Deutschland (in Bearbeitung).<br /> Posten und Sammlungen</p> <p>Kleine Posten und Sammlungen ab 10.-, Kiloware Schweiz und Ausland (Briefmarken zum Ablösen), Länder- und Motivsammlungen je nach Angebot.</p> <p>Wühlkiste - jeder Brief 1.- Stutz - hier findet jeder einen kleinen Schatz. Ansichtskarten</p> <p>Weit über 15'000 Schweizer Ansichtskarten am Lager (Litho, Lichtdrucke, Foto-AK's). Zubehör</p> <p>Briefmarken-Kataloge (SBK, Zumstein, Michel), Sammler-Zubehör von Leuchtturm (einiges am Lager), Lindner auf Bestellung. Hüllen für Ansichtskarten und Briefe, Archivierung etc., Briefmarken Alben, Systemalben für Briefmarken, Briefe, FDC, Ansichtskarten, Vordruckalben, Pinzetten, Lupen etc.<br /> Fehllisten Bearbeitung</p> <p>Wir bearbeiten gerne Ihre Fehllisten für Briefmarken, falls die gewünschten Marken nicht am Lager vorrätig sind, suchen wir Sie gerne kostenlos in Ihrem Auftrag und offerieren Ihnen diese. Hier können Sie uns mitteilen, was Sie suchen, bzw. was Ihnen fehlt.</p> <p>Briefmarken-Neuheiten können bei uns im Abonnement bezogen werden!</p> EOTEXT ); I prefer the nowdoc syntax for multiple line strings. There are also contributions like Page Editor , but it doesn't look like that's been updated for Phoenix. If you have budget, you could pay someone to do that. Either post in the Commercial Support Inquiries forum or PM @burt to see if he has something like that for Phoenix Supporters (annual fee required). If it's important that the name end in .html, then you could configure Apache's mod_rewrite to do that.

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

No I have no plans to do anything further with this. I have no idea what Phoenix's plans are, if it goes then you will either have to stick with current version or find another solution. I have frozen my add-ons at 1.0.1.2 and have no plans to do any further updates. Just too many changes to keep up with. Sorry. Just because phoenix is removing it does not mean you have to, you could just keep using it. The changes you make are up to you. Also I'm sure there will probably be a replacment add-on of some sort.

I do not agree with using this but if you wish to use it on your website that's up to you. Anti Adblock Script https://antiblock.org/

😊 Simply not true and you should know this. For it to be out of date would require a more upto date official version to be available! none is, 2.3.4.1 is still the official and latest version of the software and is the version available to down load from the official osC page. I would imagine that when HPDL releases V3.0 that will become the next official version available from ISP's. Any change of what is offerd by ISP's will need to be driven by HDLP not we poor users. Try asking your host and see how far you get 😂 would love to know what they say.

Lee, I believe that you’re referring to the same Product Information System that Dan mentioned. I’m currently in the dark when it comes to that particular topic. However, I completely support any and all initiatives that would make this software easier to customize …and especially, for the non-technical user.

While Microsoft Windows only releases a new name once every couple years (rarely as much as four), it releases service packs (now called builds) more often (I counted twenty-four releases since 1995, ignoring NT, 2000, and XP Professional x64). Plus it releases bugfixes every month and occasionally between. In the last six years, @burt has released two named versions: Frozen and Phoenix (Windows had 8.1 and 10 in the same period). Four service pack level versions (Frozen, Phoenix 1.0, 1.1, and 1.2). Less than twenty point versions (compare to seventy or so from Microsoft Windows). I suppose the next level would be to count commits as the equivalent of the individual packages that get installed in the monthly rollup for Microsoft Windows. I don't know the magnitude of that. Apple iOS has eight named releases in the last six years. And twenty-five minor releases. I don't know how many point releases, but it's had more minor releases than Phoenix has had point releases. It's had four point releases in the last month. If fewest version updates is your criterion for evaluating stability, community edition (Frozen/Phoenix) is more stable than Windows or iOS. Of course, one of the problems is that with Windows/iOS, most updates happen in the background whereas Phoenix is still updated manually. So with Phoenix one is more aware of the updates than with the operating systems.

@kgtee Thank you very much, works fine! I assume you had this done before I asked for it?

A regular expression is supposed to be "starting delimiter", the regular expression, "ending delimiter", modifiers (if any). If the "ending delimiter" appears in the regular expression, it ends it early. So something like '//d/' is invalid, as it thinks that it is trying to match an empty regular expression under a d modifier. To fix that example, you could change it to '/\/d/' Which would match a forward slash followed by the letter d. But since the regular expression is generated dynamically from the currency symbol in this case, we can't just fix it. The preg_quote function goes through and escapes any regular expression syntax in the string. In particular, we told it the delimiter was a / and to escape any occurrences of that in the currency symbol. Or to put this another way, it would turn the first string into the second string.

Hi David, As an alternative suggestion, why don't you add these as pages to your shop instead to create a more seamless experience for your customer? Everything I can see in the link provided can be added to your Phoenix shop. I'm assuming it would be beneficial to keep your customers in your shop environment. it is easy to add new pages to the shop, just: 1. Copy a simple page(e.g. conditions.php) and its corresponding language file. 2. Rename the page to what you want to call it. 3. Change all references in the files from the name of the old file (e.g. conditions), to the new one. 4. Add content. You probably only need to modify the language file to do this. Peter