https://www.cremecrm.com/forum/ Thu, 14 May 2026 12:16:18 +0000 MyBB https://www.cremecrm.com/forum/showthread.php?tid=286 Tue, 07 Apr 2026 14:20:17 +0200 genglert]]> https://www.cremecrm.com/forum/showthread.php?tid=286 th 2026 the version 2.8 of CrèmeCRM has been released, 7 months after Creme 2.7 (Septembre 2nd 2025).

It's a relatively smaller version as usual, in order to be better synchronised with Django releases, and so avoiding period when Creme is supported but the underlying version of Django is not supported anymore.

We a have prioritized small and middle features, but we managed to implement a lot of.

On technical side, Python 3.14 is now officially supported.

On user side, major changes are:
- Many improvements on credentials have be made:
  - users can have several roles (details).
  - roles can be disabled.
  - roles manage now the types of entity which you are allowed to list, and 2 special permissions can be set: users management & roles management (you had to be superuser before).
- You can now pin your favorite entities  (details). The way the last viewed entities has been improved too.
- The HTML text editor (used for the HTML body of emails for example) has been upgraded; it's used in more places.
- Some columns of list-view display now some results computed on all entities of the list:
  - the sum and the average of totals (with & without VAT) of Invoices/Quotes/Credit notes/Sales Orders.
  - the sum and the average of estimated & made sales of Opportunities.
- You can now download several Documents, Invoices or Quotes as one '.zip' archive (details).
- The custom fields can now have a description and a default value (details).

Hope you'll enjoy this release!]]> th 2026 the version 2.8 of CrèmeCRM has been released, 7 months after Creme 2.7 (Septembre 2nd 2025).

It's a relatively smaller version as usual, in order to be better synchronised with Django releases, and so avoiding period when Creme is supported but the underlying version of Django is not supported anymore.

We a have prioritized small and middle features, but we managed to implement a lot of.

On technical side, Python 3.14 is now officially supported.

On user side, major changes are:
- Many improvements on credentials have be made:
  - users can have several roles (details).
  - roles can be disabled.
  - roles manage now the types of entity which you are allowed to list, and 2 special permissions can be set: users management & roles management (you had to be superuser before).
- You can now pin your favorite entities  (details). The way the last viewed entities has been improved too.
- The HTML text editor (used for the HTML body of emails for example) has been upgraded; it's used in more places.
- Some columns of list-view display now some results computed on all entities of the list:
  - the sum and the average of totals (with & without VAT) of Invoices/Quotes/Credit notes/Sales Orders.
  - the sum and the average of estimated & made sales of Opportunities.
- You can now download several Documents, Invoices or Quotes as one '.zip' archive (details).
- The custom fields can now have a description and a default value (details).

Hope you'll enjoy this release!]]> https://www.cremecrm.com/forum/showthread.php?tid=285 Tue, 07 Apr 2026 14:11:20 +0200 genglert]]> https://www.cremecrm.com/forum/showthread.php?tid=285  - they can get a description; if it's filled, it's used in forms as help text in the corresponding field.
 - they can get a default value; if it's filled, it's used in creation forms as initial value in the corresponding field.

The configuration of custom fields has slightly changed in order to get these new features. The form to create a new custom field is now a wizard with 2 steps. In the first one, the description has appeared :



In the second step, you can define a default value (excepted for fields with type "choices" et "multiple choices"):



The form for the related type of entity will look like:

]]>  - they can get a description; if it's filled, it's used in forms as help text in the corresponding field.
 - they can get a default value; if it's filled, it's used in creation forms as initial value in the corresponding field.

The configuration of custom fields has slightly changed in order to get these new features. The form to create a new custom field is now a wizard with 2 steps. In the first one, the description has appeared :



In the second step, you can define a default value (excepted for fields with type "choices" et "multiple choices"):



The form for the related type of entity will look like:

]]> https://www.cremecrm.com/forum/showthread.php?tid=284 Tue, 07 Apr 2026 14:09:54 +0200 genglert]]> https://www.cremecrm.com/forum/showthread.php?tid=284  - Documents
 - Invoices & Quotes

