9.0.0-rc2 Second release candidate

This is a release candidate. Do not use this in production!

Please report all bugs found.

9.0.0-rc1 First release candidate for TYPO3 v10 compatibility

This is a release candidate. Do not use this in production!

Please report all bugs found.

8.5.0 Tests, WarningOnLive and Fixes

Bugs fixed: 🐛

• Clicking "cancel" when asked to publish a page/record will now actually cancel the process.
• Improved stability of publishing files. Especially if they don't exists.
• Added missing translations/Replaced hardcoded string with labels.
• Always do a reverse l10n_parent lookup to identify translations of a record.

Features: ✨

• Testing. With Codeception. And Tests. Unit and Functional. Yesss! 🎉
• WarningOnLive: Paint your foreign TYPO3 header bar in a color to add a visual warning.

8.4.5 sys_category publishing workaround

Hi there folks,

as mentioned in the #ext-in2publish TYPO3 Slack channel we've identified a regression concerning category publishing. This issue was introduced in 8.4.3. To keep the technical background story short: TYPO3 sets MM_opposite_field on both sides of the relation, which makes none the owning side. The regression was introduced when a bug - which resulted in too many relations being published - was fixed.
This release adds a permanent workaround for the specific case of sys_category relations.

Other fixes in this release:

• Configuration values which are expected to be of type array but are not will be ignored instead of resulting in an exception.
• Added a section to the docs which explains which config values may be overwritten by UserTS and PageTS
• The AbstractRecordActionLinkViewHelper will take the local portion of a combined identifier.

8.4.4 TCA group pre processor fix

A small but momentous bug was introduced in the group pre processor which decided that all configurations without the MM_opposite_field are not suited for relations instead of banning exactly those.
The bug has been reported by @dr-bock and was fixed with help of @merzilla.

8.4.3 Maintenance only

There have been a lot of commits from 8.4.2 to 8.4.3 but most of them just fixing technical details, refactoring and cleaning things up, so this release will not change much of the actual visible stuff. To keep it short i will focus on the list of changes that fix an actual bug (exceptions, failed publishing, etc).

• Use the correct charset for the remote database connection
• Fixed the return value for cached record entries
• Related records will be returned only once (especially in recursive relations or mulitple relations leading to one record)
• TCA Inline relation defined in FlexForms withtout foreign_field and without MM will now be resolved with the actual FlexForm value ("correctly").
• Fixed TCA preprocessing to exclude non-owning side relations for group, inline and select. (based on symmetric_field and MM_opposite_field). This will reduce the number of unintended relations and speed up the Publish Overview in some rare cases.
• Quoted ###REC_FIELD_[...]### Markers are now supported. Normally you won't quote these since the quotes are stripped by TYPO3 and values are quoted themselves.

8.4.2 File indexing, mutliline where clauses and broken extConf

Hello everyone 👋

to keep it short:

1. Some files haven't been published with factory.fal.reserveSysFileUids disabled: The FalIndexPostProcessor will index all files again, regardless of the module.
2. Multiline WHERE broke the query: TCA type=select foreign_table_where may now contain newlines before the ORDER BY part
3. PHP < 7.0: Record is using spl_object_hash in favor of spl_object_id for compatibility reasons
4. Whoopsi: Invalid extension configuration values crashed the SysInfo Export. Now the export will report the invalid data type instead.

Bye, cya after 2 weeks 🌴 🌞 🏄‍♂️ 🍹 🌴

8.4.1 <insert generic maintenance release here>

Hello folks,

yes, it is release time again. I told you i will shorten release cycles some time ago 😉
This release is a maintenance release that fixes some minor issues and inconveniences. Let's begin:

• Enhanced logging for some rare cases where MM tables do not have the local or foreign side properly set.
• Are we finally not executing our own deprecated code anymore? Probably yes, as of now. Sorry to the TYPO3 v8 users who experienced problems with their exceptionErrors setting.
• The Publish Overview module will not be cluttered with unchanged deleted pages anymore.
• We assure you will always find the way: It is now ensured that you will be redirected to the correct controller after publishing.
• Added a dirty fix to prevent infinite loops in a recursive method which will make your machine explode upon opening the Publish Overview module.
• MM_opposite_field, a long known TCA feature that more-or-less switches the value of uid_foreign and uid_local MM table fields is now back in the preprocessed TCA for columns of type group. This means that relations will be resolved correctly again (for eaxmple the "related" field from EXT:news).

Last but not least: The method CommonRepository::convertToRecord has been deprecated.

8.4.0 SysInfo export and fixed tool buttons

What's up?

Publishing TYPO3 content is a complex problem. It gets even worse when everybody can extend TYPO3 with own content elements and tables. The Content Publisher aims to support any feature and extension regardless of that huge hurdle. We have a lot of tests that check if certain functions are working or if settings are correct. But i have the feeling Problems know how to evolute and therefore are not cought by our big test suite.
Users, Admins and Devs that use or intregrate in2publish_core often don't want to fuzz around with the big code base, so they reach out for help. Often - and especially if they are new to this extension - people tend to send in reports like "Well, publishing does not work" without any other information like logs and error messages. This is due to the fact that they often simply can not know how to gather they required information or even what information is required to debug. So we created a tools module that exports nearly any information that was ever relevant for debugging any problem we ever had.
TBH this is very much information and it takes a lot of time to gather it, but it allows us to save a lot of time by reducing roundtrips. They only thing you really need to know:
⚠️ The exported information may contain sensitive data (e.g. credentials) ⚠️
You have to remove this data yourself before sending us your system info export.

You can find the new tool in the Publish Tools module. It is labelled with "System information". To generate a report press the "Download the system info" Button and wait until the .json file is generated and downloaded. You can see which information is included by selecting the "Show the system Info" button.
The json file is not encrypted, because we are transparent about the information we export from your system and allow you to shrink the export with your favourite JSON Editor before sending it to us.

About support:

• We have a public TYPO3 slack channel for short questions. This is not the place to post your sys info export. It is also not the place to ask someone to fix your 3rd party TCA 😉
• We allow github issues. Github issues are the place for Bugs reported by you, the community. You should not post your sys info there, because it will be publicly available (remeber the sensitive data). If required you will be asked about sections of that export.
• Mail & Issue tracker: If you require serious support you can create an issue in our issue tracker or ask for support via email.
• Enterprise version customers: You are eligible for limited free support. You can save your precious support time and by always sending the system info with your request.

---

Ah, yea, before i forget: @sbusemann wrote some CSS 😱 to prevent tool buttons hiding when the view gets too small. He did a great job! 😄

8.3.2 Fix call of findPropertiesByProperties in findByProperties

The method BaseRepository::findPropertiesByProperties was refactored to accept a table name. During refactoring of the whole application a single method call (actually 2 consecutive calls) was not rewritten correctly.