Messages

Okay for the record I find it pretty uncool the lack of responses..

This is kind of important guys..  Thoughts?

So your question implies to me that you have done very little with git before.. It would likely pay you dividends if you were to do some reading about how git works and maybe some general work flow concepts..

I realize that it's a little scary but I think (and in my experience) in the long term if you embrace this you'll really appreciate how it works.. you get a lot of stuff for free and it only serves to improve your end product..  Even php is entirely in github =)

With the typical work flow of any open source product, only direct team members can push directly to the repo or accept pull requests.   (it's a setting in github)..   Everyone else can fork the work or issue pull requests back to your repo, but they don't have access to modify files without your permission.  They can't push directly into your repo, but rather have to issue a pull request that must be approved first.

So for example;

I find a bug..  I fork or clone your repo and fix the bug..  I then issue a pull request back to your repo.. 

You guys have a look at the code submitted by me in the pull request and make sure it conforms to coding standards, solves the problem at hand and doesn't inject malicious code or cause other headaches..etc..  You can either accept the pull or reject it..  If you accept it gets merged into the repo just as if you pushed a fix yourself.. 

If you reject it you can add a note to the rejection as to why the pull isn't up to snuff.. And that can be anything from "I don't like you" to "we are fixing this differently".. to nothing at all.. though its generally polite to say why a pull got rejected.

If you go one step further you can put all of your issue back log into github that users can browser and submit fixes for directly.. so I can say "This pull request fixes issue #1234" and you can then see exactly what it fixes and close the ticket too..

An added bonus is that every time you tag a repo to a version number github automatically creates a zip archive at that very moment of the latest branch on master that you can link to on your website.. no longer do you have to host and manage zips or tgz's but github does it for you..

For now would I would probably do if I were in your shoes is to create a master branch with the core code.. create a development branch that you do all your pushing to and test on.. when its "ready" tag it and merge that into your master..  master is the code on the website for download..  The develop branch is the ongoing unstable branch..

Then you create feature branches for any new features you want and merge those back into develop as they get done..

Bugs are either fixed directly in the development branch or in a hotfix branch that gets pushed to master directly.. but lets not get too confusing yet =)

Unlike svn everything in git is a branch and branches are good..  (unlike svn in which branches and merging can suck..)


Either way you should likely try forking a big open source product and then get a buddy to create an account and have them issue a pull request that changes the "hello world" to your product and see how it works..   its all free and it's worth your effort to learn how this works.  This work flow is very important and will make you more comfortable with this process.. 

When attempting to use either the SOURCE or the shell method of db update as provided here;
http://www.mysqlfaqs.net/mysql-faqs/Client-Server-Commands/How-to-run-SQL-script-files-in-mysql-client

the update sql script fails at both the --server line and the set @block_id line.

ERROR 1064 (42000): You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '--server
('server', 'config_upload_max_size', '16000'),
('server', 'config_store' at line 2
Query OK, 1 row affected (0.00 sec)

ERROR 1064 (42000): You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '' at line 1
ERROR 1064 (42000): You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '@block_id' at line 1

~$ mysql --version
mysql  Ver 14.14 Distrib 5.1.41, for debian-linux-gnu (x86_64) using readline 6.1

Is there a list of all the features and bugfixes that got addressed from 0.92 to 1.0 please.

You should keep a running list of information like this.

When you're entering the height, width, length and weight for a product should you enter the actual size, or the shipping box size?

Is the purpose here to give better stats to the user about the product, or the final boxed size that the various shipping modules can use to determine cost of freight?

Thanks

Create a product and give it a tag "test tag".  Now visit that products page and click the "test tag" tag, the search results return nothing because space gets turned into %20 in the URL which doesn't get url decoded back for the query..

I imagine other special characters would also fail.  Tags should be stripped of all special characters except only those legal as a tag in a url .

Again this is something I could have fixed for you if there was a git repo.. 

So is it safe for me to enter a bunch of real data into Abante?

I'm wondering if data migration from one version to the next can be assured at this point?

When listing products on the admin products page, I'd really like to be able to see the SKU.. 

To that end I'd suggest to create a way to make the visible columns editable by admin..

(Or, if you open up the source via git community developers can work on that for you =)

It's less about the hosts and more about the databases they support..

If your hosts MySQL has the InnoDB (or BDB) engine then you have transaction support.. if you only have MyISAM as the db backend for your mysql install,  then you don't. 

It looks like right now AbanteCart installs by default as MyISAM which means no transactions.. (or foreign keys)

Ah ha!  Makes perfect sense.. a salt system.. good idea..

So what are the chances of getting a GIT repository so that developers like myself can help contribute?

The nice thing about git is that we can create feature branches, do something we think would be handy and then issue a pull request when we have it working.. you can then choose to merge it into the code base or not.  Most likely a lot of folks would end up committing code to the project this way  and so long as you make it clear that all code committed in this manner must be clean, dry and easy to understand it ends up being a win win for everyone..

Sweet!

Yeah I don't know that it has a lot of practical use.. but if you think of all the possible ways this system can be used like maybe for show tickets, or maybe holiday items that you only want to show certain times of the year..etc..

Could be a nice thing to have and should be fairly trivial to add all things considered..

Howdy!

I'd like to see it as an option in the latest products maybe with some weighting mechanic or at the very least in a category view.

Right now the category view has a sort drop down with a number of options.. it would be trivial to add the random option.. ( I already did it on mine to see if I could.. )