
Product
Announcing Socket Fix 2.0
Socket Fix 2.0 brings targeted CVE remediation, smarter upgrade planning, and broader ecosystem support to help developers get to zero alerts.
Python 3.11 to 3.12 DRF 3.14 to 3.16
Python 3.11 to 3.12 DRF 3.14 to 3.16
Python 3.11 to 3.13 DRF 3.14 to 3.16
Python 3.11 to 3.13 DRF 3.14 to 3.16
bump-my-version is used to manage releases.
After reaching a releasable state, run pipx run bump-my-version bump <patch|minor|major> --message="feat: release x, refs y
This will update the release version in .bumpversion.toml
and the CI/CD pipelines do the rest.
easys-ordermanager/easys_ordermanager/v3/serializer.Serializer
is considered WIP until integration in EasyS startsUpdates to Serializer v1 & v2, see serializer changelog
Updates to Serializer v1 & v2, see serializer changelog
Updates to Serializer v1 & v2, see serializer changelog
Updates to Serializer v1 & v2, see serializer changelog
Updates to Serializer v1 & v2, see serializer changelog
Updates to Serializer v1 & v2, see serializer changelog
Updates to Serializer v1 & v2, see serializer changelog
Updates to Serializer v1 & v2, see serializer changelog
Updates to Serializer v1 & v2, see serializer changelog
Updates to Serializer v1 & v2, see serializer changelog
Updates to Serializer v2, see serializer changelog
Updates to Serializer v1, see serializer changelog
Fixes flake8 errors.
Updates to Serializer v1 & v2, see serializer changelog
Updates to Serializer v1 & v2, see serializer changelog
Updates to Serializer v1 & v2, see serializer changelog
Updates to Serializer v1 & v2, see serializer changelog
Updates to Serializer v1 & v2, see serializer changelog
Updates to Serializer v1 & v2, see serializer changelog
Replace ugettext* usages with gettext* usages as Python 3 is unicode compatible anyway
Updates to Serializer v1 & v2, see serializer changelog
Updated translations of PRODUCT_PAYMENT_CYCLE_CHOICES
updates changelog
Adds product payment cycle support to Serializer v1 & v2, see serializer changelog
Updates to Serializer v1 & v2, see serializer changelog
Updates to Serializer v1 & v2, see serializer changelog
Update maximum supported version of django-phonenumber-field>=3.0.1,<5.1
Update maximum supported version of phonenumbers>=7.0.6,<8.13
Update maximum supported version of djangorestframework>=3.7.7,<3.13
Update maximum required version of django-countries>=4.4,<6.1.4 and django-internationalflavor>=0.3.1,<0.5
Update package to version phonenumbers>=7.0.6,<8.12.12
Update package to version django-model-utils>=3.1.2,<5.0 - for backwards compatibility
Update package to version django-model-utils>=4.0.0,<5.0
Fix serializer v2 choice fields
Updates to Serializer v2, see serializer changelog
Update german translations
Updates to Serializer v1 & v2, see serializer changelog
Updates to Serializer v2, see serializer changelog
Changed a translation
Fix test cases
Updates to Serializer v1/v2, see serializer changelog
Updates to Serializer v1/v2, see serializer changelog
Fixed code style to pass checks
Updates to Serializer v2, see serializer changelog
Updates to Serializer v2, see serializer changelog
Introduction of serializer v2
easys-ordermanager/easys_ordermanager/v1/serializer.Serializer
is now frozen on the state of release 1.2.3easys-ordermanager/easys_ordermanager/v2/serializer.Serializer
is considered WIP until integration in EasyS starts and new changes will go into v3, see serializer changelog for changes between v1 and v2Reverted
Make sure Django 3 is not installed until further support
Add proper dependencies to avoid unwanted failure with possible upgrades when installed freshly. See setup.py for dependencies
Add unique validation on opening_hours
list of values of OrderLineListingSerializer
.
The opening hours lis should be unique for every day_of_week
(see OrderLineListingOpeningHoursSerializer
)
This release contains backwards incompatible changes.
Changes on OrderLineDisplayBasicSerializer
geo_targeting
field.geo_targeting_zip
field which accepts one string zip code. Not mandatorygeo_targeting_radius
field accepting integer values between 1-80 (km). Mandatory only if geo_targeting_zip
is given.stock_images_allowed
field:banner_image_selection
choice field accepting following values:
target_page_type
existing field which is not required anymore.Changes on OrderLineGoogleAdsPremiumSerializer
:
call_tracking
boolean required field.Clean README file.
Fix expected_impression_share field of OrderLineGoogleAdsBasicSerializer to accept 5 digits in order to validate value 100.00
Small fix on pep8 error
This release contains backwards incompatible changes
Split Display detail OrderLineDisplaySerializer in two different serializers and fields for basic and premium product levels:
remove detail_display
field from OrderLine
add detail_display_basic
field (OrderLineDisplayBasicSerializer
) on OrderLine
The serializer contains following fields:
New fields:
banner_color_selection
choice field with values: 1 for Color from Logo/Website and 2 for Set color . To be used in combination with fields color_code_x
Fields with changed definition
impressions_per_month
choice field with accepted values: 20.000 , 40.000 and 80.000creative_options
choice field contains only values: 1 for Customer provided and 3 for Create animatedFields with the same definition as in the previous OrderLineDisplaySerializer
geo_targeting
geo_targeting
campaign_goal
headline
sub_headline
bullet_points
call_to_action
color_code_1
color_code_2
color_code_3
stock_images_allowed
target_page_type
target_url
package_template
location_frame_text
creative_options
add detail_display_premium
field (OrderLineDisplayPremiumSerializer
) on OrderLine
Serializer contains following fields with the same definition as in the previous OrderLineDisplaySerializer
booking_type
target_devices
creatives_format
impressions_per_day
impressions_per_month
age_targeting
gender_targeting
geo_targeting
channel_targeting
interest_targeting
campaign_goal
target_page_type
target_url
creative_options
Split Google Ads detail OrderLineGoogleAdsSerializer in two different serializers for basic and premium product levels:
remove detail_google_ads
field from OrderLine
add detail_google_ads_basic
field (OrderLineGoogleAdsBasicSerializer
) on OrderLine
Serializer contains following fields with the same definition as in the previous OrderLineGoogleAdsSerializer
campaign_goal
regions
expected_impression_share
keywords
keywords_with_zero_search_volume
target_audience
add detail_google_ads_premium
field (OrderLineGoogleAdsPremiumSerializer
) on OrderLine
Serializer contains following fields with the same definition as in the previous OrderLineGoogleAdsSerializer
call_to_action
campaign_goal
regions
expected_clicks
expected_conversions
existing_account_id
include_remarketing
keywords
keywords_with_zero_search_volume
target_audience
usp
All product fee fields on OrderLineSerializer
became optional:
setup_fee
start_fee
budget
fee
one_time_budget
commission
deferred_payment_sum
Add validation for commission provided for product type Google Ads level Basic: fixed value of 40
Add validation for combination of product type and level: check if a matching HC products subtype exists
Add validation for the payment fees provided: check if a matching HC payment type exists.
djangorestframework<3.9
doesn't support it)OrderLineDisplayNativeSerializer.target_url
from 400 to 2000.creatives_template
to be mandatory again, but nullable. Note: It cannot be null when the creatives_creator
is not the Customer (1
).creatives_template
from OrderLineInAppSerializer
to be optional. Note: It will remain mandatory when the
creatives_creator
is not the Customer (1
).DeprecationWarning
if a deprecated constant from easys_ordermanager.v3.serializer
is used.OrderLineDisplayPremiumSerializer
DISPLAY_TARGETING_
constants for interest_targeting
field, will be removed in v4.interest_targeting
field now accepts arbitrary integer values. Invalid values will be ignored.OrderLineDisplayPremiumSerializer
DISPLAY_AGE_14_29
choice for age_targeting
field, will be removed in v4.DISPLAY_AGE_18_29
choice as a replacement.OrderLineDisplayNativeSerializer
campaign_goal
field, optional.target_page_type
field, optional in v3, will be required in v4.OrderLineDisplayPremiumSerializer
customer_wishes
field, optional.DisplayNativeCreativeSerializer
info_for_webdesign
field, will be removed in v4.customer_wishes
field, optional, as a replacement.OrderLineListingSerializer
company_name
field, optional. Will default to customer name if not provided.DisplayNativeCreativeSerializer
NATIVE_AD_FLOW_AD_IN
(4
) from ad_type
choices.NATIVE_AD_FLOW_AD_OUT
(5
) from ad_type
choices.NATIVE_AD_FLOW_AD_PROSPECT
(6
) from ad_type
choices.OrderLineSeoSerializer
location_names
regions
field not required anymoretopics
field.OrderLineGoogleAdsPremiumSerializer
EXISTING_STROER_LANDINGPAGE
(4
) to target_page_type
choicesDisplayNativeCreativeSerializer
NATIVE_VIDEO_AD
(7
) to ad_type
choices.OrderLineInAppSerializer
gender_targeting
field, optional.age_targeting_from
field, optional.age_targeting_to
field, optional.OrderLineListingSerializer
opening_hours_description
field to 255ContactSerializer
is_primary_contact
field.AccountSerializer
campaign_goal
field.usp
field.description
field.basic_template
to OrderLineWebsiteSerializer
to chose template for basic product level websites from WEBSITE_BASIC_TEMPLATE_CHOICES
OrderLineGoogleAdsPremiumSerializer
campaign_goal
field to 1000.ContactSerializer
opt_in_reviews
, optional.opt_in_listing_reminders
, optional.AccountLocationSerializer
billing_name
to be optional.AccountLocationSerializer
billing_name
.OrderLineWebsiteSerializer
internal_area
.OrderLineEmailSerializer
included_accounts
to included_addresses
.additional_accounts
to additional_addresses
.OrderLineInAppSerializer
INAPP_AUDIENCE_EMPTY
to target_audiences
choices.OrderLineGoogleAdsPremiumSerializer
target_page_type
required.expected_clicks
expected_conversions
expected_impression_share
expected_impressions
keywords_with_zero_search_volume
branch_codes
call_to_action
is_generic_campaign
generic_topics
remarketing_setup_fee
remarketing_budget
OrderLineLandingpageSerializer
easys_related_orderline_id
, referencing the easys ID of a product in the same payload, required.EXISTING_STROER_LANDINGPAGE
NEW_LANDINGPAGE
constant.validate_website_and_landingpage_exists()
needs_website
is True
only when target_page_type
property corresponds to a new website. This was the behavior before the version 2.0.10
of the serializer.PRODUCT_TYPE_CHOICES
PRODUCT_TYPE_DOMAIN
OrderLineDomainSerializer
OrderLineWebsiteSerializer
and OrderLineEmailSerializer
have been migrated to
this serializer. Contains the following fields:
desired_domain
: character field of maximum length 100, requireddomain_type
: choice of DOMAIN_TYPE_CHOICES
, requireddomain_info
: character field of maximum length 100, optionalOrderLineWebsiteSerializer
desired_domain
, domain_type
, domain_info
)easys_orderline_domain_id
, referencing the easys ID of a domain product in the same payloadOrderLineEmailSerializer
desired_domain
, domain_type
, domain_info
)easys_orderline_domain_id
, referencing the easys ID of a domain product in the same payload.included_accounts
to accept a non-empty list of emails, requiredadditional_accounts
to accept a possibly empty list of additional emails, requiredaddresses
OrderLineSerializer
down_payment
, optionaldetail_domain
accepting OrderLineDomainSerializer
data, optionalSerializer
easys_orderline_domain_id
it must reference a domain
product provided in the same payloadOrderLineGoogleAdsPremiumSerializer
remarketing_setup_fee
and remarketing_budget
, since they are no longer used.OrderLineSeoSerializer
EXISTING_STROER_LANDINGPAGE
OrderLineSeoSerializer
campaign_goal
field, not required.3
) for target_page_type
field. It corresponds to EXISTING_STROER_LANDINGPAGE
.OrderSerializer
salesforce_opportunity_id
field, required.OrderLineDisplayNativeSerializer
target_url
.OrderLineSerializer
salesforce_opportunity_line_item_id
field, not required.OrderLineDisplayNativeSerializer
age_group_from
and age_group_from
are null
.DisplayNativeCreativeSerializer
teaser
and advertorial
to accept null instead of blank, and removed allow_blank
from ad_type
.OrderLineGoogleAdsPremiumSerializer
ticket_id
field, not required.OrderLineDisplayNativeSerializer
OrderLineDisplayNativeSerializer
OrderLineInAppSerializer
poi_targeting_file
as not required.OrderLineInAppSerializer
poi_targeting_file
field.OrderLineSerializer
is_pre_briefing_necessary
field, default value is False.OrderLineDisplayPremiumSerializer
impressions_per_month
and impressions_one_time
, depending on booking_type
(continuous or fixed).OrderLineDisplayPremiumSerializer
impressions_per_day
to impressions_one_time
.OrderLineDisplayPremiumSerializer
age_targeting
choices: DISPLAY_AGE_CHOICES
, removed legacy [DISPLAY_AGE_14_19, DISPLAY_AGE_20_29]
and added DISPLAY_AGE_14_29
detail_google_ads_basic
from OrderLineSerializer
OrderLineGoogleAdsBasicSerializer
detail_display_basic
from OrderLineSerializer
OrderLineDisplayBasicSerializer
OrderLineGoogleAdsPremiumSerializer
branch_codes
, optional.OrderLineDisplayPremiumSerializer
short_name
, optional.OrderLineEmailSerializer
desired_domain
, domain_type
and domain_info
.OrderLineGoogleAdsPremiumSerializer
is_generic_campaign
and generic_topics
, optionals.OrderLineSeoSerializer
ticket_id
optional.ContactSerializer
opt_in_marketing
, optional.OrderLineSeoSerializer
regions
optional.OrderLineInAppSerializer
target_audiences
optional. One of the target_audiences
and other_target_audiences
is requiredOrderLineSerializer
payment_cycle
: choice of PRODUCT_PAYMENT_CYCLE_CHOICES
, optionalOrderLineListingSerializer
tonline_costs
and tonline_city
PRODUCT_TYPE_CHOICES
PRODUCT_TYPE_TONLINE
AccountLocationSerializer
payment_debit_account_iban
in case of payment_type
ChargeOrderLineWebsiteSerializer
design_preference_minimalistic_embellished
design_preference_modern_classic
design_preference_simple_striking
design_preference_text_picture
OrderLineFacebookSerializer
ages
choices adjustment: 14_18
is now 13_17
and 19_24
is 18_24
OrderLineWebsiteSerializer
desired_domain
to accept only domain names without http protocol and no IP addressesOrderLineGoogleAdsPremiumSerializer
expected_impressions
and expected_impression_share
target_page_type
AccountLocationSerializer
google_places_id
to be 1000 characters max (was 30 before)OrderLineWebsiteSerializer
additional_subpages
must be >= 0 and <= 60 nowOrderLineGoogleAdsBasicSerializer
target_url
OrderLineGoogleAdsPremiumSerializer
target_url
AccountSerializer
branch_codes
cannot be empty any moreOrderLineSeoSerializer
topics
cannot be empty any moreregions
cannot be empty any moreOrderLineGoogleAdsBasicSerializer
regions
cannot be empty any moreOrderLineLandingpageSerializer
added, similar to OrderLineWebsiteSerializer
except for
additional_subpages
: positive integer, requiredlogo_creation
: choice of LOGO_CREATION_CHOICES
, requiredOrderLineSerializer
detail_landingpage
: type OrderLineLandingpageSerializer
, only required when OrderLine represents a landingpage productOrderLineGoogleAdsBasicSerializer
target_page_type
: choice of GOOGLE_ADS_LANDING_PAGE_CHOICES
, optional
Serializer
changes for validationOrderLineGoogleAdsPremiumSerializer
branch_codes
: list of HeroCentral provided industry topic codes, optional
target_page_type
: choice of GOOGLE_ADS_LANDING_PAGE_CHOICES
, optional
Serializer
changes for validationremarketing_setup_fee
: decimal, must be >=0 if include_remarketing=true
remarketing_budget
: decimal, must be >=0 if include_remarketing=true
target_page_type
NEW_WEBSITE
, the serializer will require an OrderLine of type PRODUCT_TYPE_WEBSITE
to existNEW_LANDINGPAGE
, the serializer will require an OrderLine of type PRODUCT_TYPE_LANDINGPAGE
to existtarget_page_type
are:
FAQs
API definition of RH order manager for EasyS
We found that easys-ordermanager demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Product
Socket Fix 2.0 brings targeted CVE remediation, smarter upgrade planning, and broader ecosystem support to help developers get to zero alerts.
Security News
Socket CEO Feross Aboukhadijeh joins Risky Business Weekly to unpack recent npm phishing attacks, their limited impact, and the risks if attackers get smarter.
Product
Socket’s new Tier 1 Reachability filters out up to 80% of irrelevant CVEs, so security teams can focus on the vulnerabilities that matter.