I don't think a lot of the main core blocks are editable.  My system is the same...Things like category, customer, currency, etc...are system generated from data.  You can test this by creating your own block and see if you can edit that one.

I upgraded from 1.2.4 -> 1.2.5 manually and it looks ok, the include option above (not in the docs) seems to do the database delete/update stuff for people who are wondering.


All that said, similar to the other manual process in the docs of just copying files, should we just copy over the version.php over from the latest Abantecart zip file so it doesn't alert us that we still need to upgrade?  None of the docs show how to update that file (and one reason I was hesitant to do it manually in case I miss some stuff that's going on behind the scenes).


Lastly, if someone can answer, is it safe to assume that if I unzip the full install (abantecart_1.2.5.zip) and compare my live files to the files in this zip, as long as they are the same, I am good to go?


The auto package update thing hasn't worked well for me probably due to my changes and my hosting provider, but if this is pretty much key (matching the files up and just copying over version.php), then I will probably just do it this way moving forward...


Thanks for any clarification.

I am not part of admin or development staff (just a fellow user), but to upgrade to the latest version, you MUST upgrade by every point release.  This means to go from 1.2.2 to 1.2.5, you need to first go from 1.2.2 -> 1.2.3, then -> 1.2.4 then -> 1.2.5.

My advice has always been to setup a test environment first.  It is well worth the time and try your upgrade there first.  If you have made any changes at all to the system (which probably everyone has...), you will need to redo those changes.  My method is to just download the upgrade only package, then look through and compare all the new updated files with core and your existing files/changes...

After finding the differences, re-apply all those changes (it helps to have good documentation) again to the new updated files.

Depending on how much you have customized, you can decide if doing an upgrade is "easier" vs. just trying to export all the data and re-import to the new version.  (All that will depend on what skillsets you have and how comfortable you are with databases/abantecart/systems admin stuff).

Been hammering away trying to figure out what is causing the auto webUI upgrade to fail and I'm still stuck.  I'm wondering if anyone had any ideas to try or ran into this as well...I tried changing my various php.ini settings to

mysql.connect_timeout = 14400;
default_socket_timeout = 14400;

but it didn't seem to fix it.  I'm wondering if it's some other timeout problem causing the error or max_packets or something else as it does work occasionally.


What's strange is if I try again or blow away my test environment, restore, try again, it would generally work the 2nd time I try the webui upload install on my test environment pretty consistently so it's not failing all the time (NEVER WORKS ON THE 1ST TRY THOUGH).  When I tried it in production, it never worked however, even on multiple attempts.


It's throwing off this error:

tail -f error.txt
2016-01-29 15:20:59 - warning:  AbanteCart core v.1.2.4 Error while sending QUERY packet. PID=43628 in <b>/home/webdevmerc/tst/core/database/amysqli.php</b> on line <b>70</b>
2016-01-29 15:20:59 - database error:  AbanteCart core v.1.2.4 Error: <br />SELECT dataset_id
                                                                                  FROM abc_datasets
                                                                                  WHERE dataset_name = 'install_upgrade_history'
                                                                                                AND dataset_key='admin' LIMIT 1 in <b>/home/webdevmerc/tst/core/database/amysqli.php</b> on line <b>105</b>



I CAN run the above sql statement in the database in PhpMyAdmin and get:

SQL:
SELECT dataset_id
FROM abc_datasets
WHERE dataset_name = 'install_upgrade_history'
AND dataset_key = 'admin'
LIMIT 1

OUTPUT:
dataset_id
4


The structure of abc_datasets
#   Name      Type      Collation   Attributes   Null   Default   Extra   
1   dataset_id   int(11)                  No    None           AUTO_INCREMENT
2   dataset_name   varchar(255)   utf8_general_ci   No    None
3   dataset_key   varchar(255)   utf8_general_ci   Yes    

DATA of datasets
SELECT *
FROM `abc_datasets`
LIMIT 0 , 30

dataset_id    dataset_name          dataset_key
1       menu             storefront
2       menu             admin
3       menu             storefront_description
4       install_upgrade_history    admin
5       file_uploads          admin


I've considered changing all my database tables to use the ac_ prefix, but saw various unix files using the abc_ prefix so didn't go in that direction yet.

Hi WebDev - 

Check the prefix on your database -  it should be ac_

If you look at the sql update file,  the statements are for datasets ac_ 

I expect you know this,  but in case not,  you can use phpMyAdmin to easily change the prefix on your database

Let us know if this did the trick.

Lee

Hi Lee,

My database prefixes are all abc_ actually.  I think this was the default when you do a manual install.

The upgrade.sql individual script does point to using ac_, but I think the script automatically factors in databases using abc_ as running the exact same thing twice seems to work.  I don't know why though.

Also, using the auto network update worked as did when I did the select upgrade_only file going from 1.2.3 -> 1.2.4...

Is there a reason why the docs show abc_
http://docs.abantecart.com/pages/tips/change_domain.html

I think we discussed this maybe a year back, trying to find that old post...

I recommend AGAINST this personally...Assuming you use any real or even half hearted accounting program which takes into account your company/business (Quickbooks, etc...), and other various costs to run it, that would be a much much better solution to begin with.

Developing this at all would be a waste of developer resources when there are literally tons of paid/free solutions around already.  Those solutions can also take care of things way out of the scope of a single cart/web solution such as hiring people, other costs to acquire products to sell, Paypal fees, etc...

I am on 1.2.4...I tend to upgrade a little bit after the new version is released and still formulating the best way to do this quickly with my custom changes...

Manual upgrade doesn't work very good since the system doesn't recognize it when you have changed the files so I'd like the developers to make that work better (I might be the only one though who seems to want this)...

Thank you for all your time and helpful posts here.