Leaderboard

http://template.me.uk/frozen2bs4/index.php I still have some work to do (especially on the modules for index & index_nested & index_products). Always moving forward, even if in "hiding".

i keep doing my best for you! Issues,bugs, suggestions: https://github.com/osc2nuke/oscommerce-2.3.4.1-CE Keep following/monitor the active branch. 14 files away from a bootstrapped admin. Greetings Henry a.k.a wHiTeHaT !

Massive changes in bootstrap structure between v3 and v4. If shopowner is using an unabused recentish Edge or Frozen... drop on the new files. When...soon. Where...undecided. To whom...people who I feel are supportive. Next two projects are lined up which will radically change osCommerce for the better.

https://github.com/gburton/Responsive-osCommerce/releases/tag/2341-Frozen There will be no further Code Changes. Issues will be immediately closed. What is broken, stays broken. PRs will be immediately closed. What is now there, is there. Thank You to all Shopowners and Developers who have supported the Project in the last 4 and a bit years. Personal Thanks go out to all those Shopowners who were able to support my 28d bits and pieces for 3 of those 4 years - it is you guys who have made it possible for the hundreds of other Shopowners to continue using osCommerce. A big Thank You and from me, I will not leave you guys high and dry - you have my support always, we are a Band Of Brothers. Onwards!

I don't expect this will be a publicly available thing; its a showcase of what the Responsive could (and should) have been had we got as far as Final. It will be available to some shopowners if they want it, but that will only be the handful of shopowners who are the diehard supporters of my efforts. Put simply; this is made to flatten my bsv4 learning curve.

Visually, I think everything looks better. Functionally, the code is cleaner & faster.

All New Cart Page

That has not much to do with this forum, wouldn't you agree? We cannot take any sort of influence on Google's search results. I think you have been provided with help here and in the other thread (advanced specials). Unless for you getting help means having everything served on a silver platter for free. True. Not so many shop owners left anymore since osC doesn't evolve as fast as other cart systems these days. Still those who are left are not code-junkies. They are store owners that try to help osC move somewhat forward in any way they can in their free time. The first guy, his name is John btw, has provided you with a link to the answer you seek. You just need to know which link to click. Just try and click on the bold text BrockleyJohn replied to a topic The other guy, also named John, mentioned Burt by name because we all know who Burt is or at least those that use his Community Edition which would include you too. He is a osC Team member so just click on the "Staff" tab at the top and you should see a "monkey with a hat" avatar guy, that's him. Just a friendly advice. I know things can get frustrating if you try to get something working as quick as possible but bear in mind there are people here from all around the globe so there is a time difference to consider and consider that those people are trying to help here for free most of the time. So keep your attitude in check please and don't try to vent it out here in the forum.

As a store owner, I don't want to have to visit Github (or wherever) to see if there are any patches I need to apply to my live store(s). For me, I was very happy when Edge/Final/Frozen was 'finished'. That's not to say that there aren't any bugs still in it. That's the reason for this thread ... a place to document bugs, and hopefully fixes. I am also pleased that development is still happening. Keep it up, guys. Use this thread as a source of information to improve your forks. But please, for this thread, let's keep it just for Edge/Final/Frozen, ok?

Here we go, continued project: https://github.com/osc2nuke/oscommerce-2.3.4.1-CE issues: https://github.com/osc2nuke/oscommerce-2.3.4.1-CE/issues

Ive said it before and I shall say it again Thanks Gary @burt for what you have done. Its a shame that others were not prepared to help you a bit more whether it be coder, developer or shop owner. Its a shame that it has come to this, but it had to happen one day. It could have been 4-5 years ago, but you saved the project as best you could. There seems to be some support from a few coders in this thread so may be its their turn to commit and move the project forward. Lets see what happens. I expect nothing.

