New 
Mark Evans
-
Posts
2,466 -
Joined
-
Last visited
-
Days Won
5
Posts posted by Mark Evans
-
-
1. Most usage.
2.x
2. Expand to support next release of osCommerce easily.
3.x
-
The roadmap can be seen at http://countdown.oscommerce.com/index.php?article=roadmap
In short, there is a lot of work to do on 3.0 and it will take a while, if your a developer then why not help out
-
Whatever happened to backwards compatibility?
There was no way we could be backwards compatible and move the codebase forward enough to be a good base for the future. As I've said a few times recently, if your not a developer don't use v3.x for now, 2.3 is a supported released and will receive more updates to keep the general userbase busy.
If you really want v3.x then you pay a little more per month and get a VPS, there are 1000's of companies offering them which will give you PHP 5.3.
Supporting every shared hosting company out there will do nothing but hold everyone back
-
I have taken today off work to spend time installing and assessing V3, will it be released today or should i go to work and re-book the time out for next week?
If your that desperate to take a look just download it from https://github.com/osCommerce/oscommerce there is no need to wait
-
90% of those webhosting companies would be resellers of the very few "real" hosting companies. So the conclusion is not quite as dramatic as it could be.
Yep totally agree, if you also add VPS / Cloud / Dedicated servers into the mix you are into 1000's of hosting companies as well so I think people jumping up and down saying its wrong to have PHP 5.3 as a minimum requirement are just spreading pointless FUD.
2.3 is also a supported release and will be getting some updates soon to fix some of the known bugs so people have a real choice, stick with the 2.3 series which while its a pain to modify and upgrade will run just about anywhere, or use 3.x which is a little more strict but will be what the future is built on.
-
-
There have been FIVE (5) identified hosting providers that will support PHP 5.3. 99% of current users more than likely aren't hosted with them.
There are now 9 and thats just the shared packages
, I can probably make that into the 100's if we included VPS / Dedicated servers.To make a long story short, 3.x is in it for the long haul, its not ready to be used by people that don't know what they are doing and I think thats a good thing. We should all stop looking for the new shiny thing and lets give it time to bed down and stabalise, get other developers trained up and get the community addons and contributions to core rolling in. This will all benefit the codebase and the userbase considerably for the future and was one of the core goals of the 3.x series.
Its "cup 1/2 full" time and not "cup 1/2 empty"
- Pronux, Hotclutch and dannyhenderson
-
3
-
Wordpress does it well. Of course, wordpress is a simple system for writing blogs and not a fullblown ecomm system. But it might give a way forward.
Wordpress is a good example of how a modular approach can be implemented, there are also quite a few other open-source solutions which have tackled the same problem in different ways, I intend to look into a number of different solutions to this and hopefully what we can get out of it is something which will stand us in good stead for years to come.
-
I just have a layman's view of this, but it's hard to imagine every module can be installed without changing the core code. The simple reason is that, some modules change the functionality of the core.
It will be possible to change even core functionality without changing core code.
When a module is created, it should be written with all other modules already installed. This will lay the responsibility on the developer to consider added features of the current base of modules. Complication arises when the instantiated version number of osCommerce changes before a module is completed (more experienced members might have easy solutions to this).
With over 6000 contributions currently available this is not a viable solution in any sense of the word.
The osCommerce team will ensure that the functionality in core continues to work at all times but we will not be testing every single addon, that is the responsibility of the addon developers themselves.
-
With the development of the 3.x series we will be moving towards an approach where modules can be installed and changes to osCommerce made without the need to edit core code which is the problem with the 2.x series.
This will handle the installation of modules and the removal of modules.
I am not sure when this will be ready but hopefully we can start on this soon.
If anyone has any thoughts on how this process should work or how modules could be implemented I am of course interested to hear idea's.
-
-
My own personal opinion is that 3.x will be released when its ready rather than by an arbitrary deadline.
That said I am hoping we can have a roadmap ready soon to give people an idea of just whats left to do before a 3.x release can be made.
There is also very likely to be another 2.3.x release soon once I have had time to catch up and fix the current list of open bugs, once that is done I will also start to focus more on the 3.x release along with Harald who is already working hard on it.
As I have said many times before, as soon as we are close to a release I am pretty sure we are going to shout about it from the tree-tops. I would hazard a guess that we want to get the 3.x series out in the wild as much as you all do... if not maybe a little bit more
That being said, I don't plan on answering every single one of the "When is 3.x going to be released" threads which are already springing up and no doubt there will be more. I would rather spend my time bug fixing and coding new functionality. So if you don't get any replies from me don't think its because I am ignoring you, its because I am working to get it right.
I will also be blogging on some osCommerce related topics very soon which should give you all an idea of where we are with things.
-
-
v2 and v3 are completely different codebases so the issues will be different.
Rest assured though we don't knowingly ship software with security issues :thumbsup:
-
I've never had this issue before and have used a pretty wide range of hosting companies so I suspect there is something specific in the php configuration on the servers where this problem is found.
It would be interesting to take a look into the PHP config of people who have had this issue to see if there is something which is common across them all
-
Is the new osC 3 Framework based on an established PHP Framwork, like symphony or zend?
No
Is the new Frameworks design pattern based. Does it feature MVC or ORM table behaviors?
Partially, the code is very much in development and improvements are happening all the time.
Also I hope the new Framework will be completely object oriented and has an intuitive and consistent API?
Its as OO as it needs to be, the API is in development and will be fully documented and as consistent as possible.
One last question. Does the new Framework supports PDO for multi database connection?
The DB layer is in development and more details will emerge as the coding is in progress.
Information on the architecture of the 3.x series will be posted in blogs soon so people get a good idea of where things are going. I am pretty excited about the use of namespaces and some of the cool things PHP 5.3 allows us to do so be prepared for something amazing. ;)
And before anyone asks, no there isn't a timeline of when it will be ready :thumbsup:
-
I would think we would try to provide a database upgrade path but I won't promise that will be the case, we still need to get 3.x into a shape we are happy with and that could require more changes to the database that we don't know about yet.
As we get closer to the 3.x stabilisation we can look into this more closely.
-
With 3.x as long as the contributions follow coding standards there is no need for a special autoloader, we are working out the details at the moment and as soon as we have a concrete implementation we will be sure to blog about it.
For now making anything for the alpha5 codebase is pointless.
-
I don't know of any implementation of this into the authorize.net module provided by osCommerce.
From what I can tell these changes are quite significant in the way the authorize.net module works and will require changes to the core of osCommerce to support, if someone from the community can take a look into what changes are required and knocking up a patch / addon I am sure it would be appreciated by the rest of the community.
-
An osCommerce team does not exist
. Nice to Know thanks :-"
-
The more wide a range platforms we can get testing completed on the better, also with different versions of PHP 5.2.x and 5.3.x especially.
-
Hi Nicolas
The roadmap is very much in flux at the moment whilst we work on core stability and flexibility.
If you are keen to get started I would suggest setting an account up at github and getting your own copy of the codebase, then giving the 2.2 branch of github a really good test on as many platforms as possible.
There are also a number of outstanding issues in the issue tracker http://svn.oscommerce.com/jira/secure/IssueNavigator.jspa?reset=true&pid=10000&resolution=-1&fixfor=-1 so you could take a look to see if you can find fixes for them and commit to githib so that they can be easily merged into the core codebase.
-
This has been asked a number of times, for more details see
http://www.oscommerce.com/forums/topic/352279-new-version-of-osc2/page__view__findpost__p__1475741
Rest assured that we are working on it and as soon as we have more firm details we will announce them. Right now though the focus is on coding.
Locking this thread since this subject is always sure to entice the trolls. Feel free to contact me via PM if you have constructive feedback / comments.
-
Since I don't know anything about the Linkpoint API I can only provide general suggestions, if this is out of your field of knowledge then you really need someone who can look into this by accessing your test store and debugging the response to find out why its coming back different to what is expected. It could be down to a change in the API itself or just lousy code.
Taking a quick scan there seems to be a debugging option in the module, did you try to activate that and see what the response comes back as?
What your looking for is the absence of a field called r_avs if thats not in the debugging email then AVS isn't being used (I am guessing), maybe its an option in the control panel for the merchant account?
TBH looking at the code for the module it seems pretty messy so if your coder is unable to do the debugging then I would suggest you find a more competent coder who won't leave you in the lurch with a half finished store.
Which osCommerce version is suggested for a new develop web api service? Thanks!
in Add-Ons Development
Posted
I'd use 2.3.3 as the base, 2.4 will be on the way soon but will be pretty similar in terms of functionality, I would then suggest keeping an eye on the 3.x development as once we get closer to stabilising the core codebase we will look to prepare a full functionality release which will be radically different to the 2.x series