You can now select several entities, then download a .zip archive:

]]>  - Documents
 - Invoices & Quotes

You can now select several entities, then download a .zip archive:

]]> https://www.cremecrm.com/forum/showthread.php?tid=283 Tue, 07 Apr 2026 14:08:51 +0200 genglert]]> https://www.cremecrm.com/forum/showthread.php?tid=283
In the header block, a new button has appeared :



When an entity is pinned, a small sticker is displayed :



Then you can get the last pinned entities in the menu entry "Quick access"; this entry replaces the entry which displayed only the last viewed items, and displays these ones and also the pinned entities:



A new block is available for home; it displays all the pinned entities :

]]>
In the header block, a new button has appeared :



When an entity is pinned, a small sticker is displayed :



Then you can get the last pinned entities in the menu entry "Quick access"; this entry replaces the entry which displayed only the last viewed items, and displays these ones and also the pinned entities:



A new block is available for home; it displays all the pinned entities :

]]> https://www.cremecrm.com/forum/showthread.php?tid=282 Tue, 07 Apr 2026 14:05:19 +0200 genglert]]> https://www.cremecrm.com/forum/showthread.php?tid=282
Some people have several functions in your organisation, and so get several users; they log in with the right user depending on the job to do. But it's annoying to log out then log in each time (and having several users corresponding to only one person could be confusing too).

Creme 2.8 proposes an answer to this: multiple roles. A user can have several roles, and can switch from one to another without having to log out.

In the configuration interface, the creation (& edition) form for user accepts several roles (before it accepted only one):



A user can switch its active role from the main menu:

]]>
Some people have several functions in your organisation, and so get several users; they log in with the right user depending on the job to do. But it's annoying to log out then log in each time (and having several users corresponding to only one person could be confusing too).

Creme 2.8 proposes an answer to this: multiple roles. A user can have several roles, and can switch from one to another without having to log out.

In the configuration interface, the creation (& edition) form for user accepts several roles (before it accepted only one):



A user can switch its active role from the main menu:

]]> https://www.cremecrm.com/forum/showthread.php?tid=274 Thu, 02 Oct 2025 10:45:10 +0200 genglert]]> https://www.cremecrm.com/forum/showthread.php?tid=274 nd 2025 the version 2.7 of CrèmeCRM has been released, 13 months after Creme 2.6 (August 2024).

On technical side, Django has been upgraded to version 5.2, & so minimal versions are now:
 - Python 3.10
 - MySQL 8.0.11
 - MariaDB 10.5
 - PostGreSQL 14

On user side, major changes are:
- custom types of entity can now be created (détails).
- a workflow engine (for automatic actions) has been added (détails)
- the generation of Invoices/Quotes/... numbers can now be configured (détails)
- the configuration of buttons can now be made per role (as with blocks, forms etc…).
- the views of list & the filters can now be cloned (in order to avoid building them from scratch).
- the calendar has been updated, & a new block allows to display your own calendar on the home page (see blocks configuration as usual).
- the deletion has been improved, to prevent more often the deletion because of dependencies (instead of cascade deleting things), or to get a better display for these blocking dependencies.
- it's now possible to create unsuccessful phone-calls from the detail-view of Opportunities.

Hope you'll enjoy this release!]]> nd 2025 the version 2.7 of CrèmeCRM has been released, 13 months after Creme 2.6 (August 2024).

On technical side, Django has been upgraded to version 5.2, & so minimal versions are now:
 - Python 3.10
 - MySQL 8.0.11
 - MariaDB 10.5
 - PostGreSQL 14

On user side, major changes are:
- custom types of entity can now be created (détails).
- a workflow engine (for automatic actions) has been added (détails)
- the generation of Invoices/Quotes/... numbers can now be configured (détails)
- the configuration of buttons can now be made per role (as with blocks, forms etc…).
- the views of list & the filters can now be cloned (in order to avoid building them from scratch).
- the calendar has been updated, & a new block allows to display your own calendar on the home page (see blocks configuration as usual).
- the deletion has been improved, to prevent more often the deletion because of dependencies (instead of cascade deleting things), or to get a better display for these blocking dependencies.
- it's now possible to create unsuccessful phone-calls from the detail-view of Opportunities.

