I updated my OsCommerce shop to 2.3.3.4:
I replaced all files with the new default files from the package.
I Updated the old database with the script here: https://stackoverflow.com/a/19806818/1069083
Compared an sql-dump of the old database with the dump of an empty new database, It looked all OK.
Now the new version works with all products in it, but although I activated the "Categories" box in the admin interface it is not shown on the left.
Did I forget a Detail?
I found out why:
there are two different configure.php files, one is in
catalog/includes/configure.php
and one is in
catalog/admin/includes/configure.php
I didn't set the database to the new database in the admin config file, so all changes in admin didn't affect the real shop
Related
Django Admin change "history" logs
As you know Django Admin's sidebar shows a list of APP > MODELS. When you click on a MODEL, the focus area displays a list of RECORDS. Click on a RECORD, then the focus area shows a single RECORD as a form which you can change.
Here, in the upper right hand corner of the change form, is a gray pill-shaped button labeled "HISTORY" with entries like:
Dec. 9, 2021, 4:38 p.m. me Changed Table price headers.
Feb. 26, 2022, 2:06 p.m. me Changed Table date headers.
What I need is a copy of the record data before each change. Later, I need to query the Django database and--in this example--get the version of the record prior to the Feb 26 change.
How can Django Admin change "history" logs be used to also store copy of data?
Not for every Django Model
The rest of the Models & Records in Django Admin should behave normally. I only have a few Models where I need history log and data.
Not to be confused with model history
When discussing this with other Django developers I have to explain the history I need is for the record's data, and not the model. There is a third-party Django packages which does the other thing which I don't need.
Why do I need this?
In my Django site I run a script which requires settings. I'm querying a non-Django-related MongoDB database where I keep a copy of reports generated by several third-party vendors. To help me manage and utilize this data I need a record of each report's headers or schema.
There is a tight coupling between the data I'm storing in Mongo and the data's schema. For this reason I'm storing these headers as "settings" in Django's database. It's been really convient for me to use the Django Administration page to update these schema settings.
However, once in a blue moon a third-party will rename a header or add a new column to their report. When this happens I have to update the settings record in the Django Admin. Currently I don't have access to the historical schemas in my Django project, and have to write custom scripts to access historical data.
My wish is store each version of these records, so I can check the settings change history log. When the requested records needs a historical schema, I can then query the Django database to recall the valid headers for the date range.
Have you tried django-simple-history? Works fine for me.
I developed a new cms using django and wagtail.
News website that I developed the CMS for, used to use a php cms storing data in a messy and not normalized mysql database.
So now, I have to store all old database records in my new django app's database.
As the links to news in old cms were generated based on their ID and obviously the old links should keep pointing to the corresponding content, I have to keep IDs as well as other fields.
Right now I am confused about what approach should I take in order to do the job.
Basic idea is to use inspectdb generating a new model for records in old database, then write a script to fetch each object from old db, use it to generate an object of newly developed models and save the object in new database.
What more efficient approaches can I take?
I worked on a project with the same problem.
Inspectdb worked well but I had to do a lot of cleaning on the modelos.py. You will also have to work out ManytoMany relationships if your database has any.
I have a simple ocmod.xml for my opencart 2.3 application.
I've uploaded the changes but now I need to modify it.
Instead of reinstalling the new version, how can I quickly modify it and refresh modification during development?
Where is the file located?
If you uploaded the file via the admin end then it will be stored in your MySQL database. Under modifications table in the database and the xml row in the table you will see it. If you edit it there then clear and refresh the modifications you will see the changes.
You can also do it we try a new miss called an ocmod manager. This all is you to edit from admin for opencart 2x or for opencart 3x
I'm totally new to Mezzanine CMS. I got handed a site to work with and so far I've been able to do all the changes without problem. I've run across a problem in which they want a new section in the home page. I go to the admin section to edit the home page, but there is no extra content field.
On the home page, I see 4 sections "content" "priorities" "testimonials" and "clients". I would like to have another "content" area as a 5th section. How do I go on and add this section? I'm totally new to Django but would be appreciative if someone could explain or point in the right direction.
Here is a link to an image for reference.
https://imgur.com/a/sUKOtvS
Thanks in advance
The homepage content would be backed by a Django model with attributes for the partners and testimonial fields. You'll need to find the Python class for this model in your code base (you could search for those field names), and you'll need to add a new attribute for the new section you need.
Django and Mezzanine have lots of different field types you can use for these attributes, so consult their respective documentation for how those work (Django's are a lot more comprehensive, so start there).
Once you've done that, you'll need to create a database migration for the new attribute - that adds the field to the database table that will store the actual content, again consult the Django documentation for how these work.
Finally you may need to add the new field to the Admin class, which is the Python class (similar to the model) that controls which fields appear in the admin interface, and how they appear. I say "may" as these generally appear automatically without any code, but if things have been modified to a certain extent, you may need to do this manually.
I have OpenCart 1.5.6.4 installed on a server, and I have imported a database with over 64,000 products. They are all being displayed on the admin pannel, I can edit them, but on the front there apper to be none. If I add a new product it will be displayed. I have already checked the database an all the values of the new products are similar to the old one but. I have also changed the theme. Nothing happend
So they are displayed on the admin pannel, but not on the front, what am I missing?
Check your product_to_store table. If it's empty, you just need to write a small script to add the product IDs to the correct store (usually ID 0)