It will happen only if Harald (who owns osC and this site) wishes for it to happen. He has given no indication that he does. Last August he promised a 2.3.5 upgrade release of some sort, and 2.3.6 (the CE version), within a few weeks, and it's been 8 months now. No one has heard from him in over 3 months, and we're starting to wonder if he's still above the grass. Anyone holding their breath, waiting for something to happen, is very blue by now. Most people have given up and are moving on to other projects. It's unfortunate, and even tragic (given the amount of work that he and others have put in), but he just does not know how to run a major project. You can not disappear for years at a time, crafting your solo personal project to perfection, and then suddenly present it for the world to ooh and aah over. The current offering has to be kept alive and updated and supported, and this just has not been happening.

Todays task is to try to make all the places where a product shows (in a list) look the same. I settled on this look: The places where a product shows (in a list) is (linked to Frozen so that you can see the differences); http://template.me.uk/234bs3/index.php - new products for month http://template.me.uk/234bs3/index.php?cPath=1 - new products for month http://template.me.uk/234bs3/index.php?cPath=1_4 - product list in category http://template.me.uk/234bs3/specials.php http://template.me.uk/234bs3/products_new.php http://template.me.uk/234bs3/advanced_search_result.php?keywords=matrox You can see that in Edge/Frozen the lists look broadly similar. I want them all to look exact the same in Frozen2BS4

I usually don't participate in these types of threads, and there have been many, since they usually evolve into a list of things that, in my opinion shouldn't be added to the core, but rather created as modules assuming they don't exist already and most of them do. I can't see using our limited resources (the only active team member) in that manner. Do you really want your only resource bogged down with add-ons that should be developed and maintained by other developers or even shop-owners? To me it would be far better to use your resource to work on things that are needed to maintain the core to keep it current with changes to PHP and other dependencies as well as adding functionality to allow developers to create modules more easily. In other words bigger picture stuff. Having said that I would like to see... 1. A market place app (which I think our resource is already working on). 2. An auto-up-date routine for the core. Updates are simply pushed out to those who want them. Again I think our resource has been working on that. In would be nice to have those two pieces in place and then the next steps can be taken. Dan .

I've been thinking of doing the same. Here are some changes that should be made (not all are mistakes): 1 - In includes/modules/content/product_info\templates/tpl_cm_pi_price.php, the variables in sprintf are in the wrong order. Change <h2 class="h3 text-right-not-xs"><?php echo (tep_not_null($specials_price)) ? sprintf(MODULE_CONTENT_PI_PRICE_DISPLAY_SPECIAL, $specials_price, $products_price) : sprintf(MODULE_CONTENT_PI_PRICE_DISPLAY, $products_price); ?></h2> to <h2 class="h3 text-right-not-xs"><?php echo (tep_not_null($specials_price)) ? sprintf(MODULE_CONTENT_PI_PRICE_DISPLAY_SPECIAL, $products_price, $specials_price) : sprintf(MODULE_CONTENT_PI_PRICE_DISPLAY, $products_price); ?></h2> 2 - In languages/create_account_success.php change priviledges to privileges. 3 - In languages/shopping_cart.php change two instances of "don't" to "don\'t". 4 - In languages/shopping_cart.php change "immediate deliver" to "immediate delivery". 5 - In includes/application_top, add the deprecated flag to prevent future warnings and disable display errors since it is a security hole by changing error_reporting(E_ALL & ~E_NOTICE & ~E_DEPRECATED & ~E_STRICT); to error_reporting(E_ALL & ~E_NOTICE & ~E_DEPRECATED & ~E_STRICT & ~E_USER_DEPRECATED); ini_set('display_errors','0'); 6 - In includes/template_top.php, change the version number to the current one because some icons being used won't work in V 5.0.6. <script defer src="https://use.fontawesome.com/releases/v5.0.6/js/all.js"></script> to <script defer src="https://use.fontawesome.com/releases/v5.0.9/js/all.js"></script>

I have split and hidden the shitty politics, apologies to all.