Hope you'll enjoy this release!]]> https://www.cremecrm.com/forum/showthread.php?tid=272 Thu, 04 Sep 2025 10:06:22 +0200 genglert]]> https://www.cremecrm.com/forum/showthread.php?tid=272 settings. We can now configure more finely the form the numbers will have, only from the configuration UI.

In the configuration page for "billing", a new block has appeared:



Here the configuration form:



Some explanations:
- the possibility to edit numbers manually can be disabled (they can only be generated by Creme).
- the number pattern can be quite more complex than prefix+counter. For example we can insert year/month wherever we want, or chose the length of the counter (which can be padded with 0 if it's needed)
- the counter can be reset monthly or yearly.]]> settings. We can now configure more finely the form the numbers will have, only from the configuration UI.

In the configuration page for "billing", a new block has appeared:



Here the configuration form:



Some explanations:
- the possibility to edit numbers manually can be disabled (they can only be generated by Creme).
- the number pattern can be quite more complex than prefix+counter. For example we can insert year/month wherever we want, or chose the length of the counter (which can be padded with 0 if it's needed)
- the counter can be reset monthly or yearly.]]> https://www.cremecrm.com/forum/showthread.php?tid=271 Thu, 04 Sep 2025 09:03:56 +0200 genglert]]> https://www.cremecrm.com/forum/showthread.php?tid=271
A new menu entry has been added to go to the configuration:



Here the configuration page of workflows:



If we want to create a new workflow, the first step of the form asks us the type of events which triggers the actions:


(description for accessibility -- different type of event are: "An entity has been created", "An entity has been modified", "a property has been added", "A relationship has been added")

The second step allows to add some conditions (actions will be performed only of conditions are filled):


(description for accessibility -- the conditions are like the filters conditions, on regular fields & on custom fields)

In the third step, we chose the type of the first action (other actions could be added later):


(description for accessibility -- the different types of actions are  "Adding a property", "Adding a relationship", "Sending an email", "Sending an email (from a template)")

In the last step we configure the first action. Here the configuration of the action "Sending a email"; there are plenty of possibilities (e.g. choosing the recipient proposes several options):



After submission, our workflow has been created:



Notice that the workflow is currently disabled; it allows to add other actions and then enable the workflow when it's complete (with the button "Enable" on top-left of the workflow's panel).]]>
A new menu entry has been added to go to the configuration:



Here the configuration page of workflows:



If we want to create a new workflow, the first step of the form asks us the type of events which triggers the actions:


(description for accessibility -- different type of event are: "An entity has been created", "An entity has been modified", "a property has been added", "A relationship has been added")

The second step allows to add some conditions (actions will be performed only of conditions are filled):


(description for accessibility -- the conditions are like the filters conditions, on regular fields & on custom fields)

In the third step, we chose the type of the first action (other actions could be added later):


(description for accessibility -- the different types of actions are  "Adding a property", "Adding a relationship", "Sending an email", "Sending an email (from a template)")

In the last step we configure the first action. Here the configuration of the action "Sending a email"; there are plenty of possibilities (e.g. choosing the recipient proposes several options):



After submission, our workflow has been created:



Notice that the workflow is currently disabled; it allows to add other actions and then enable the workflow when it's complete (with the button "Enable" on top-left of the workflow's panel).]]> https://www.cremecrm.com/forum/showthread.php?tid=270 Wed, 03 Sep 2025 16:50:58 +0200 genglert]]> https://www.cremecrm.com/forum/showthread.php?tid=270
It's now possible to create up to 20 new types of entity directly from the configuration UI.

A new menu entry has been added to access the configuration :



There is currently no custom type:



Let's create a new type:



