Jump to content

Leaderboard


Popular Content

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

  1. 7 points
    Harald Ponce de Leon

    Naming Convention

    Yes, at Github. 1.0.0.0 to 1.0.0.2: https://github.com/gburton/Responsive-osCommerce/compare/v1.0.0.0...1.0.0.2 1.0.0.2 to 1.0.0.3: https://github.com/gburton/Responsive-osCommerce/compare/1.0.0.2...1.0.0.3 They will be made aware as CE releases use the same update mechanism from v2.3. This means the update procedure is manual for v2.3 based CE releases (the architecture does not support online updates). Automatic updates will first arrive with v3 and v3 based CE releases. Community Edition maintainers have the ability to push out a release to the website without my intervention. In fact, the website automatically checks Github once every hour to see if a new release has been pushed out at Github and automatically updates the download page and posts a news announcement if one was posted at Github. This will be addressed when Community Editions are officially announced. If they want to stay on PHP 5.6 they can with their current installation. If it runs perfectly today, it will run perfectly tomorrow, and there are active developers in the forum that can help when problems arise. If they want to move to another release or platform, they can't stay on PHP 5.6. There is a lot of excitement when releases are pushed out, however your current installation is not going to burn if you don't upgrade immediately.
  2. 4 points
    swguy

    Frozen

    Whoops! You misspelled "Thank you, Burt, for all your hard work in keeping the osCommerce project alive and relevant. We know we have to keep up with evolutions in PHP and other technologies, and we're glad you are helping us do it."
  3. 2 points
    puddlec

    Phoenix

    noticed a problem with the zip for 1.0.0.3 the security check for github folder language file it is in a folder called security_checks and not security_check this is a problem with the zip file only it is correct on github itself
  4. 2 points
    ruden

    Phoenix

    haraldpdl began to make changes to the branch Responsive-osCommerce https://github.com/haraldpdl/Responsive-osCommerce/commits/php73 if push branch I'm with you Phoenix
  5. 2 points
    burt

    Phoenix

    Versioning Feedback well received from previous discussion & taken on board ... so I will do my best to keep on top of versioning. I may miss some but please blame that on my age and eyesight Versioning is set at a.b.c.d (aka 1.0.0.0 -> 1.0.0.1 > 1.0.0.2 and so on) If bug(s) are squashed or typo's or other minor things {d} will update +1 If a new feature is added (say, for example, the shopping_cart.php page went modular) {c} would update +1 {d} would reset to zero If a major update occurred (not sure what it would be...) {b} would update +1 {c} would reset to zero {d} would reset to zero I will also provide a zip file for each movement of {b}{c}{d} A gotcha to bear in mind; v1.0.0.23 is NEWER than v1.0.0.2 I have found it helpful to say the number rather than read the number (if that makes sense), eg one.zero.zero.twothree is less easy to work with than one.zero.zero.twentythree or put another way it's loads easier to immediately recognise that "twenty three" is a higher number than "two". I hope that all makes sense, and goes someway to making life easier for shopowners and developers alike.
  6. 1 point
    burt

    Naming Convention

    There seems to be some confusion over the Naming Convention chosen...so, as posted elsewhere, let's set the record straight; I originally called it "BS" as a bit of a joke. I still like that name as it stands for *cough*BS*cough* err BootStrap. When it got quasi-official acceptance, that was changed to "CE" which stands for Community Edition. Under the umbrella of CE is (as of today) ONE release; PHOENIX [ https://github.com/gburton/Responsive-osCommerce/archive/master.zip ] Bootstrap v4. There are also two development Tags which were fixed points in the timeline to release of Phoenix; GOLD [ https://github.com/gburton/Responsive-osCommerce/archive/v2.3.4-GOLD.zip ] Bootstrap v3. FROZEN [ https://github.com/gburton/Responsive-osCommerce/archive/2341-Frozen.zip ] Bootstrap v3, with more modularity. Simple, isn't it Well, I think so even if you don't.
  7. 1 point
    Jack_mcs

    What to do with .com and .co.uk

    Pointing it to the .com site just does that. It won't gain you anything other than making sure anyone using that domain name ends up on the other one and you prevent a competitor from using it. Having the .co.uk point to .com may be useful for UK searches since google UK will return those due to location. Creating an information site can be useful for SEO purposes, if done correctly. You can use a link from it to the .com site, or vice versa. But not both if you end up with a duplicate site since google may punish for that. But don't expect anything useful from the search engines right away. They will usually delay ranking for many months to insure the site is real. Otherwise you could create a hundred shops today and point them all to one site in an attempt to help that site. But I think having a different site with a similar name might be confusing to your visitors. They may type in .co.uk by mistake and see that you don't have products and assume the site is no longer available for products. So you would want to make it clear the sites are related. Personally, I think the name is too similar to the original to be anything other than a pointer to the original. One exception might be if you want to target your UK visitors differently, like giving them a discount or location-specific options. The .co.uk site will generally be returned to UK searchers for the same search term over the .com, though that assumes the pages are setup for the same keywords.
  8. 1 point
    burt

    Phoenix

    Yes, we say thank you to Harald for his pushes yesterday. There's a lot of changed files so going to pull it into a branch and test it out. Many thanks Harald!
  9. 1 point
    burt

    Phoenix

    1.0.0.3 hotfixes and enhancements How to update Make sure you have applied the 1.0.0.1 hotfixes -> 1.0.0.1.zip Make sure you have applied the 1.0.0.2 hotfixes -> 1.0.0.2.zip Apply the 1.0.0.3 hotfixes -> 1.0.0.3.zip You could also simply download & install the latest v1.0.0.3 https://github.com/gburton/Responsive-osCommerce/tree/1.0.0.3 and install it. You could make commit by commit changes 1.0.0.2 to 1.0.0.3: https://github.com/gburton/Responsive-osCommerce/pull/744/commits I suggest the simplest way is to grab the 1.0.0.3 zip, unzip it, and upload the files. Enjoy. Thank you to everyone who found bugs etc.
  10. 1 point
    the modal on the advanced search, the close X is before search help, i have only ever seen it on the right
  11. 1 point
    Rwe

    Phoenix, constructive feedback + bug hunting

    https://validator.w3.org/ Validate the page by URL or the pages that the validator cannot access ( checkout and account) you can use validate by direct input: source to textfield
  12. 1 point
    Rwe

    Phoenix, constructive feedback + bug hunting

    index.php?cPath=1 Duplicate attribute class. line 103 <select name="filter_id" onchange="this.form.submit()" class="form-control input-sm" class="form-control">
  13. 1 point
    Same error found in products_review_write as well. Thank You. Will be pushed in 1.0.0.3
  14. 1 point
    Rwe

    Phoenix, constructive feedback + bug hunting

    product_reviews.php?products_id=4 validating errors: <img src="images/apple-1.jpg" alt="Apples" title="Apples" width="100" height="80" class="img-fluid" hspace="5" vspace="5" /> The hspace attribute on the img element is obsolete
  15. 1 point
    burt

    Phoenix

    Bug Reporting, constructive feedback etc @ https://forums.oscommerce.com/topic/493648-phoenix-constructive-feedback-bug-hunting/ The more things that get brought to my attention as problematic, the better the core code can be. I have tried over the past weeks to catch as many bugs etc as I can across a number of threads, and those I was able to replicate I fixed. Those I was not able to replicate...I did not fix.
  16. 1 point
    Totally off topic I know but there is nothing stopping you, or anyone else, creating a package that makes changes to the core code to comply with country specific legal requirements. If everything was kept country specific it would make loading them and updating them easy as each countries requirements changed. A package that would alter things like address layouts, tax values, date and time formats, and all sorts of other changes would be a start to making the code international.
  17. 1 point
  18. 1 point
    Ok let me have a look and see if I can reproduce the error on my test site.
  19. 1 point
    No sorry I keep forgetting your using Frozen BS3 yours will be like this,
  20. 1 point
    Back to your problem, so it looks as if the path is missing the product id it should look like this, can you post yours the actual screen grab please as the way the path is directed is important.
  21. 1 point
    But you had that working before or am I just getting confused? Anyway using your browser hover over the product causing the problems and look in the bottom left corner of the browser window, it should show you the path the link is using and post it here. Will look somthing like this, just do a screen grab.
  22. 1 point
    I think we were not talking about the same thing posiably 😊 your posting in the Specials carousel with Ribbon v2.3.4.1 CE thread but I see from the ealier posts you also asked for a bit of custom code for sales ribbion on indexed products! Which are you actualy having problems with?
  23. 1 point
    I mean no disrespect - but gotta ask why waste your time (it is your time to waste)? It’s still won’t run without modification on newer versions of PHP and there is an available alternative already done that is being actively developed. It’s right here in the downloads page...just like everyone always wanted... sanctioned by HPDL. https://www.oscommerce.com/Products
  24. 1 point
    burt

    Phoenix

    I introduced a dumb copy/paste error, d'oh. Please update to 1.0.0.1 by performing; https://github.com/gburton/Responsive-osCommerce/commit/05b4d809ff2e87a9f46d76cd8699740c3d2c5389 https://github.com/gburton/Responsive-osCommerce/commit/13756ebb536d80f348bf1a7adcdbe4fb3c19377b Or in plain english: replace /admin/modules_content.php replace /includes/version.php I am going to try to keep on top of versioning going forwards so everyone knows exactly where they are. 1.0.0.1.zip
  25. 1 point
    burt

    Phoenix

    Vast majority of club members are those who supported Feb 2019 28d project. I'll come up with some other way to get club access for anyone who didn't feel able to support 28d.
×