Here is the next part of the Puzzle. 0:00 Donald Duck makes an account using create_account.php on this page there is a MATC checkbox that MUST be ticked to allow the account to be created also two modals, one for privacy, one for terms Donald agrees and sets up an account. 0:36 Donald now goes to account.php and clicks to get to the GDPR page 0:44 Donald now sees everything the site knows about him of particular interest is SITE ACTIONS, where shopowner has stored the fact that Donald signed up *and* agreed to T&C/Privacy In the Database, shopowner has also stored the details; 1:03 Donald now checks out. 1:24 Donald hits checkout_confirmation.php on this page there is a MATC checkbox that MUST be ticked to allow the order to be processed also two modals, one for privacy, one for terms Donald agrees and completes his Order 2:04 Donald now goes back to GDPR page of particular interest is SITE ACTIONS, where shopowner has stored the fact that Donald agreed to his details being passed to external companies In the Database, shopowner has also stored the details;

New progress bars are now on the Test Site. Obviously if you wish to see them, you need to be checking out. If you are checking you need an account, please at least use a real email address so that my server doesn't bounce back undeliverable messages at me, thanks. I hate seeing people test stuff and using (eg) wenvjowe@venvoevn.com type of bullcrap. Hooks System For anyone who knows a bit about the Hooks system, this has had an overhaul so that it is now possible to pass parameters through hooks; EG: checkout_shipping.php <?php echo $OSCOM_Hooks->call('progress', 'progressBar', [Parameters]); ?> And on EG checkout payment all you need to do is pass through a different Parameter, and that increases the display of the progress bar. Henceforther shopowners/developers can have two or more pages using the same Listener...just passing thru a different Parameter. And, even better, no limit on the what Parameters you want to pass through to your Listeners. #forward #we #go

New version 5.6 for 2.3.4.1. CE Frozen uploaded: QTpro BS 5.6. Compatibility: OsC 2.3.4.1. CE Frozen PHP: 5.6 - 7.2 Changes versus QTpro 5.5r1 BS - Updated for 2.3.4.1. CE Frozen - Updated template naming and auto inclusion in content modules - cleaned code and fixed undefined errors in stats_low_stock_attrib.php - updated included modified core files to CE Frozen - included modified action class "add_product.php" - updated hook for auto register naming convention - tested with PHP 7.2 Version 5.5r2 for 2.3.4.(1.) EDGE included Changes versus QTpro 5.5r1 BS - fixed missing function error in shopping cart module

Carousel is built into BSv4, and a quick and easy module built, so all that needs to be done is turn it on. No limit to number of images and no need to change any core code Grid/List module is now a lot smoother Footer area is now cleaner code Lots of code changes in other places to suit the new layout style of BSv4 I know some people appreciate what goes on, I am certain that others do not. That's life.

Not being on the forum 24/7 does not mean the same as "inactive". HPDL: Will be returning shortly, I am in contact with him. GB: I am working on porting Frozen to Bootstrap v4. JZ and TG: Appear to have left. HW: Lots of hot air.

" BTW, the domain here expires end of this year, unless we hear from HPDL, it makes me wounder what's gonna happen " Look at any domain and it has a expiry date! Many of my websites expire ant the end of this year "omg" what will I do??? Nothing they are on auto renew like many sites. The expiry date means nothing. Making statments like this helps no one.

If you have not downloaded the Final/Frozen version, DO SO NOW! As I understand it, the Github project has been archived, and is pending deletion! Since there will be no more development on it, I propose posting any bugs and/or fixes here. I'll start: In the Also Purchased module ... There is a tiny mistake in cm_pi_also_purchased.php. Line 62 has "Enable Reviews Module" instead of "Enable Also Purchased Module".

Better developers could also contribute a 'lite' add-on to the core and offer a 'premium' version via the market place. There are lots of possibilities. We need to get away from thinking that everything needs to be included in the core. It can be included in a separate or extras package. In my opinion, for the core, less is better. Dan

wysiwyg html editor for the admin size , like CKEditor :)

Further ideas: 1. Product checkboxes for easy move, copy or delete multiple products 2. Standard integration of seo url,s 3. Standard integration of product image thumbnailer. 4 Possibility to hide categories. 5 Standard integration of Purchase Without Account 6. Possibilty to change boxes layout , left , right or no boxes on selectable frontstore pages. and more but for now thats what i can think of. :)

