Jump to content

Leaderboard


Popular Content

Showing content with the highest reputation since 10/18/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. 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.
  3. 3 points
    Reuploaded all Phoenix compatible Addons flagged for Phoenix
  4. 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.
  5. 3 points
    @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
  6. 3 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.
  7. 3 points
    @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
  8. 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
  9. 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
  10. 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;
  11. 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.
  12. 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.
  13. 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 😉
  14. 2 points
    I believe it is intentional to ensure customers spear ahead to checkout and not to be distracted by other things. 😀
  15. 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.
  16. 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
  17. 2 points
    Phoenix users - please get Better Together for Phoenix here: https://apps.oscommerce.com/Apps&XpyA1&better-together-for-phoenix
  18. 2 points
    ecartz

    Framework searched for Homepage

    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.
  19. 1 point
    Dan Cole

    Documentation Initiative

    Yes...it's deafening in here. Dan
  20. 1 point
    For anyone else who feels the need to check for ad-blockers this is a simple implamentation of this detection script for Phoenix. https://github.com/InteractiveAdvertisingBureau/AdBlockDetection It's implamented using 2 sitewide hooks so no core changes. It will give you something to play with and refine for your site. It detects if ad-blocker is active in the customers browser and displays a message in a modal window which the customer can dismiss. It's not in the apps market and I do not plan to support it beyond what is posted here. You are free to edit the hooks code as you like. AdBlock Check Phoenix V1.0.zip
  21. 1 point
    I think limiting the length of names is not going to do much in stopping people from creating fake accounts. These people will still hack the system with short names. Best is install captchas.
  22. 1 point
    Demitry

    admin orders onclick change

    @Kevin.Dallas One more thing about the usability of creating a feature like this. I assume that you need to make changes once in a while to a tracking number due to an initial data-entry error. With your solution,.. changing it in the Order History Update section/log will not send an email to the customer to notify them of the correction. And, it will not date/time stamp that correction for your own records, so that you can go back and see when you made this change. Of course, you could hire a developer to have these features added as well, but why? All you have to do is post another Order Update with the correct tracking number and add a note saying that this is the correct tracking number so, please discard the one sent in the last update. This will record in your Order History Update section/log and it will send an email to the customer notifying them of the change. Better record keeping, no need to get into the database, and no need to pay a developer. Problem solved!
  23. 1 point
    ecartz

    Framework searched for Homepage

    With mod_rewrite (Apache), you don't even have to redirect. It is quite capable of serving the content of angebot.php when angebot.html is requested. I'm not sure that's necessary. Google is quite capable of crawling .php pages with static content. For example, searching for "Put here your Conditions of Use information." returns results from multiple osCommerce sites, even though that is certainly useless content. Documentation: https://httpd.apache.org/docs/trunk/rewrite/remapping.html High ranked internet tutorial: https://aloneonahill.com/blog/url-rewriting-for-beginners Example: RewriteEngine On RewriteRule ^angebot.html$ angebot.php [L] When angebot.html is requested, that will serve the content from angebot.php . Or with redirect: RewriteEngine On RewriteRule ^angebot.html$ angebot.php [R=308] Change the redirect code as appropriate (e.g. 301, 307, etc.). The default is a 302, but that seems unlikely to be what you want here (302 means that people should continue to request the redirected URL, as the target is only temporary; presumably you'd be doing this permanently). Nginx may have similar capabilities, but I don't know how they work.
  24. 1 point
    @Dan Cole I think the Product Information System that you’re referring to is part of the Phoenix release. I’m not familiar with it and this is the first I’m hearing of it. Though out of curiosity I’d love to know more about it.
  25. 1 point
    burt

    Phoenix Announcements

    Phoenix 1.0.2.5 Particular thanks to @BrockleyJohn for fixing the Hooks class. Demo Site: https://template.me.uk/phoenix/index.php This Update; Fixes bug in Hooks Class that presents itself on some, not all, servers Update version to 1.0.2.5 How to Update if on 1.0.2.4; Download this Zip: 1.0.2.5.zip Unzip it Upload it Visit admin > tools > security checks and perform any needed actions Enjoy using 1.0.2.5 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.4 Then follow "how to update if on 1.0.2.4" instructions - OR - You can download and install a brand new 1.0.2.5; 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 using 1.0.2.5 - Join the Phoenix Club - https://forums.oscommerce.com/clubs/1-phoenix/ If you are not a member of the Phoenix Club, request it; you'll get to see some of the "behind the scenes" work and help to steer future releases.
×