When our new type has been created, it's available everywhere. In a first time you will probably add some custom fields (by default there is only one field, "name"), add a menu entry to the list-view & create associated relationship types.
This screenshot shows that our new type can receive a specific button configuration: 

]]>
It's now possible to create up to 20 new types of entity directly from the configuration UI.

A new menu entry has been added to access the configuration :



There is currently no custom type:



Let's create a new type:



When our new type has been created, it's available everywhere. In a first time you will probably add some custom fields (by default there is only one field, "name"), add a menu entry to the list-view & create associated relationship types.
This screenshot shows that our new type can receive a specific button configuration: 

]]> https://www.cremecrm.com/forum/showthread.php?tid=269 Wed, 03 Sep 2025 15:54:33 +0200 genglert]]> https://www.cremecrm.com/forum/showthread.php?tid=269 er 2023).

No big technical change; notice that Python 3.12 is now officially supported.

On user side, main changes are:
- a notification system has been added.
- the calendars got 2 big improvements. The JavaScript component FullCalendar has been upgraded to the version "5.11", & it's now possible to configure the calendar per role (hour range, worked days…).
- with the library "openpyxl", XLSX files should be better supported for imports (& the format is proposed for exports too).
- the configuration of blocks for a role can now be created by cloning the configuration of another role.
- Reports has been quite improved. The main improvement is the possibility to create filters which can only be used by Reports.
- in the "billing" app, you can now configure status which are selected by default in forms. You can also chose the status used by Invoices when their number is generated.
- the button menu is now dynamically reloaded when blocks are reloaded.
- a new button, which can be set on Contacts' detail-view, is now available: "Create an unsuccessful phone call".

Hope you'll enjoy this release!]]> er 2023).

No big technical change; notice that Python 3.12 is now officially supported.

On user side, main changes are:
- a notification system has been added.
- the calendars got 2 big improvements. The JavaScript component FullCalendar has been upgraded to the version "5.11", & it's now possible to configure the calendar per role (hour range, worked days…).
- with the library "openpyxl", XLSX files should be better supported for imports (& the format is proposed for exports too).
- the configuration of blocks for a role can now be created by cloning the configuration of another role.
- Reports has been quite improved. The main improvement is the possibility to create filters which can only be used by Reports.
- in the "billing" app, you can now configure status which are selected by default in forms. You can also chose the status used by Invoices when their number is generated.
- the button menu is now dynamically reloaded when blocks are reloaded.
- a new button, which can be set on Contacts' detail-view, is now available: "Create an unsuccessful phone call".

Hope you'll enjoy this release!]]> https://www.cremecrm.com/forum/showthread.php?tid=247 Wed, 13 Sep 2023 11:57:03 +0200 genglert]]> https://www.cremecrm.com/forum/showthread.php?tid=247 th 2023 the version 2.5 of Creme has been released, 7 months after Creme 2.4.

This version is smaller than previous ones (release are normally made once a year). We have decided to release in the middle of the year intead of the start of the year, in order to improve our use of the supported Django's versions. Creme 2.5 already uses the long term support (aka LTS) Django 4.2 which has been released in April 2023. So Creme 2.5 is a transition release; in 2024, Creme 2.6 may be released in June or July.