Yes! it is about time these very old images dissapear and make place for some modern products with new pictures. Also no need for 28 products and empty categories can also be removed. I think 10 products is enough to get an idea. Now is a perfect time to change to an up to date Oscommerce.

Dear @wHiTeHaT Just a cosmetic detail, to make better marketing to osCommerce. It would be nice to add some modern products such as Samsung S9 or iphone 8 cell phones or iphone x to the catalog to give it a renewed look. Having prehistoric images does not help new users thinking that osCommerce has not evolved in all this time. Best regards, Valqui

+ and liking................... i LOVE IT. posting your ideas & wishes for osCommerce keep going on would give more insight to the things you want. i have nothing against: - better attributes - better customers groups - better admin rights to admin sections. - better checkout system it is CE, accepted as a community edition. Raise your voice or be ignored.

The trolls ate them

For "others" , they just need to adapt. There is already a mess. default 2.3.4.1 users previous BS users who NEVER upgraded. The bottom line needs to be drawn. For that a roadmap needs to be made towards a osc version that will be accepted by a wider audience committed to oscommerce. It will NOT going to be easy. But i have a plan, and it WILL work. The first plan: Any post FLAMING and RANTING about oscommerce Will be hidden. Positive critics are accepted and should be read as. And will be moved to: https://forums.oscommerce.com/forum/13-general-discussions/

Store Logos Multi 1.0 Responsive and Localized Store Logos Store Logos Multi Compatibility: Responsive 2.3.4.1 BS CE Frozen and all 2.3.4.(1.) BS EDGE versions and GOLD PHP 5.4-7.2 How it Works: Responsive and Localized Store Logos will add a new Logo page to your admin where you can upload 3 different logo sizes for each of your store languages. A new alternative header content module is included which will display the Logo just like the standard core logo module. Purposes: 1. Serve different logo sizes to allow the visitors browser to select the most apropiate for it’s device size and resolution. The browser will automatically download only the logo which fits best it’s need. Example: You are using a banner style store logo which is set to half of the header width (col-6) - for a standard desktop screen and a retina tablet a width of about 640px would be good - for a retina desktop device with double resolution like i-mac, 1280px would be better - for a small simple mobile phone 320px would be optimum to save download time. This add-on allows you to upload 3 different sizes of your store logo (1280px, 640px and 320px for this example) If your store logo uses the full width (col-12), upload for example the sizes 2560px, 1280px and 640px. 2. If you wish to use different versions of the Store Logo for each of your store languages, you can now easy upload a different set of logos for each language. It is not mandatory, You can use one and the same logo and only upload to the default language. It will be used then for all languages.

I am not a developer or a coder so don't expect too much. It should just work but if not stick it one here and I will do my best to help. Info links modal popup Edge v2.3.4.1 CE You can try it out on this test site.https://tbyb.co.uk/ A simple footer info block addon it gives you the information links as modal popup. Why? Well on large sites it can take time to find what your looking for. With stock osC if having found it you press a info link your taken away from the page you were looking at. With the popups the page stays behind the popup and when you close the popup you carry on with what you were looking at. Again totally standalone with no core code change. Once you have copied all the files over go into admin/Content /Modules and install “JCM Information Links Block”. Turn it on and turn off the stock info block (do not uninstall original not sure why but it has to remain for the new one to work! Just turn it off. If anyone knows why this is let me know) :) This version will not change the contact us link. That remains as new window. The other stock links are not replaced. We make new ones for the popups so you can revert back anytime you like. To add new text for each link simply edit one file. /includes/modules/content/footer/templates/tpl_cm_footer_jcminformation_links.php Simply find the following and replace the stock text between each marking. Line 40 <!-- Place your Shipping & Returns text below this--> <!-- Place your Shipping & Returns text above this-→ Line 60 <!-- Place your GDPR text below this--> <!-- Place your GDPR text above this-→ Line 298 <!-- Place your T&C text below this--> <!-- Place your T&C text above this--> A basic GDPR statement is provided as a boiler plate you can edit this to your requirements. Make sure to replace all red stuff **business name** with your own details. Keep it plain text. That’s it nothing to complicated and should make the store front a little more user friendly. I do have a version that replaces the contact us with a modal popup but as that requires setting up the email I am not going to post that in the apps. You can see the email on the test site. If anyone wants that just pm me and I will email you the file.. It looks the same so be careful you are looking at correct one when testing. Zahid On clicking a link you get window popup. As you can see the page is still open behind popup. Popup can be closed by pressing the x in top or close button at bottom.

