Technical announcements:
04-Sep-2024: Since REMP tools v3.9, the primary Elasticsearch version we support is v8. We made sure that there’s backwards compatibility with the v7, so you still have time to upgrade your database. The compatibility will only be enforced by the end of this year. After January 2025 the compatibility will most likely still be in place, but will not be guaranteed by us.
24-May-2024: This summer Elasticsearch will drop support for v7. We are planning to move to Elasticsearch 8. If you use Beam, plan the Elasticsearch update to end of the summer / beginning of the fall 2024. Otherwise you might not be able to update to the latest version.
22-Jan-2024: Next major CRM release (4.0) planned for second half of 2024 will raise minimum MySQL version to 8.0.31 (due to features required by our modules) and will drop support of PHP 8.1. Please plan your upgrades accordingly.
22-Jan-2024: CRM 3.0 dropped support for PHP 8.0. CRM now requires PHP 8.1 and newer.
21-Nov-2023: The latest version of CRM (2.11) is the last one to support PHP 8.0. Future versions of CRM will require PHP 8.1 at minimum.
28-Jun-2023: REMP 3.0 dropped support for Yarn 1.x. REMP now requires Yarn 2.x (or newer).
It took more than two months to release the new version of CRM, but we hope it was worth it. We’re working on the support for One Stop Shop mode in EU, which allows you to charge your users VAT rate dependning on their country. At the moment it’s not completely finished yet, since we still need to work on foreign B2B sales. The full support with the documentation will be available next month.
These changes forced us to do some major refactorings and they caused some breaking changes. Please go through the changelog (mainly the PaymentsModule
) and verify that these changes don’t break something for you.
The noticable features of this release are:
You can see the full changelog here.
We managed to successfully upgrade to Elasticsearch 8 during the summer months. The upgrade was farely easy and we only needed to follow official upgrade guide. To use the latest version of Elasticsearch, please upgrade Tracker API, Segments API, and Telegraf.
Thanks to our friends from Fatchilli, we also made changes necessary to split Campaign to the separate skeleton app in the near future. The Campaign is already extracted into its own module and we now wait for the skeleton app to be ready. Becasue of that, there are some important changes to follow/check before upgrading in the Campaign’s changelog, please make sure you read them.
The full list of changes is available here.
In this version we bring improvements to the Mailer UI, Beam dashboard and add support for Elasticsearch 8 into the Segments and Tracker APIs. Eventhough the update is not mandatory for this release, we highly recommend to do it so you are future-proof. We remind that the Elasticsearch 8 update is imminent and should happen by the end of the summer / beginning of the fall.
Full changelog is available here.
This version brins changes, that will allow us to support One Stop Shop scheme in the EU. In fact, we already support this internally and test it on our installations. If nothing special emerges, we expect to open-source the full support in the following releases. You might see stuff related to One Stop Shop in the changelog, none of it is actually live yet and we recommend not to enable it.
Apart from the One Stop Shop changes, this version includes:
|trans
filter.header_block
and sales_funnel_header_block
config options, and for head_script
in each of the sales funnels.SalesFunnelTwigSnippetLoaderTrait
that helps you loading and providing snippets into your funnels.The rest is mainly improvements and minor fixes. You can check the full changelog here.
No new features in this release, but couple of notable technical improvements:
RedisClientTrait
are important for you.application:cleanup
command that removes obsolete data from the database. Please add it to your scheduled tasks to be run at least once a day.Full changelog is available here.
After 2 months, CRM brings some notable changes that took us some time to deliver.
TriggerManager
to scenarios. If you implement your own triggers, please see the changelog./api/v2/apple-appstore/webhook
endpoint.We advise to review the full changelog available here.
This release brings interesting feature in Campaign and some minor updates in other tools.
Full changelog is available here.
After 6 weeks, we have new CRM release with some notable new features:
ActiveRow
object can now provided its state before the update thanks to integrating OriginalAwareInterface
.We advise to review the full changelog available here.
This time it’s a very minor update, since most of our efforts were directed to the CRM.
We’ve also updated our skeleton apps (Mailer, Beam) to use PHP 8.2 by default. That’s the version of PHP we recommend to use from now on.
Full changelog is available here.
After two months of updates and refactorings, we’re finally able to release version 3.0 of REMP CRM.
This version brings lots of internal updates and breaking changes - if you are a developer extending CRM with your own modules, please pay attention to everything marked as BREAKING and IMPORTANT within the changelog. Minimum supported version of PHP is now 8.1 and we plan to raise minimum version of MySQL in the next major release (4.0). The most cumbersome changeset of this release - PSR4 refactoring - is covered by Rector rules and the fix can be automated on your side.
Feature-wise this is a standard update release, with couple of notable ones:
google:create-missing-recurrent
.Updates in the Skeleton app (https://github.com/remp2020/crm-skeleton/):
app/bootstrap.php
change application initialization to $application = new Crm\ApplicationModule\Application\Core(dirname(__DIR__));
. (namespace change)bin/command.php
change application initialization to $application = new Crm\ApplicationModule\Application\Core();
. (namespace change)
app/config.neon
change definition of ConfigExtension
to local_configs: Crm\ApplicationModule\Config\ConfigExtension
.
app/config.local.neon
, if you kept the original set of populators, replace Populator
with Populators
within their namespaces.You can see all of those changes commited here: https://github.com/remp2020/crm-skeleton/commit/4d115a560c0b3d6160aff8158bc38ab3a5a0d372
The full changelog is available here.
.env
file. We haven’t tested it in production and it doesn’t support Redis Sentinel, so use it at your own risk.Full changelog is available here.
This release focuses on bringing some smaller features developed to one of our clients and made available open-source.
n_token
) and the first account was kept signed in in CRM.The full changelog is available here.
Full changelog is available here.
Due to the changes in underlying framework, we were force to quickly release a hotfix for Mailer with some possibly breaking changes. See the changelog here.
This release brings performance and visual improvements. The notable are:
LazyEventEmitter
allows us to defer initialization of event handlers and speed up all requests to CRM. You can either replace the registration manually, or use our Rector rule to do that automatically for you.
public function registerEventHandlers(Emitter $emitter)
with the replacement method:
public function registerLazyEventHandlers(LazyEventEmitter $emitter)
The full changelog is available here.
New minor version brings mostly fixes to Beam (related to Beam skeleton) and project changes (docker & docker compose changes and fix for yarn link not being able to link JS packages).
Full changelog is available here.
Important changes:
charge_at
is calculated from payment->paid_at
and subscription_type->length
).All changes are listed in changelog for v2.9.
Our friends from Petit Press reported some issues when using Yarn 3. This release fixes two issues that could occur if you used Yarn 3 to install dependencies instead of (tested) Yarn 2. If you encounter any issues, update to this version.
Full changelog is available here.
During testing of Beam Skeleton (now with the complete Docker Compose!) we’ve found out that there are background schedules missing and couple of other minor issues. If you started to work with Beam Skeleton, please update remp/beam-module
to the latest version.
We also recommend to check the updated version of Beam Skeleton, since it now provides all dependencies within Docker Compose (there’s no need to install them manually) and also testing article with example how to include JS snippet into the page and which APIs are mandatory to call when you want to use Beam.
Full changelog is available here.
This version brings mainly stability improvements including couple of bugfixes.
The most notable feature of the release is that Mailer now has the option to notify REMP CRM that user’s mail subscription changed. This one is important for people using CRM’s user data cache (in Redis), as people’s mail subscription might be updated directly in Mailer and CRM wouldn’t know about this change. To enable this feature, register the handler to these Hermes events:
services:
hermesWorker:
setup:
- add('user-subscribed', Remp\MailerModule\Hermes\NotifyCrmSubscribeUnsubscribeHandler())
- add('user-unsubscribed', Remp\MailerModule\Hermes\NotifyCrmSubscribeUnsubscribeHandler())
- add('user-subscribed-variant', Remp\MailerModule\Hermes\NotifyCrmSubscribeUnsubscribeHandler())
- add('user-unsubscribed-variant', Remp\MailerModule\Hermes\NotifyCrmSubscribeUnsubscribeHandler())
The full changelog is available here.
This month brings mainly usability and performance improvements within CRM:
See the changelog. to see full list of changes for this version.
After couple of months of development we’re proud to release v3.0. There’s a lot going on under the hood and Beam, Campaign, and Sso are no ready to be extensible apps instead of static apps provided at the moment. We now deprecate use of remp2020/remp
repository for deploys in favor of the newly created skeleton applications. We’re finalizing Beam Skeleton and the other apps will continue soon.
Please be aware that this version is a major release due to some breaking changes. Please update your Mailer skeleton application based on these changes and Yarn to v2.
Apart from the under-the-hood changes, this release also brings performance improvements and some minor feature updates to Mailer.
The full changelog is available here.
This release brings new extensions points for widgets and event handlers accross the application, and fixes some UI and usability issues of CRM admin.
If you want to get more technical, the full changelog is available here.
Patch release 2.2.1 contains fixes for link tracking (new feature of Mailer introduced in 2.2).
The full changelog is available here.
Release 2.2 contains only Mailer changes. Notable change are clicked links tracking and breaking change to how multi variant mail types are subscribed when default variant is not set and no variant is provided.
The full changelog is available here.
Release 2.6 brings few fixes (eg. next_subscription_type_id
not being saved when creating subscription type in admin); audit log for payment_items
; option to not prolong child company subscriptions when new parent subscription is purchased and pairing of one device token to multiple access tokens of same user. RempMailerModule
contains few breaking changes.
The full changelog is available here.
This release brings lots of optimizations to Beam, which started to feel a bit slower for bigger instances. Mailer brings better possibilities to manage newsletter variants (both in APIs and UI).
The full changelog is available here.
The latest version of CRM is out. This month it’s mainly backend improvements and edge case fixes. There were some important internal changes in the InvoiceModule
and the SubscriptionModule
- see the Changelog.
The full changelog is available here.
The main reason for major version is bump of the minimal version of the core dependencies. REMP tools now require PHP 8.1 and Node.js 18+ to release. The release otherwise contains performance improvements in Mailer and Beam, which will also continue in the following releases.
Please note that in order to use this version, it is expected that both mail:migrate-mail-logs-and-conversions
and mail:migrate-user-subscriptions-and-variants
commands introduced in the previous versions were already executed. Update to this version only if you meet the criteria.
The full changelog is available here.
This release brings new extension method for subscriptions asked by our users for some time - ExtendLastExtension
. It adds new subscription after the last available subscription. It should replace the ExtendActualExtension
as the default in the future. Also we found a logical issue with audit log which could keep track of anonymized records. To delete those records, please add application:audit_logs_cleanup
to your scheduled tasks.
The full changelog is available here.
Today we also bring the new version of REMP tools. In Mailer we continue with internal updates (see info about mail:migrate-user-subscriptions-and-variants
) and improve tracking of subscribe sources. In Campaign the most important feature is new set of settings for the campaign allowing you to configure what happens when users clicks/closes the banner (without using the Beam segments).
Please note that this version requires you to schedule a manual migration in order to update database internals without the distruption of the system. Read the CHANGELOG’s section with mail:migrate-user-subscriptions-and-variants
command execution.
The full changelog is available here.
After some irregular updates in the recent months we will be trying to get back to more regular (monthly) release cycles. This CRM release might not look big, but for API-primary users of CRM it will be a huge performance improvement.
The full changelog is available here.
This took a while, but there are features to look for. This release brings support for PHP 8.1 and couple of notable features:
ServiceParamsProviderInterface
in the Mailer’s readme file.Please note that this version requires you to schedule a manual migration in order to update database internals without the distruption of the system. Read the CHANGELOG’s section with mail:migrate-mail-logs-and-conversions
command execution.
The full changelog is available here.
Main feature of this release is support for PHP 8.1, which can now safely to deploy the CRM. Otherwise this is again mainly stability release.
The full changelog is available here.
The hotfix fixing the issues from 19-Dec-2022 should have included also release of Users and Subscriptions modules. We’ve just realized it was missing and it’s available now for download.
Release is addressing changes in the nette/di
package since version 3.1
. If you updated your project, you could see some deprecations that were fixed in this release.
Release is fixing bug preventing saving form when editing existing subscription type/segment/sales-funnel in administration.
After the major release couple of months ago, we have a new version of CRM with performance and stability improvements.
The full changelog is available here.
Finally, after few years of development, we have managed to release the first major stable release (1.0) of the REMP tools.
The main change is that PHP 8.0 is now the required version in all tools.
The full changelog is available here.
Hotfix includes issue fix that prevents saving template with invalid syntax in Mailer.
The full changelog is available here.
This version is the last PHP 7.4 compatible release of the REMP tools. Changes:
The full changelog is available here.
Few months after the first major version comes CRM version 2.0, as we now follow semantic versioning more rigorously. The two biggest changes are upgrade from PHP 7.4 to version 8.0 and switch from Latte v2 to v3.
There are other major features added, such as:
The full changelog is available here.
This release includes couple of usability fixes and minor features, that were requested for a longer time:
And more. You can check the full changelog here.
We’ve identified an issue with Access-Control-Allow-Credentials
header, which was not included in the all requests if it was configured. This release fixes the issue. (info)
This release is made primarily of one feature: Wallet pay support. Since this version, CRM contains new wallet pay module, which brings support for Google pay and Apple pay payments through the gateway - mostly banks and big payment providers.
Our implementation brings the wallet pay payments with support of Tatrabanka (Slovak bank), but the module is extensible for other providers as well. Since the feature is new, please consider it as a nearly-production-ready and use with a bit of caution.
This version also brings German translations, kudos to alexmerz for all the effort.
The full changelog is available here.
Since today, Mailgun started to enforce additional checks on their API which broke non-batch sending of emails. If you encounter an error when sending the system emails through the Mailgun, please update immediatelly.
The changelog and error description is here, and this is the commit explaining the issue.
After more than a two months we bring new version of the CRM. This is more-or-less stability / minor features release. Make sure you go through the changelog to see if any of the features/changes interest you.
Full changelog is available here.
The newest version of Latte templating engine started to trigger deprecation notices for one of the Mailer internal features. This version fixes the deprecation warning and filterLoader issue.
See the changelog here.
We’ve accidentally made a breaking change in one of our APIs which forced us to release this hotfix version. Since we were able to merge couple of other minor fixes/notices since the last version, this release contains breaking-change fix and also couple of minors.
See the full changelog here.
It’s been a couple of weeks since the latest release and REMP tools bring couple of nice features:
You can see the full changelog here.
After years of features and months of refactorings, we’re happy to annouce that the CRM is stable enough for major version 1.0. Internally we updated the underlying framework and API library, to bring you better features in your modules.
Full changelog is available here and is split to the two sections: Nette 3 update-related section, and feature changes made since the 0.38. This update will be a bit harder due to the amount of breaking changes. Please follow the migration guide in order to successfully update your internal extensions.
This release brings some useful features to Beam and Mailer:
Full changelog is available here.
We’ve received a report for XSS vulnerability present on the SSO login error callback page. This error was present in the all previous versions of REMP tools and affected Beam, Campaign and SSO. Please update your REMP tools to prevent the vulnerability misuse. (changelog)
We’ve received couple of bugreports in Beam. One related to the conversion event aggregation (which could miss some events prior to conversion) and author/section segment calculation (which could take couple of hours). We recommend to upgrade to this release. (changelog)
We pushed this release as late as possible. This might also be the last release before major update to v1.0. There are couple of important changes in this version:
You can check the full changelog here.
Almost three months passed since the latest version, yet this is mainly a maintenance release:
And numerous fixes and optimizations. Head to the changelog to see all of the changes in this version and don’t forget to also update your Tracker and Segment API binaries (available here).
Handling of sales funnel meta values got broken in the latest release and CRM was not able to save new funnel. If you use this flow to create new funnels (opposing to using seeders), please update to the latest version. (changelog)
CRM was generating notices on scenarios detail because of the dependency on the currently-internal module. Please update the crm-scenarios-module
to fix this issue. (changelog)
Main features of this release are:
Check the changelog to see the full list of changes and upgrade information.
The query generated by SubscriptionTypeLength scenario criteria was incompatible with MySQL 8 and could cause DB execution errors. Please update your crm-subscriptions-module
to 0.36.1
. (changelog)
Another two months passed by and a lot features landed in this release:
And much more. Head to the changelog to see all of the changes in this version and don’t forget to also update your Tracker and Segment API binaries (available here).
This time it’s more about internal improvements and bugfixes.
There’s one note-worthy experimental feature to mention: Google/Apple pay payments in combination with Stripe gateway. We’re currently testing the implementation and we’ll probably be extending this in the future so it can be used with Tatrabanka. Stay tuned.
Check the changelog to see the full list of changes and upgrade information.
Previous version optimized and speed up API. Unfortunately it introduced bug which breaks initial CRM installation (application is unable to create required tables). This hotfix release contains fix for Core::command()
. Update your crm-application-module
to 0.35.1
(changelog).
This release focuses mainly on improving stability, but brings some interesting features.
Check the changelog to see the full list of changes and upgrade information.
This is mainly maintenance release focusing on improving existing features. The main improvements are:
There’s more, including couple of breaking changes that might affect your own modules. Head to the changelog to see the full list of changes and upgrade information.
Form for managing subscription types is extendible through data-providers. Unfortunately due to a bug the data-providers were not correctly handled during the form submission process. Update your crm-subscriptions-module
to 0.33.1
(changelog).
This is another bigger release, which took us more than two months to finalize. The main improvements are:
And much more. Head to the changelog to see all of the changes in this version and don’t forget to also update your Tracker and Segment API binaries (available here).
Recently CRM added support for read-only connections in case you have multiple database replicas. In case you haven’t configured the connection yet, the Heartbeat handler (trigerred by application:heartbeat
) command would crash. This release fixes the issue. (changelog)
There have been issues reported with access to CRM admin caused by external translation libraries. Please update your crm-application-module
to 0.33.1
. (changelog)
It’s been a while since the last release. The main improvements in this version are:
There’s more, including couple of breaking changes, so head to the changelog to see the full list of changes and upgrade information.