On technical side, important items are:
- the move to Django 4.2 as seen above; this version is supported until April 2026 (https://www.djangoproject.com/download/).
- Python3.7 as been dropped, Python 3.8 becomes the minimal version.
- the minimal versions are now: MySQL 8, MariaDB 10.4 & PostGreSQL 12.

On user side, important changes are:
- an "exploration" mode which allows to view sequentially the entities contained by a list-view.
- you can now reset a Custom Form to its initial state.
- the displayed name for users can be configured (in order to keep short names & avoid names collisions as you wish).
- the SMTP servers for email campaigns can now be visually configured.
- the work started with Creme 2.4 to manage big numbers of Sector/Status/... has been finalised & works now in the filter forms.
- product & service Lines in Quote/Invoices can be re-ordered.
- a field which adds a customised colours is now present in many small models, like Activities/Invoices Statuses.
- the render of graphs has been improved, notably when there are many data to display.

Hope you'll enjoy this release!]]> th 2023 the version 2.5 of Creme has been released, 7 months after Creme 2.4.

This version is smaller than previous ones (release are normally made once a year). We have decided to release in the middle of the year intead of the start of the year, in order to improve our use of the supported Django's versions. Creme 2.5 already uses the long term support (aka LTS) Django 4.2 which has been released in April 2023. So Creme 2.5 is a transition release; in 2024, Creme 2.6 may be released in June or July.

On technical side, important items are:
- the move to Django 4.2 as seen above; this version is supported until April 2026 (https://www.djangoproject.com/download/).
- Python3.7 as been dropped, Python 3.8 becomes the minimal version.
- the minimal versions are now: MySQL 8, MariaDB 10.4 & PostGreSQL 12.

On user side, important changes are:
- an "exploration" mode which allows to view sequentially the entities contained by a list-view.
- you can now reset a Custom Form to its initial state.
- the displayed name for users can be configured (in order to keep short names & avoid names collisions as you wish).
- the SMTP servers for email campaigns can now be visually configured.
- the work started with Creme 2.4 to manage big numbers of Sector/Status/... has been finalised & works now in the filter forms.
- product & service Lines in Quote/Invoices can be re-ordered.
- a field which adds a customised colours is now present in many small models, like Activities/Invoices Statuses.
- the render of graphs has been improved, notably when there are many data to display.

Hope you'll enjoy this release!]]> https://www.cremecrm.com/forum/showthread.php?tid=238 Wed, 05 Jul 2023 17:56:08 +0200 Technowonk]]> https://www.cremecrm.com/forum/showthread.php?tid=238
I am attempting to understand the database structure of Creme, but alas I need help in viewing it. 

Could someone please let me know how to access the database schema directly?  (Or maybe someone already has it and could send it to me).

Thank you,]]>
I am attempting to understand the database structure of Creme, but alas I need help in viewing it. 

Could someone please let me know how to access the database schema directly?  (Or maybe someone already has it and could send it to me).

Thank you,]]> https://www.cremecrm.com/forum/showthread.php?tid=237 Mon, 22 May 2023 23:09:41 +0200 Technowonk]]> https://www.cremecrm.com/forum/showthread.php?tid=237
I am new here and somewhat new to coding.  I have a project that could make use of a great CRM and would like to explore the capabilities of Creme. 

I have been trying to get Creme installed on a local Fedora laptop, but without success.  The instructions are likely very clear to someone who knows Django well, but unfortunately not good enough for a Django noob (like me).

As mentioned, I am running Fedora (38) on a Thinkpad laptop (64G RAM, 6TB SSD, Xeon processor).

I've created a virtual env under Python 3.9 (also tried 3.11, but that didn't work either).

In my project root directory (CREME) I have two subdirectories, creme-crm (having installed from ZIP file) and env3.9.16 (the virtual env).

Changing directory into creme-crm and then running pip install -e .[pgsql] works for a bit and then produces the following error:
...
...
Collecting certifi>=2017.4.17 (from requests>=2.24.0->pyHanko>=0.12.1->xhtml2pdf==0.2.9->creme-crm==2.5a1)
  Using cached certifi-2023.5.7-py3-none-any.whl (156 kB)
Collecting pycairo>=1.20.0 (from rlPyCairo<1,>=0.2.0->reportlab>=3.5.53->xhtml2pdf==0.2.9->creme-crm==2.5a1)
  Using cached pycairo-1.23.0.tar.gz (344 kB)
  Installing build dependencies ... done
  Getting requirements to build wheel ... done
  Installing backend dependencies ... done
  Preparing metadata (pyproject.toml) ... done
Collecting pycparser (from cffi>=1.12->cryptography>=3.3.1->pyHanko>=0.12.1->xhtml2pdf==0.2.9->creme-crm==2.5a1)
  Using cached pycparser-2.21-py2.py3-none-any.whl (118 kB)