@14steve14 Obviously with a backup done first!! This first query is the "Master Blaster"... delete from customers where customers_id not in (select customers_id from orders) and customers_newsletter = 0 that will remove all customers that have never made an order AND are not a subscriber. You then need to clean out other tables, and we know that any ID that does not exist in the customers table, should not exist anywhere else; delete from action_recorder where user_id NOT IN (select customers_id from customers); delete from address_book where customers_id NOT IN (select customers_id from customers); delete from customers_basket where customers_id NOT IN (select customers_id from customers); delete from customers_basket_attributes where customers_id NOT IN (select customers_id from customers); delete from customers_info where customers_info_id NOT IN (select customers_id from customers); delete from products_notifications where customers_id NOT IN (select customers_id from customers); delete from whos_online where customer_id NOT IN (select customers_id from customers); delete from reviews where customer_id NOT IN (select customers_id from customers); delete from reviews_description where reviews_id NOT IN (select reviews_id from reviews); And that should do it. But all of this is UNTESTED...

New Progress Bars for Checkout Hooks system is updated to accomodate this. Now all you have to do is change 1 hook file and your changes are reflected on each page that has the progress bar. OLD: NEW: + Points: Removes about 10 lines of .css Can now affect all pages displaying the progress bar by amending one file (eg if you wish to display something else) - Points: Not as pretty as the older layout? Always moving forward, even if steps are small.

This addon is a replacement for the previous MATC module. It is fully compatible with all community edition versions of oscommerce but it does require raiwa's modular checkout pages addon to be installed.. Once installed, it will place a check box on the create account, checkout payment or checkout confirmation pages, depending upon the settings in the module. The check box prevents the customer from proceeding unless they check that box. If the check box is to appear on the create account page, a few file edits are requited. Otherwise, it all works with the installation of modules.

new version uploaded: Featured Products BS v1.5. Changes version 1.5: - Updated for 2.3.4.1. CE Frozen - Updated template naming and auto inclusion in content modules - updated deprecated each function in featured_products.php - fixed undefined messages in admin/featured.php and admin/select_featured.php - sanitized search input in admin/select_featured.php - Added "is-product" class and "data-is-special" in content modules and featured products page - Added "data-has-attributes", "data-in-stock" and "data-product-id" to "buy" buttons in content modules and featured products page.

The core will be changed and will come close to 2.4. Many people have now installed the ce edition. currently i work on an bootstrapped admin. I try to keep it as close to the origin admin with minimum changes. i also keep using html table(s). Each page will be limited to only 1 table for the data and 1 table for the configurations. All admin pages have a nice heading and bootstrapped table for the data. Some pages have a button, a search form or a drop-down menu pulled right from the page heading. Some of them have a mix of these. I know there are some repositories around where the admin is already bootstrapped. Yet these come all in some kind of personal flavor. This admin is brought to a very minimum so that it is easier for existing admin files (coming from add-ons) to merge. Still this is not the real good way for a market add-on, and will be only work for (admin) add-ons that have their own admin files. An improved App system for 2.3.4.1 CE could give a solution. Another option will be KITT, where can edit any file via the admin as you please, with an option to role back. This means there is still room for DIY add-ons and the risk to break your osC system. But that is just how it works. The market add-on will be serving the CE edition initially. Then i will try to see how far we can get to come close to a 2.5.0 CE. As that is going to be a complete diff version users will then be able to choose if they want to install the 2.3.4.1 CE or with the newer 2.5.0 CE. The 2.3.4.1 CE still has a good lifespan. This gives also space for the development on 2.5.0 CE 2.3.4.1 CE + the market will then be the base for 2.5.0 CE. 2.3.4.1 CE will be just a little more friendly to use and will come with some blend-into core functionalities, where some of them we already know from add-ons. These are pretty logical choices. There will be plenty room for other dev's to anticipate on these blend-in add-ons.

