Contao-backend

[SeptimusVII]

• [x] #7

• [x] job's fields not relevant in a generic context. Should be made from custom attributes

• [x] #8

• [x] this field is not planned in module's zoning, and doesn't seem useful to me.

• [x] #9

• [x] can we have a blnDisplayAttributes, and a blnDisplayPictures, next to the blnDisplayText field

• [x] can't dupplicate an offer: An exception occurred while executing a query: SQLSTATE[42000]: Syntax error or access violation: 1064 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 '='' WHERE id='6'' at line 1

[SeptimusVII]

@LupusVII

[create-issue-branch[bot]]

Branch issue-6-Contao-backend created!

[LupusVII]

The duplication issue is linked to the first SQL error.

[LupusVII]

For the contact picture, since it is not mandatory, should we leave it for people who might use it?

[SeptimusVII]

For the contact picture, since it is not mandatory, should we leave it for people who might use it?

since it is not a generic type of field, my go to would be to trash it. If someone happen to need it, it should be a module override

[LupusVII]

For the contact picture, since it is not mandatory, should we leave it for people who might use it?

since it is not a generic type of field, my go to would be to trash it. If someone happen to need it, it should be a module override

Trash it is then

[LupusVII]

Done in https://github.com/Web-Ex-Machina/contao-offers/releases/tag/2.0.0