Building wheels for collected packages: creme-crm, pycairo
  Building editable for creme-crm (pyproject.toml) ... done
  Created wheel for creme-crm: filename=creme_crm-2.5a1-0.editable-py3-none-any.whl size=7967 sha256=d11221cb01dc9dee3befca99e1a5131326d11f68cbb859390f9f524d6b14502c
  Stored in directory: /tmp/pip-ephem-wheel-cache-88erz_8o/wheels/4e/f2/31/690ba39ad6f36fa1fb514effc290a0cb58a8e97629719f90f5
  Building wheel for pycairo (pyproject.toml) ... error
  error: subprocess-exited-with-error
 
  × Building wheel for pycairo (pyproject.toml) did not run successfully.
  │ exit code: 1
  ╰─> [15 lines of output]
      running bdist_wheel
      running build
      running build_py
      creating build
      creating build/lib.linux-x86_64-cpython-39
      creating build/lib.linux-x86_64-cpython-39/cairo
      copying cairo/__init__.py -> build/lib.linux-x86_64-cpython-39/cairo
      copying cairo/__init__.pyi -> build/lib.linux-x86_64-cpython-39/cairo
      copying cairo/py.typed -> build/lib.linux-x86_64-cpython-39/cairo
      running build_ext
      Package cairo was not found in the pkg-config search path.
      Perhaps you should add the directory containing `cairo.pc'
      to the PKG_CONFIG_PATH environment variable
      Package 'cairo', required by 'virtual:world', not found
      Command '['pkg-config', '--print-errors', '--exists', 'cairo >= 1.15.10']' returned non-zero exit status 1.
      [end of output]
 
  note: This error originates from a subprocess, and is likely not a problem with pip.
  ERROR: Failed building wheel for pycairo
Successfully built creme-crm
Failed to build pycairo
ERROR: Could not build wheels for pycairo, which is required to install pyproject.toml-based projects



So have been assuming I need to learn something obvious but after 2 and half days it isn't obvious (and I see that many other people are having similar challenges on other Django projects not related to Creme.

Really hoping someone can provide me a bit guidance on how to get this running, please.

Thank you

  Creme-Screenshot.png (Taille : 152.35 Ko / Téléchargements : 911) ]]>
I am new here and somewhat new to coding.  I have a project that could make use of a great CRM and would like to explore the capabilities of Creme. 

I have been trying to get Creme installed on a local Fedora laptop, but without success.  The instructions are likely very clear to someone who knows Django well, but unfortunately not good enough for a Django noob (like me).

As mentioned, I am running Fedora (38) on a Thinkpad laptop (64G RAM, 6TB SSD, Xeon processor).

I've created a virtual env under Python 3.9 (also tried 3.11, but that didn't work either).

In my project root directory (CREME) I have two subdirectories, creme-crm (having installed from ZIP file) and env3.9.16 (the virtual env).

Changing directory into creme-crm and then running pip install -e .[pgsql] works for a bit and then produces the following error:
...
...
Collecting certifi>=2017.4.17 (from requests>=2.24.0->pyHanko>=0.12.1->xhtml2pdf==0.2.9->creme-crm==2.5a1)
  Using cached certifi-2023.5.7-py3-none-any.whl (156 kB)
Collecting pycairo>=1.20.0 (from rlPyCairo<1,>=0.2.0->reportlab>=3.5.53->xhtml2pdf==0.2.9->creme-crm==2.5a1)
  Using cached pycairo-1.23.0.tar.gz (344 kB)
  Installing build dependencies ... done
  Getting requirements to build wheel ... done
  Installing backend dependencies ... done
  Preparing metadata (pyproject.toml) ... done
Collecting pycparser (from cffi>=1.12->cryptography>=3.3.1->pyHanko>=0.12.1->xhtml2pdf==0.2.9->creme-crm==2.5a1)
  Using cached pycparser-2.21-py2.py3-none-any.whl (118 kB)
Building wheels for collected packages: creme-crm, pycairo
  Building editable for creme-crm (pyproject.toml) ... done
  Created wheel for creme-crm: filename=creme_crm-2.5a1-0.editable-py3-none-any.whl size=7967 sha256=d11221cb01dc9dee3befca99e1a5131326d11f68cbb859390f9f524d6b14502c
  Stored in directory: /tmp/pip-ephem-wheel-cache-88erz_8o/wheels/4e/f2/31/690ba39ad6f36fa1fb514effc290a0cb58a8e97629719f90f5
  Building wheel for pycairo (pyproject.toml) ... error
  error: subprocess-exited-with-error
 
  × Building wheel for pycairo (pyproject.toml) did not run successfully.
  │ exit code: 1
  ╰─> [15 lines of output]
      running bdist_wheel
      running build
      running build_py
      creating build
      creating build/lib.linux-x86_64-cpython-39
      creating build/lib.linux-x86_64-cpython-39/cairo
      copying cairo/__init__.py -> build/lib.linux-x86_64-cpython-39/cairo
      copying cairo/__init__.pyi -> build/lib.linux-x86_64-cpython-39/cairo
      copying cairo/py.typed -> build/lib.linux-x86_64-cpython-39/cairo
      running build_ext
      Package cairo was not found in the pkg-config search path.
      Perhaps you should add the directory containing `cairo.pc'
      to the PKG_CONFIG_PATH environment variable
      Package 'cairo', required by 'virtual:world', not found
      Command '['pkg-config', '--print-errors', '--exists', 'cairo >= 1.15.10']' returned non-zero exit status 1.
      [end of output]
 
  note: This error originates from a subprocess, and is likely not a problem with pip.
  ERROR: Failed building wheel for pycairo