WYSIWYG Perhaps better to prevent any html in the database, what about: https://stackedit.io/app# Markdown wysiwyg editor

some thing like this? You can do this by editing admin/categories.php, but to use this you have to pay a small fee. see https://www.tinymce.com/ however you can get free open source but its a little more work to integrate into osc. This is best left to the professional team as needs to be done properly. There are some good options, take a look at this one. https://quilljs.com So much that can be done but so little time and only one team member active now

Uploaded v. 2.0 for 2.3.4.1 CE Frozen: Points and Rewards BS v2.0 Compatibility: Responsive 2.3.4.1 BS CE Frozen PHP 7.0-7.2 ------------------------------------------------------------------------------------------------------------- 2.3.4.(1.) EDGE versions and GOLD, please use Points and Rewards BS v1.2 ------------------------------------------------------------------------------------------------------------- Change log ----------- Version 2.0 - Updated for 2.3.4.1. CE Frozen - Replaced checkout payment hook by content module - Moved checkout payment output from functions/redemptions.php into new content module - Updated installation scripts for 2.3.4.1 CE Frozen and checkout payment content module - Updated template naming and auto inclusion in all content modules - Added support for core modular product info - Added support for Modular Checkout - Replaced modified core template files by complete alternative box and footer content modules Only one manual core file change left: (optional if using) paypal_standard.php

Problem fixed. Its a bug when the store has ONLY ONE category. osCommercians who have only one category and using Seo Friendly Urls must go and comment the line 308 //elseif($citems==1) $children[] = $items[$clang]; //in case we have one category item without subcategories, rare but possible In the next upcoming update this will be fixed... @wHiTeHaT I asked from @Stephan Gebbers to send me info in PM because I knew that I had to investigate the problem on his live website.... After the bug fix I would ( as I did ) post the solution... About $ - who fixes it, it's another story but it would be nice to see if there would be anyone here that could fix it... :-)

I AM A CAPTAIN! No time for losers!

You're in for pain, no matter what you do, but over time the least pain will come from upgrading to CE. That part is fairly easy, but replicating additional features you had in your old store could be tough. If you've kept good track of both add-ons installed and custom coding changes, including why you made those changes (what features are added), you can see what's now built-in, what's available through add-ons (which may have to be updated to work with this version), and what needs to be done custom. "Heavily modified" means different things to different people, but if you've kept track of changes, it shouldn't be too bad. If you haven't kept track, prepare for a lot of work comparing old store with new. A hint: even if your store is running fine at the moment, don't let yourself fall more than a year or so behind on releases. When you run a business, you depreciate equipment with the expectation that after some time that equipment will wear out and need to be replaced -- you should do the same with software. Your host upgrades MySQL and PHP, which causes old code to break. Don't wait to start thinking about scheduled updates until it's an emergency and your site is down.

A new version has been uploaded with these changes: Added screenshots - thanks to member Demitry. Added new classes and changed some of the previous ones. Changed some css in sitemap.php - thanks to member Demitry. Changed the css for the shop side so it is fully responsive. Changed the javascript code to use icons instead of images. Changed the admin infobox to load as a module so the change to admin's english.php is no longer needed. Fixed some security holes in the modules. Fixed a typo in the css of sitemap.php - thanks to member Demitry. Fixed the coding in the sitemap modules that prevented the dropdwon lists from working. Moved the javascript file to the ext/js/ directory. Removed the store address from the sitemap page. Only shows the phone and email address now. Replaced the remaining pre-BS definitions. Rewrote the three modules to get rid of html code (div's instead of td's). Rewrote the install and uninstall files to clean up after themselves when they are used and to work in all shop versions. Please be sure to read the update file since changes have been made that will break existing installations. And note that these changes are for the CE version only. The addon will still work with the other versions of oscommerce but the improvements have not been made to those versions.

