Jump to content

Archived

This topic is now archived and is closed to further replies.

Fusion616

OSCommerce appears to be totally outdated

Recommended Posts

Antonio, all very good points raised, thank you. Our website will be updated to address some of those points.

 

I would like to take this opportunity and also ask you directly, and those reading this, if you would be interested in helping us with the points you have raised?

 

Something that non-programmers and actual store owners can help out with is with documentation. There are over 1,000 topics in the v2.x Tips and Tricks forum channel that would be ideal to be placed into a knowledge base / wiki, specifically our documentation library site at http://library.oscommerce.com. Our documentation site links to old PDF documents that need to be updated and placed into the library site.

 

I am sure the team would welcome a new addition to help lead this effort.


:heart:, osCommerce

Share this post


Link to post
Share on other sites

Can I add a plea for a page listing all official patches to the latest release with links to the relevant github page or a link to a download that includes these patches.

 

Maybe even an email to all members of the forum when a core fix is released if they request the service.

 

If a new OSC user arrives at the site and downloads the "Latest" version what they actually get is a known out of date version and nowhere pointing out they ought to update their code to cure known faults.

 

Does the 2.3.3 package on the downloads page include all the patches, the last one I down loaded did not.

 

Maybe have a 2.3.4 vanlla download and another with all the patches applied 2.3.4.1 latest

 

It may be yet another job to do but the fault was thought serious enough to correct.

 

Cheers

 

G


Need help installing add ons/contributions, cleaning a hacked site or a bespoke development, check my profile

 

Virus Threat Scanner

My Contributions

Basic install answers.

Click here for Contributions / Add Ons.

UK your site.

Site Move.

Basic design info.

 

For links mentioned in old answers that are no longer here follow this link Useful Threads.

 

If this post was useful, click the Like This button over there ======>>>>>.

Share this post


Link to post
Share on other sites

Geoffrey, I don't understand what you mean. The latest v2.x releases available for download are stable and production ready releases ready to install and use.

 

We will definitely not link to "patches" for code updates pending the next release version, as until the next version is released, the changes are considered in-development and still in testing.

 

When the next version is released, we spend a lot of time and love producing release notes that specifically point out what code changes have been performed. This is included as a PDF documentation in the update download packages and also online at our library site.


:heart:, osCommerce

Share this post


Link to post
Share on other sites

 

Something that non-programmers and actual store owners can help out with is with documentation. There are over 1,000 topics in the v2.x Tips and Tricks forum channel that would be ideal to be placed into a knowledge base / wiki, specifically our documentation library site at http://library.oscommerce.com. Our documentation site links to old PDF documents that need to be updated and placed into the library site.

 

I am sure the team would welcome a new addition to help lead this effort.

 

I understand the general concept of the documentation. It's helpful, for for example the documentation you posted about PP Express V3 helps the user understand better what's happening, especially if the user is not a master of coding.

 

What exactly is needed/expected of those that might want to help with documentation? What format is it done in? Is special software needed? Is there a template to use? Is collaboration part of the scheme if a project is very large? Who reviews and vets the documentation? Who posts the documentation.


I am not a professional webmaster or PHP coder by background or training but I will try to help as best I can.

I remember what it was like when I first started with osC. It can be overwhelming.

However, I strongly recommend considering hiring a professional for extensive site modifications, site cleaning, etc.

There are several good pros here on osCommerce. Look around, you'll figure out who they are.

Share this post


Link to post
Share on other sites

What exactly is needed/expected of those that might want to help with documentation? What format is it done in? Is special software needed? Is there a template to use? Is collaboration part of the scheme if a project is very large? Who reviews and vets the documentation? Who posts the documentation.

 

Our documentation is written in HTML with custom template codes. It is versioned on Github so changes can be tracked, and is served through our website running on OSCOM 3.0.

 

The source code for our library site is available at:

 

https://github.com/haraldpdl/website_library

 

The documentation is located in this directory:

 

https://github.com/haraldpdl/website_library/tree/master/public/sites/Library/Asset

 

There is a small learning curve in setting it up and I have written some how-to documentation which I will get ready and push out.

 

