@bmihelac How about making this a jazzband project? That way, the entire django community can maintain it. This is by far the best cookie library for django since it completely replaces paid solutions. I think it would be great for the community to have this project.

Fixed the typo

@VictorGerritsen

Just to be clear, you only want have the cookie consent banner show up on only the root domain and not the subdomains?

Example only show it on mydomain.com and do not show it on sub.mydomain.com ?

@ThomSawyer Thanks I was already aware of PyPi not being updated and needing to use the command to use the latest version as you have kindly added here. I have been using the COOKIE_CONSENT_LOG_ENABLED successfully for some time now.

I am confused. Why create a completely separate dedicated app if you could have another additional setting merged to the main django-cookie-consent library to let people decide if they want to use it or not? What I was trying to suggest was just make a setting for your plugin something like COOKIE_CONSENT_PLUGIN_SIGNALS = True|False or whatever you want to call it so that everyone could use/not use it from just 1 app instead of 2? If you made a setting like that, then users like me wouldn't be forced to have anything logged to the database for users regarding their cookie acceptances/declines. And users like you could decide to have it logged in the database if they wish.

Or do you mean in the meantime before PyPi is updated with the main django-cookie-consent to have a separate app so that people could have an updated one from you for the time being until the main one gets updated?

@templargin Thanks for posting your solution. You might need to separate Company.objects.get_or_create because created_by should probably not be in the get lookup.

@aureliendebord

I call this method when I run into a type error when using this field post-import.

def repair_json(djangoobject, field: str):
    """
    Repairs broken import/export strings.
    @param djangoobject: the broken django object, has side effect, as it might be repaired
    @param field: name of the field to repair
    @return:
    """
    # check if there is a chance that it is broken
    if hasattr(djangoobject, field) and (
            type(getattr(djangoobject, field)) == JSONString or type(getattr(djangoobject, field)) == str):
        jsonstring = getattr(djangoobject, field)
        jsonstring = jsonstring.removeprefix("\"")
        jsonstring = jsonstring.removesuffix("\"")
        jsonstring = jsonstring.replace("\'", "\"")
        jsonstring = jsonstring.replace("\\\"", "\"")
        jsonstring = jsonstring.replace("False", "false")
        jsonstring = jsonstring.replace("True", "true")
        setattr(djangoobject, field, json.loads(jsonstring))
        # even if validation will fail, this was improved
        djangoobject.save()

@9mido The COOKIE_CONSENT_LOG_ENABLED already handles the situation you are discribing. If set to False there will be no log entries in the database. You can see it in the codebase:

• https://github.com/bmihelac/django-cookie-consent/blob/master/cookie_consent/util.py#L95
• https://github.com/bmihelac/django-cookie-consent/blob/master/cookie_consent/util.py#L117

I think that your problem might be that the latest release on PyPI (0.2.6) doesn't allow you to enable / disable this setting.

To fix your problem quickly, you can install the package from Github's master branch instead of PyPI:

pip install -e git://github.com/bmihelac/django-cookie-consent@master#egg=django-cookie-consent

Same problem here. @BSVogler did you find a workaround for this?

Hi, I want to import a CSV , but there are space behind the "," in the header row.

Internal id, Date and time, Transaction type, Coin type, Coin amount, USD Value, Original Interest Coin, Interest Amount In Original Coin, Confirmed

in the model I have defined the fields like this: internal_id = models.CharField(('Internal id'), max_length=40, db_index=True) date_and_time = models.DateTimeField(('Date and time'), db_index=True) transaction_type = models.CharField(('Transaction type'), max_length=20, db_index=True) coin_type = models.CharField(('Coin type'), max_length=10, db_index=True) coin_amount = models.FloatField(('Coin amount'), db_index=True) usd_value = models.FloatField(('USD Value'), null=True, db_index=True) original_interest_coin = models.CharField(('Original Interest Coin'), max_length=10, db_index=True) interest_amount_in_original_coin = models.FloatField(('Interest Amount In Original Coin'), null=True, db_index=True) confirmed = models.CharField(_('Confirmed'), max_length=5, db_index=True)

If I change the header row and replace the fieldnames to the internal variables the import is running perfect. Is it possible to map fieldnames with a space in front and in the name to the import fields ??

Thanks a lot !!

Ingo

Is there a way to set the cookie-consent cookie on the root domain? e.g. *.mydomain.com I have a wildcard subdomain and right now the consent cookie includes the subdomain, making the consent banner popup appear for each subdomain i visit.

I have the following models and M2M relationships:

class Market(models.Model):
    marketname = models.CharField(max_length=500)
    market_id = models.CharField(max_length=100, blank=True)

    def __str__(self):
        return self.marketname

class TeamMember(models.Model):
    firstname = models.CharField(max_length=100, default= "First Name")
    lastname = models.CharField(max_length=100, default= "Last Name")
    email = models.EmailField(max_length=254)

    def __str__(self):
        return self.email

class EmailReport(models.Model):
    name = models.CharField(max_length=1000)
    recipients = models.ManyToManyField('team.TeamMember', related_name="teamrecipients")
    frequency = models.CharField(max_length=1000, blank= True)
    markets = models.ManyToManyField('opportunities.Market', blank=True)
    def __str__(self):
        return self.name

The following is my admin.py for the EmailReport registration.

class EmailReportResource(resources.ModelResource):
    recipients = fields.Field(widget=ManyToManyWidget(TeamMember, field="email"))
    markets = fields.Field(widget=ManyToManyWidget(Market, field='marketname'))
    class Meta:
        model = EmailReport
        fields = ['id', 'name', 'recipients', 'markets']

class EmailReportAdmin(ImportExportModelAdmin):
    resource_class = EmailReportResource

admin.site.register(EmailReport, EmailReportAdmin)

I am able to export- and all char fields export normally- however, my M2M fields all appear blank.

Can anyone please point out my mistake?

Thank you so much!

Any updates for this?

Want multiple types of export for the same model Eg. We have investors model We want exports like

• Investors data for issuing shares for project owner.
• Investors data for compliance data with different fields
• Founders to see investors with invested project.

Dup of https://github.com/django-import-export/django-import-export/issues/765

This issue has solution in pr https://github.com/django-import-export/django-import-export/pull/1223

<!--- Welcome to django-import-export --> <!--- Your issue may already be reported! Please search on the issue tracker before creating one. --> <!--- Additionally, you can either search or ask you question on Stack Overflow tagged with django-import-export --> <!--- If you would still like to create a question on github, please do so and remember that the more details you give, the more likely your question will be answered. -->

Its hard to debug this without the proper information, ie versions, how you are importing it, project structure, etc.

Have the same problem now too