Ok you can download and try. Thank you to both BrockleyJohn and wHiTeHaT your input helped get this done much quicker. John as you said the function from the box worked fine. The software builder saved a lot time as well thanks. Products by Manufacturer v2.3.4.1 CE

GDPR & info tabs popup Edge v2.3.4.1 CE It should just work but if not stick it on here and I will do my best to help. You can try it out at the test site. https://tbyb.co.uk/ V1.0 full package by JcMagpie 24-5-2018 Zahid A much simpler footer information block addon. It gives you the information links and as modal popup with tabs so all GDPR , T&C and Shipping & Returns are all shown in one popup with tabs. The contact us is still separate link. Reduces the information footer block to just 2 nav pils. Why? Well gives a cleaner look to the footer and makes reading information much better for the customer. On large sites it can take time to find what your looking for. With stock osC if having found it you press a info link your taken away from the page you were looking at. With the Tabbed popup the page stays behind the popup and when you close the popup you carry on with what you were looking at. Again totally standalone with no core code change. Once you have copied all the files over go into admin/Content /Modules and install “JCM GDPR Information Links Block”. Turn it on and turn off the stock info block or another you may have uninstall it. This version will not change the contact us link. That remains as new window. The other stock links are not replaced. We make new ones for the popups so you can revert back anytime you like. To add new text for each link simply edit one file. /includes/modules/content/footer/templates/tpl_cm_footer_jcmgdprinfo_links.php Simply find the following and replace the stock text between each marking. Line 74 <!-- Place your GDPR text below this--> <!-- Place your GDPR text above this-→ Line 287 <!-- Place your T&C text below this--> <!-- Place your T&C text above this--> Line 60 <!-- Place your Shipping & Returns text below this--> <!-- Place your Shipping & Returns text above this-→ A basic GDPR statement is provided as a boiler plate you can edit this to your requirements. Make sure to replace all red stuff **business name** with your own details. Keep it plain text. That’s it. It looks like this I have kept it plain, You can add css if you want fancy colors. On clicking a link you get window popup with tabs. As you can see the page is still open behind popup. Popup can be closed by pressing the x in top or close button at bottom.

@AAWISDOM Since it looks like you are starting out with a clean install of osC 2.3.4.1, listen to what @Jack_mcs said. While v2.3.4.1 is the last 'official' release, it was just a hot-fix to v2.3.4, which is several years old. In addition to being old, there are concerns that v2.3.4.1 will fail when your host upgrades their version of PHP. The 'community edition' of osC, while not 'official', is the latest version. It is responsive (meaning it will adjust the display to fit the screen size (important for all of the people using mobile devices these days)), much more modular (meaning you can turn features on or off, or even add new features, all without touching the core code), and is PHP 7.x ready. And, as @Jack_mcs said, it handles CSS much better. There is a user.css file which loads last, so you can enter any css definitions you want, all without having to touch the 'stock' css files (which you should never touch). You can find a link to it in my signature below. Now, before you bitch about why the community edition is not official, nor is there any reference to it on the osC website, please note that the owner of the osC name and code has stepped away from the project (we don't know for how long), and he is the only one that can make that change. This is why the community has stepped up to produce an updated version of osC. After all, this is an open source project. Nice way to ask for help, by the way ... Malcolm

Dead? It's at a place I am mostly happy with; php7, a bit modular, responsive etc. Good Luck to all Shopowners.

A nice layman's view article: https://www.scotsman.com/news/politics/insight-the-gdpr-revolution-we-can-t-opt-out-of-1-4742104 There are apparently some unresolved data issues, which will need to be settled by the courts, such as a beauty salon owner required by her insurance company to hold on to customer medical data for 6 years, even if the customer requests that it be deleted. Which takes precedence? If the customer demands that her data be deleted, does she forfeit any claim that could have been refuted by the salon had it kept the data? Or is the salon in trouble for keeping that data after being told to delete it? What if the data is simply taken offline -- short of a search warrant, how would a customer know what has been kept, short of suing for malpractice and seeing what's there? I like the joke in the "letters" section: "I've found a really good GDPR consultant". "Can you give me their email address?". "No"