The table of contents shown on a page is automatically generated through <hX> header tags, where the structure is:

 

* Only one <h1> tag can exist on a page and it must be the first

* Subsequent <hX> must be done in order, eg, h2, h3, h4, and back to h2 for the next major heading

* <hX> heading tags are used for structure, not for design layout

 

If you want to start writing right now, by all means start and it can be formatted properly and pushed out to Github as soon as the how-to guide is ready.


:heart:, osCommerce

Share this post


Link to post
Share on other sites

Developers can also publish documentation regarding their Add-Ons on our Library site. This is managed by git submodules and versioned on the developers own git repository.

 

Two examples are here:

 

https://github.com/haraldpdl/website_library/tree/master/public/sites/Library/Asset/Package/Content/en


:heart:, osCommerce

Share this post


Link to post
Share on other sites

Antonio, all very good points raised, thank you. Our website will be updated to address some of those points.

 

I would like to take this opportunity and also ask you directly, and those reading this, if you would be interested in helping us with the points you have raised?

 

Something that non-programmers and actual store owners can help out with is with documentation. There are over 1,000 topics in the v2.x Tips and Tricks forum channel that would be ideal to be placed into a knowledge base / wiki, specifically our documentation library site at http://library.oscommerce.com. Our documentation site links to old PDF documents that need to be updated and placed into the library site.

 

I am sure the team would welcome a new addition to help lead this effort.

 

Harald:

 

OF COURSE, we will try to collaborate in all you need. also for LANGUAGE support (Spanish, in my case). The language support is, in my oppinion, a important feature lost in the past years and I think is important to have a beautifull and prominent button with donwload osc and then a dropdown menu link with the available 'languages packs'.

 

Also I can help in the translation of the documentacion if need.

 

I suggest you a kind of gifhub where each languagje may be put there. In the readme file you reming that 'you can download this pack clicking in the zip button, bla, bla, bla'.


Get the latest current code (community-supported responsive 2.3.4.1BS Edge) here

No pierdas el tiempo. Si quieres usar la versión más estable de osCommerce (la realizada por la comunidad, que además es 'responsive', la 2.3.4.1BS Edge) pincha aquí y aquí para descargarte el idioma Español.

Share this post


Link to post
Share on other sites

Can I add a plea for a page listing all official patches to the latest release with links to the relevant github page or a link to a download that includes these patches.

 

Maybe even an email to all members of the forum when a core fix is released if they request the service.

 

If a new OSC user arrives at the site and downloads the "Latest" version what they actually get is a known out of date version and nowhere pointing out they ought to update their code to cure known faults.

 

Does the 2.3.3 package on the downloads page include all the patches, the last one I down loaded did not.

 

Maybe have a 2.3.4 vanlla download and another with all the patches applied 2.3.4.1 latest

 

It may be yet another job to do but the fault was thought serious enough to correct.

 

Cheers

 

G

 

Yea!

 

The 2.3 users (I think) can easy kept informed because the admin widget that inform about the news about osc. May be it should be a good idea to make another widget with the updates/patches/security changes with the link of the proper place to read/donwload.

 

Poor users as me, in the 2.2 world, should need a contribution that warms us of these interesting events. I will try to code something... :wub:


Get the latest current code (community-supported responsive 2.3.4.1BS Edge) here

No pierdas el tiempo. Si quieres usar la versión más estable de osCommerce (la realizada por la comunidad, que además es 'responsive', la 2.3.4.1BS Edge) pincha aquí y aquí para descargarte el idioma Español.

Share this post


Link to post
Share on other sites