Successfully built creme-crm
Failed to build pycairo
ERROR: Could not build wheels for pycairo, which is required to install pyproject.toml-based projects



So have been assuming I need to learn something obvious but after 2 and half days it isn't obvious (and I see that many other people are having similar challenges on other Django projects not related to Creme.

Really hoping someone can provide me a bit guidance on how to get this running, please.

Thank you

  Creme-Screenshot.png (Taille : 152.35 Ko / Téléchargements : 911) ]]> https://www.cremecrm.com/forum/showthread.php?tid=44 Mon, 25 Nov 2013 14:58:23 +0100 genglert]]> https://www.cremecrm.com/forum/showthread.php?tid=44
If you have successfully run this migration, you have to make 2 changes in your database in order to update the code with later code (after november the 25th)

• In the table "south_migrationhistory", delete the line corresponding to the migration  "0006_v1_4__rename_field_report".
  
• In the table "reports_field", rename the column "sub_report_id" into "report_id".
  

]]>
If you have successfully run this migration, you have to make 2 changes in your database in order to update the code with later code (after november the 25th)

• In the table "south_migrationhistory", delete the line corresponding to the migration  "0006_v1_4__rename_field_report".
  
• In the table "reports_field", rename the column "sub_report_id" into "report_id".
  

]]> https://www.cremecrm.com/forum/showthread.php?tid=27 Wed, 03 Apr 2013 16:46:02 +0200 genglert]]> https://www.cremecrm.com/forum/showthread.php?tid=27
The project layout has changed, which is recommended by the Django team:
- manage.py is now at the project root, no more in creme/ .
- in settings.py, and in the  code too, Creme apps are now prefixed with 'creme.', for example 'creme_core' becomes 'creme.creme_core' .

Notice that for the moment the time zones are disabled (USE_TZ = False). It is the main feature of Django 1.4, but it needs some extra work in the code. It is temporary, and the time zones will be enabled/working in the following weeks, for the release.

Happy virtualenv !]]>
The project layout has changed, which is recommended by the Django team:
- manage.py is now at the project root, no more in creme/ .
- in settings.py, and in the  code too, Creme apps are now prefixed with 'creme.', for example 'creme_core' becomes 'creme.creme_core' .

Notice that for the moment the time zones are disabled (USE_TZ = False). It is the main feature of Django 1.4, but it needs some extra work in the code. It is temporary, and the time zones will be enabled/working in the following weeks, for the release.

Happy virtualenv !]]>