Jump to content

Leaderboard


Popular Content

Showing content with the highest reputation since 05/18/2019 in all areas

  1. 5 points
    burt

    Confusion over osC Versions.

    CE is the umbrella term for my "Responsive" fork on Github. What I am working on is called Edge. Gold (release) is a fixed point along that Edge timeline. Frozen (release) is a fixed point along that Edge timline. I suspect there may be more fixed points in the future, but that depends on the Community at large helping...instead of throwing stones. Edge is (and always has been) a work in progress. It's easier to say the work is "bad" than to actually help shopowners get a good responsive and useable version of osCommerce, hence some of the posts we've all seen in the last 12 months. And then I see those same moaning minnies using the CE for their clients or for their own shop Copyright Any file that IS in CE and IS NOT in official is a new file. New files are copyright their respective author. If anyone believes they wrote one of these new files and the copyright is incorrect on that file, raise an issue on Github and it will be sorted. Respecting copyright is very important and if I have failed in that, I want to know. Naming/Tagging (and other areas that could be changed) Agreed that things could be better, but you know what...get involved and it might get changed. The last person who did get involved...wanted the version checker changed on release of Frozen, so it was changed to accommodate what he wanted. Moaning and groaning (about anything I do or don't do) whilst you have done nothing to help...is not an ideal situation. When all that is said and done, I thank you all for your feedback, it's been taken on board. Now, a couple of people who have posted in this thread have actually done positive things for the community since Frozen was released - I'm sure you have received thank you's from the thousands of users of the CE releases. If not, that's not ideal - accept my thank you now - thank you. As for the ones who are "loud" in their opinions yet have done nothing to help, I challenge you to actually step up to the plate and start swinging. If you don't swing you won't get a home run... As you guys have been so candid in your opinions, I hope that I'm allowed to give my opinion in the same candid manner. So I ask each of you who have posted here and anyone else reading this a rhetorical (ie does not need answering here, just have a think on it) question..."have you done your part in making osCommerce a viable option for todays shopowner needs" ?
  2. 3 points
    version 3.1.1 is available for download from https://apps.oscommerce.com/Apps&XpKWd&quick-update-bs Sponsored by @supercheaphobb it includes options for working with prices including tax and adding a datepicker to the specials expiry date. It also fixes the manufacturer query error that @radhavallabh hit the other day but not the latest bug above. Update is simple - just copy the files. New options are added automatically when you access the page and set to default.
  3. 3 points
    Jack_mcs

    Article Manager v1.0

    A new version has been uploaded with these changes: Compatible with php 7.2. Compatible with BS4. (see note below) Header Tags SEO no longer required. (see note below) Added code to automatically add the title and tags for an article to Page Control in Header Tags SEO (if HTS is installed). Added the date posted on the blog comments page. Added a link to the customers account on the blog comments page, if it exists. Added multi-select option to the Cross Sell page in admin. Added a module to display articles on the home page. Added a module to display articles on the product page. Added the article ID to the article listing page in admin. Added reply to blog in admin. Added IP tracking for blog articles. Added option to require approval for blog posts. Changed the articles infobox to use ssl, if set, to fix a non-secure warning. Changed the articles infobox to only display the articles section if articles exist for those sections. Changed the format of the article listing pages on the shop side. Changed the default setting for an article to non-blog. Changed all of the article listing to use the sort order setting. Fixed code to handle the filter database definition correctly. Reported by member @vmn. Fixed code for the listing description text to prevent problems when html is used. Reported by member @vmn. Fixed Cross Sell code to the blog page. Fixed Cross Sell code to display the images. Fixed article listing page to only show blog or non-blog articles. Fixed code in the articles box to correctly show upcoming articles. Fixed the layout problem in authors section of admin. Fixed coding mistakes on the topics page that caused incorrect links. Fixed coding mistakes on the articles page that caused incorrect links. Fixed coding mistakes in the articles infobox for upcoming article that caused incorrect links. Made many changes on the blog comment page in admin fixes and improvements. Replaced date code with jquery's datepicker. Reported by member @vmn. Replaced all uses of NONSSL with $request_type. Replaced the topics code in the articles infobox with standard oscommerce code. Removed preview from articles creation page. Removed preview code in admin blog comments. Removed unnecessary database code from the articles box. Removed extra files in the new directory for the CE version. Removed redundant functions used by the articles infobox. Removed all filename and table definitions so it now works in CE shops. Rewrote the new articles page to remove html codes. Rewrote the upcoming module to remove html codes. Notes: 1 - The changes in this update are only for the CE versions. The code for the CE version will probably work in 2.3.4 shops, though I haven't tested it, but not any version before that. There were far too many changes in this version to get them to work with the older versions. It can be done but will take a bit of time. 2 - I included the code for BS4 versions. This was not thoroughly tested but I don't think there are any problems in that version. 3 - The requirement to have Header Tags SEO installed has been removed. This was not thoroughly tested but I don't think there are any problems caused by it. You have to turn the option for Header Tags SEO off in the settings. Please note that if you don't have Header Tags SEO installed, you will not be able to set the title and meta tags from admin. You will need to figure out how to do that manually. Also, the Ultimate SEO url rewriter won't change the url's as expected. My sincere thanks to @FrediHis help in troubleshooting this saved weeks on the release date. It was invaluable since he pointed out things I probably would not have seen.
  4. 2 points
    That's up to @shetch it's his code. The issue is with bootstrap scss line 114 $contents[] = array('text' => tep_draw_separator('pixel_black.gif', '100%', '1')); The height of "1" is beeing over ruled by the scss .img-fluid { max-width: 100%; height: auto; } So simple hack fix set /public_html/admin8262/whos_online.php <style> .img-fluid { max-width: 100%; height: 1px!important; } </style> @shetch I'm sure will have a proper fix in time. For now works ok.
  5. 2 points
    MrPhil

    Confusion over osC Versions.

    OK, Peter, let's draw a diagram: +--------------------------------------------------> osC 2.3.4.1 ------------------------------------> ??? | (official) basically suppress PHP 7 warnings osC 2.3.4 ---+ (official) | Gary Burton's now 2.3.4.1 +---- CE stream -----> Gold (snapshot) ---> known -----> changes -----> Frozen (snapshot)----> Edge continues on GitHub as Edge incorporated development BSv3 store only modularity, PHP 7 BSv4 both sides PHP 7.2 That, as I understand it, is more or less the history of osC over the last 4 years or so. Forget about "Gold". It's an obsolete snapshot. The "Frozen" snapshot is a quite stable, but needs a few patches. It is BSv3 (on the public store side only, not on admin). Gary has stated that he intends to make no further changes to Frozen -- that's what it literally is. He is working only on "Edge", with BSv4 responsive on both sides (store and admin), and some level of PHP 7.2 compatibility (eventually fully). It is a work in progress. There is no such thing as "Frozen BS4". It's either Frozen (with BS3) or Edge (with BS4), unless someone has their own private fork. In that case, they should make it very clear when discussing on this forum what they're talking about. Most people should use Frozen (plus patches), unless they want to be on the bleeding Edge of development. If what you want is a working store, I'd stick with Frozen. If you have the time and skills, and enjoy working with a constantly-changing code base, Edge could be for you. Yes, Frozen should be officially released as osC 2.5, but I'm not holding my breath. Yes, naming and versioning could be much improved by Gary, to reduce confusion. Only one repository is needed, as Gold and Frozen are fixed in time and space.
  6. 2 points
    raiwa

    Modules Control

    New Version uploaded: Module Control 1.1.0 Changes: - removed support for navbar modules. Thanks to @Omar_one for the error report - fixed typo for filename "osc_template.php" in instructions. Thanks to @Omar_one for the report
  7. 2 points
    raiwa

    Modules Control

    Hello @Omar_one, I had a deeper look now and found that the navbar modules are not processed at all in osc_template.php class. They are processed and included in the navbar parent module. Therefore it does not make sense to include them in Modules Control. I'll remove them and update. Anyway it's not common to switch off the navbar modules for selected pages and if needed it can be done in the modules themself. Thanks for your help and patience. Best regards Rainer
  8. 2 points
    Tsimi

    Discount Code BS

    @raiwa Discount_Codes_5.0.0_BS sounds good to me. Also separating the BS4 and BS3 stuff by keeping it in separate catalog folders sounds like a good plan. I will test your files tomorrow, 1:30 AM here now, and get you some feedback asap. Thanks
  9. 2 points
    raiwa

    Confusion over osC Versions.

    CE stands for Community Edition and refers (now) to the complete series of Burt's bootstrapped edition. From early 2.3.3. 2014 repo until actual 2.3.4.1 EDGE BS4, including the fixed GOLD and FROZEN versions. The name "CE" appeared maybe a couple of years ago just to distinguish Burt's repos made with the help of other "Community" members from the "official" versions.
  10. 2 points
    I'm glad this post has been created. I've been using and developing with osC for 16 years ish and normally I wouldn't look any further than the oscommerce.com/products to see if there are any updates. After becoming more active in the forums recently I've discovered the existance of gburton repo and had names of 3 different versions thrown at me with no real clear answer of what is production ready, the difference between them etc and then debates amongst users of which version to use. You can see the post where I'm trying to work it out here I've been a PHP developer commercially for 18+ years, experience of osC for 16 and for someone like me to be confused over this what chance does any normal consumer/Joe Public installer have? Artcolnc's reply has helped but still unsure if CE is the Frozen download everyone talks about, it reads historically like it is but I've had to read between the lines to establish that. I think interchanging references contribute to the confusion also, if 2.3.4.1 CE is 2.3.4.1 Frozen and vice versa, then one of those terms should be picked and stuck to. I've seen both used separately in the forums. Then I just clicked one of the links in MrPhil's signature and found that Gold isn't Frozen (or at least the topic I'm about to link to implies it isn't) but Artcolnc's breakdown implies it is (Gold was released, 2.3.4.1 hot patch applied, frozen was released). From the link below I understand they may be the same codebase and so run parallel to eachother but are different and separate forks of 2.3.4.1. Clearly states Gold and Frozen are two separate varieties (and not stated but are 2.3.4.1) - UPDATE: or not both 2.3.4.1 as the post above says it's 2.3.4. Can anyone else see/understand why I'm still confused? Everyone here is very familiar with the fantastic progress/work Gary's been doing (Gary none of my comments are in anyway intended to take away/detract from the credit you deserve) so this all may seem simple enough to the active members here, you've been following it this whole time and you know the history of development. Any other member of the public interested in installing osC will see this and run a mile straight into the arms Magento, Presta/Open Cart or WooCommerce. There's no possibility of changing what's displayed on oscommerce.com/products so most will install stock osC 2.3.4.1 then possibly come here once they realise many of the popular payment modules don't work anymore (the amount will grow as time passes and HPDL is absent). Again just my opinion...but I would say frozen and gold need to be in their own separate new repo's within Gary's github (it's free to do, you can have multiple repos). Both clearly documented that they are Production ready but End of Life/no further development, possibly only bug/security fixes. Then BS4/Edge can be clearly marked as experimental/development/experienced only. If news users venture into the forums there needs to be a united/unanimous response from existing members as to what fork to install/update to if they want to. Then maybe the most active members in here could agree to have a common signature (at least part of it) similar to the above logic, below as an example: I'm not trying to be inflammatory or argumentative, I hope that's not how it's coming across. I'm just trying to give you all some feedback of my experience so far of my introduction to these forks and the confusion around them. If anything I've listed above is incorrect about which version is which etc then that just further illustrates the problem.
  11. 2 points
    burt

    Confusion over osC Versions.

    Thanks for the feedback and support of the project.
  12. 2 points
    Well with a cup of coffee and some time spent pulling my hair out trying to get the page select to work with the existing function and failing miserably came up with a simple alternative. in the add-on template file add the following at start of <?php if ( basename($PHP_SELF) == 'index.php' && $cPath==null) { ?> then at end of file add <?php } ?> What you are doing is basicly saying if it's not an index page ignore this code. So on pages like product_info or checkout or contact us that header will not show. It will show on any page that is part of index page. My not be the most elagent way of doing this but it works.
  13. 2 points
    ArtcoInc

    Confusion over osC Versions.

    (as a bit of background) As has been said before, the Community Edition does not have an accurate version numbering system. When Burt started this project back in 2014, osC was at version 2.3.3.4. So, the Community Edition, all through its early development, was also v2.3.3.4. Every release of the Community Edition during these early times was called v2.3.3.4. When osC upgraded to v2.3.4, Burt brought the Community Edition code base up to the v2.3.4 code base, and the Community Edition became (and stayed at) v2.3.4 while further development was happening. In January 2015, Burt released the 'Gold' fixed release. Development still continued, with every release still being called v2.3.4. When osC had the v2.3.4.1 Hot Patch applied, Burt also applied the Hot Patch, and the Community Edition was bumped up to v2.3.4.1. Once again, development continued, with every new release still being called v2.3.4.1. Burt released the 'Frozen' fixed release in August 2018. No additional development is being done on 'Frozen'. Some bugs have been identified in 'Frozen', and there is a thread here on the forum identifying them (and some fixes too). At lease one member here is maintaining a patch file of these fixes needed for 'Frozen'. Development still continues (usually called 'Edge', although that is not a fixed release), and the version number is *still* v2.3.4.1. Some significant changes have been made since 'Frozen' (such as the 'upgrade' from BootStrap v3 to v4), causing some compatibility issues with prior versions, and many (most?) add-ons out there. So, there is no one 'Edge' version. Releases prior to 'Frozen' could technically be called 'Edge', and every release since 'Frozen' is also technically 'Edge'. A release of 'Edge' from a month ago may not (and probably is not) the same as 'Edge' today. Also, there is no 'Frozen' BS4. All changes to upgrade to BootStrap v4 came *after* the release of 'Frozen'. I won't go into why this has happened, nor into what could/should be done to address this. And I encourage others to not feed into a woulda/coulda/shoulda rant that will add nothing to the discussion. Malcolm
  14. 2 points
    MrPhil

    Confusion over osC Versions.

    I can't agree with Gary's reasoning on this. Since it's obvious that Harald will never legitimize Frozen as the official osC 2.5 (and later, some form of Edge as 2.5.1), it's time to stop bending Frozen to try to fit with the news and updates stuff. Just comment out all the code that interacts with updates and "latest version" items, and put up a "check GitHub here for latest version(s)." Or something like that. What developers keep losing track of is that most of the users of osC are business people, not computer nerds. It is unreasonable to expect them to dig through source files to find vague and confusing version stamps, and to have to remember the exact date on a zip file! They're just trying to run their business, and the more roadblocks we put in their way to making it relatively easy to manage their online store, the more of them will desert to easier-to-use platforms. What most want is a selling appliance, not a whole new career. The whole mess of ancient official versions (why in 2019 do we still have to tell newbies that they installed the wrong version?) and "Frozen with BSv4" fiascos couldn't be better designed by a competitor to sink osC.
  15. 2 points
    @Kurre So it does not affect every where you are best to create your own like here line 40 in /includes/modules/boxes/bm_categories.php "mycatagory" $OSCOM_CategoryTree->setParentGroupString('<ul class="nav nav-pills nav-stacked" id="mycatagory">', '</ul>', true); The change #columnLeft to #mycatagory in user.css
  16. 2 points
    Has been updated to make it work with BS4 and other small changes. Featured products with Ribbon v2.3.4.1CE Also the header verson is now on the apps section. Use only one on the same site to avoid conflicts. Featured products header carousel BS4/3
  17. 2 points
    That should not be required if your using the new header code as that can be changed in admin
  18. 2 points
    raiwa

    Modules Control

    New Version 1.0.3 uploaded.  Modules Control Changes Version 1.0.3: - added script to admin/modules_control.php to scroll back to top after update to show success message.
  19. 2 points
    check your code to see what is beeing called for boostrap in template_top, just inspect using browser tools. <link rel="stylesheet" href="https://stackpath.bootstrapcdn.com/bootstrap/4.1.0/css/bootstrap.min.css" Boostrap 4 is the update to Bootstrap 3 , runs a bit faster is less resource hungry and introduces a few new classes among other things.
  20. 2 points
    Not sure if many will need this but here it is for those (one or two) that may 😊. Has been updated to allow 1) Ribbon text to be set in language file 2) Set number displayed on small, medium and large screens in admin. 3) Ribbon color and gradient can be set in admin 4) Added class to limit length of text display to one line to keep compact. ( css can be removed in template file ) Only for CE Frozen BS3 or Frozen BS4 If you already have one running then you don't need to install the header_tags again. Enjoy! Oh and for those who wish to see it running it's on the BS4 test site but running in static mode. https://chilleddisplays.co.uk/ Featured products with Ribbon Header v2.3.4.1CE V1.0.zip
  21. 2 points
    burt

    Editing Footer Links...

    In quite recent (Edge, BS4) I changed the links system to make it easier - so you can now amend one file to add in a new link; https://github.com/gburton/Responsive-osCommerce/blob/master/includes/languages/english/modules/content/footer/cm_footer_information_links.php#L22-L27 this auto-updates the list that shows in the footer area by simply adding another item to the CONST array In older versions (Frozen, Gold etc) you need to amend two files https://github.com/gburton/Responsive-osCommerce/blob/2341-Frozen/includes/languages/english/modules/content/footer/cm_footer_information_links.php#L22 add lng define in this file https://github.com/gburton/Responsive-osCommerce/blob/2341-Frozen/includes/modules/content/footer/templates/tpl_cm_footer_information_links.php#L8 add list item here
  22. 1 point
    JcMagpie

    Confusion over osC Versions.

    I don't think github is the issue here, version_checker.php pulls data from the osc website to check if it's the latest version. curl_setopt($ch, CURLOPT_URL, 'http://www.oscommerce.com/version/online_merchant/' . $major_version); The main issue is that users simply don't know which version they have installed as the install has no install date stamp or version in the code other than stock 2.3.4.1 CE which I assume HPDL has control over 😊. Now anyone with file access can simply look at the server date stamp on installed files, but an end user may not have this or may not know what they are looking for. Most people will have admin access and will simply click version checker and get the stock responce Installed Version: osCommerce Online Merchant v2.3.4.1 CE Which is no use to anyone as it could be anything. As I said a simple addition to the version_checker.php file could fix this. Even if this is not done on the github, it takes all of 5 minutes to edit the one file required, Some responsability needs to be taken by the person doing the shop install, be that a developer or end user. After all it's just good house keeping.
  23. 1 point
    Omar_one

    Modules Control

    @raiwa Error Message :implode(): Invalid arguments passed is type of error message occur when implode function do not get any array with string to implode. I fixed and now there is no error anymore by adding an array change this (line 87) return implode("\n", $this->_blocks[$group]); to this return implode("\n", (array)$this->_blocks[$group]); BR Omar
  24. 1 point
    Look your Db and the varchar product name. You can change the number until 255.
  25. 1 point
    Of course, that's on the old store's site, pointing to the new store site. If you've lost access to the old site, you're probably out of luck.
×