html files are not good to try a collaborative work, as you must download the files to read it and edited in a html editor, right?. (may be there are a easy way to read it, but in this moment I don't know it).

 

I'm not a githup ninja, so I don't know that should be the best type of file to manage a collaborative TEXT (not code) versioning.

 

What about penflip? Not reading all the capabilities / limitations. Only found this article:

 

http://madebyloren.com/github-for-writers

 

Easy for all (developpers and users that request changes/improvements). Only write as far your fingers does!!! :lol:


Get the latest current code (community-supported responsive 2.3.4.1BS Edge) here

No pierdas el tiempo. Si quieres usar la versión más estable de osCommerce (la realizada por la comunidad, que además es 'responsive', la 2.3.4.1BS Edge) pincha aquí y aquí para descargarte el idioma Español.

Share this post


Link to post
Share on other sites

Does the 2.3.3 package on the downloads page include all the patches, the last one I down loaded did not.

 

2.3.3.1, 2.3.3.2, 2.3.3.3, 2.3.3.4 were all releases that included some patches and some functionality as an addendum to 2.3.3


Help shape the future of Phoenix; join the Phoenix Club

Share this post


Link to post
Share on other sites

Geoffrey, I don't understand what you mean. The latest v2.x releases available for download are stable and production ready releases ready to install and use.

 

We will definitely not link to "patches" for code updates pending the next release version, as until the next version is released, the changes are considered in-development and still in testing.

 

When the next version is released, we spend a lot of time and love producing release notes that specifically point out what code changes have been performed. This is included as a PDF documentation in the update download packages and also online at our library site.

 

It is not the code updates pending the next release but bug fixes such as if the PP module stops working.

 

As an example, a new user downloads the latest version and out of the box the PP module does not work but on the master branch on github a patch has already been posted.

 

How would a new user of OSC get to find out about the patch?

 

The point I am trying to make is that the average user of osc doesn't know where these fixes or the "in-development changes" are or how to find them.

 

Thus they are in no position to make an informed decision as to whether they should apply them to their copy of OSC.

 

So they bimble along with a shop that is not working correctly when developers and others that read the forum, know there is a fix and where to find it.

 

Github is great for developers but incomprehensible to shop owners (no insult to shop owners intended).

 

So if something is serious enough to warrent a fix to the core system why not have a clear link to the change on github clearly available on the web site not hidden away on the forum?

 

Hope that clarifies what I meant.

 

Cheers

 

G


Need help installing add ons/contributions, cleaning a hacked site or a bespoke development, check my profile

 

Virus Threat Scanner

My Contributions

Basic install answers.

Click here for Contributions / Add Ons.

UK your site.

Site Move.

Basic design info.

 

For links mentioned in old answers that are no longer here follow this link Useful Threads.

 

If this post was useful, click the Like This button over there ======>>>>>.

Share this post


Link to post
Share on other sites

Hi Geoffrey..

 

We are in the process of pushing out regular releases and to keep the modules in sync with their Add-On packages. If we need to push out a bug fix for an Add-On that is bundled with our releases, we will also push out a point core release including the fix.

 

Kind regards,


:heart:, osCommerce

Share this post


Link to post
Share on other sites

2.3.3.1, 2.3.3.2, 2.3.3.3, 2.3.3.4 were all releases that included some patches and some functionality as an addendum to 2.3.3

 

I previously mentioned that all v2.3.3.x changes would be included in the v2.3.4 upgrade guide. This is no longer the case - as mentioned in the v2.3.4 upgrade guide, the release is based on v2.3.3.4 (not v2.3.3) so upgrading from v2.3.3 requires you to go through the v2.3.3.x upgrade guides.

 

This was to avoid having duplicate content in the v2.3.4 upgrade guide which would not have been of interest to up-to-date users. This way there is a clearer distinction of changes to apply, which of course can be applied at your own leisure.


:heart:, osCommerce

Share this post


Link to post
Share on other sites

Have been reading this thread with interest. Thought I'd add my tuppence as a shop owner- hopefully I won't ramble too much, but there's a few things I wanted to comment on.

 

Improving the basic Oscommerce package

 

I like the fact that OScommerce is customisable, both frontend and backend. However I do think the basic package could still do with a bit more improving.

I upgraded from RCa2 to 2.3.3 last year, and was very happy that several add-ons from my old site were included in 2.3.3, so that I didn't have to reinstall them (multiple images, Ultimate SEO, etc) but there's still some functions I'd consider 'core'. I don't necessarily agree with every addon listed by other shopowners here, but there is certainly overlap between us ,eg, stock control for multiple attributes (OTPro is a ballache to install, and ALWAYS causes problems with another addon), responsive design ( My stats across all the platforms I sell on show a continuing increase in use of mobiles and tablets, so I'm hoping the new Bootstrap stuff gets added in, so I can use that instead of the bloated template I currently have).

 

I do like the modular add-ons that are now available via the admin in the newer versions of OScommerce. I suppose we could look at add-ons at two levels- 'Essentials' that are modules that are provided with the basic package, and can be implemented via Admin, and then 'Additionals', which can be more specialist, and can be downloaded and added in the usual way?

 

Why don't shopowners update their shops to the latest version?

 

Similar to what others have said- For me it's time-consuming because of all the add-ons. For some shop owners it might be a case of not knowing how to do it, or simply not caring. Less of a problem for bigger businesses that can afford to pay someone to do it, but for the tiddlers in the pond like me, I prefer to save my cash for paying for oscommerce stuff I know I can't do at all.

 

 

It's a difficult balancing act for OSC for the future. As well as meeting the evolving demands of online shopping and other cart competitors, there's also many more selling platforms for businesses (Shopify, Wix, Weebly, etc). My experience with other micro/small business owners is that many either don't have a clue as to how to set up their own online store, or are too busy with their businesses, so will often prefer anything that is easy and relatively simple to set up. Does that mean they make the best choices for their business? Possibly not, but that's what I'm seeing.

 

I can't really comment on the developer side of this issue- I don't have a clue as to how best to implement this, and avoid OSC being piled up with so much stuff that it performs like some sort of arthritic Buckaroo.

 

Making it worthwhile for the developers who spend so much time on improving OSC? I wouldn't mind a sliding scale of monthly fees, much like I pay for my webhosting. Is that workable?

Share this post


Link to post
Share on other sites

Hi all,

 

I am proud to be here since so many years.

 

Just my 2 cents:

I am wondering, why the 2.3.. does not contain

SPPC

Hide products from customer groups for SPPC

Quantity Price Breaks for SPPC

 

It would be helpful, to have this functionality out of the box!

 

kind regards

Götz

Share this post


Link to post
Share on other sites

@@texmaxx

 

Easy answer:

1. SPPC is not coded to the standard expected of something in the Core

2. A (relatively) small percentage of shops would need it

 

In future versions of osc, you will find things added to the core, but these things will be;

a. coded in a consistent manner to how osc is coded

b. used by at least 90% of all shops (typical example: seo, needed by all shops).


Help shape the future of Phoenix; join the Phoenix Club

Share this post


Link to post
Share on other sites

@@texmaxx

 

Hi Gotz,

 

Can you imagine how confusing it would be for a new shop owner to have the options you mention when they are selling flowers :D

that is the strength of osCommerce not a weakness!!

 

It try's to cater for everybody with a base to build on to optimize for specific needs

 

regards

Joli


To improve is to change; to be perfect is to change often.

 

Share this post


Link to post
Share on other sites

Easy answer:

1. SPPC is not coded to the standard expected of something in the Core

2. A (relatively) small percentage of shops would need it

 

In future versions of osc, you will find things added to the core, but these things will be;

a. coded in a consistent manner to how osc is coded

b. used by at least 90% of all shops (typical example: seo, needed by all shops).

1. Exactly! if integrated, it would be.

2. Wondering why 30% of my customers use it...

 

It shows already in the addons section, that developers are going to give up to follow the 2.3..

Share this post


Link to post
Share on other sites

Gotz what on earth are you talking about :P

 

with the help of that old mama noodles and a few others it is a perfect package  sppc

 

if  30% of your customers are  wholesale/retail  that is very specific to your business model most shops 99% are retail i would guess

 

"It shows already in the addons section, that developers are going to give up to follow the 2.3.."

 

most of us guys here are thinking about retiring

 

 after 2.3 but before 3.0  if that old ghost of rc2/ms2 is still spooking you there is a help desk sure somebody will have the link if not call ghost buster!!

 

Regards

Joli


To improve is to change; to be perfect is to change often.

 

Share this post


Link to post
Share on other sites

oscommerce have its share of shop owners using old versions, but so does many of the newer carts even though easy core version update is available.

Why are they not updating?

Share this post


Link to post
Share on other sites

×