Releases: in2code-de/in2publish_core
5.8.2 Small release with FAL indexing and plugin inclusion fix
Two little patches are included in this release, also some cleanup has been done to get rid of the legacy stuff for TYPO 6.2.
5.8.1 Small fixes
This small release is required for an update of in2publish and also fixes a relation resolving bug with MM relations when the owning side is also the local side.
5.8.0 RCE API and hella bugfixes
Some time has passed since the last release and things have been kind of quiet, but I'm back with a new feature release from in2publish_core.
Despite not being visible in the user interface, a large part of the SSH connection has been subjected to a general overhaul, which leads to a devaluation (our first real depreciation of an API) and a completely new API, namely "Remote Command Execution", in short "RCE".
This new API increases stability, fault tolerance, and provides response filtering and is clean and easy to use.
This API also provides the foundation for any other API that is used to communicate with the remote system, which would be RPC/Envelope and rFALd, which got mentioned in previous releases.
Also, some stuff now gets cached so things might speed up a bit... Just a bit.
The second feature is visible, since it tests the setting adminOnly
on the live system and result in a warning if regular editors are allowed to log in in the live backend (Which is something in2publish should make superfluous).
And here's a bigger list of bugfixes:
- The command
status:all
now outputs really all status values. It was a bit too shy. - The command
table:backup
won't try to backup non existent tables anymore - I've found another place where the foreign system tries to initialize a connection to stage. tut tut tut!
- Envelopes are now only fetched when the database is connected
- Added a missing default value for the TCA ImageManipulationProcessor
- Backend Modules can tolerate filed database connections again
- Spyc is now included properly everywhere
- File permissions are once again applied when using PHP 7
- Removed the hover effect on links in backend modules
- Files which got replaced and then moved (or moved and then replaced) can now be published properly. Also, files failed to publish up to now they will be shown as changed again. (FAL returned not the real file size ;..; )
5.7.0 just_signals
This release is, despite being a feature release, nothing really big and it won't change anything for you. There are just a few new signals which are used by the enterprise version to support other extensions out-of-the-box (fal_securedownload in this case).
5.6.0 setDBinit and inline-mm support
It's feature time again 🎉
- Respect the foreign setting [SYS][setDBinit] ([DB][Connections][Default][initCommands] in v8)
- Enable support for inline records which are referenced over an intermediate MM table (kudos to @birgerstoeckelmann )
Also there are some bugfixes included:
- Fixed a bug which led to segmentation faults in PHP 5.6 (since the latest few patches of that PHP version)
- Display the correct storage UID ich the storage has a different driver on foreign
- Do not try to connect to a foreign database on foreign (that would be stupid, eh?)
Happy publishing!
5.5.1 File publishing fixes, typos, last TYPO3 v6 support
Since 31 March TYPO3 6.2 LTS is no longer supported and will no longer receive updates (except ELTS). When we began this project we decided to stickt with the LTS versions, so we support most of the websites out there. So this is the last version of in2publish_core that supports the old TYPO3 version.
Anyway, a lot of stuff has been added to this release "last minute", including a lot of "random" bug- and typo-fixes, API changes (methods copied from Record to RecordInterface) increase of loose coupling of the Record model and also some bugfixes concerning the new "file publishing" (or rather "UID conflict avoidance") strategy.
5.5.0 TYPO3 v8 LTS support and conflict avoidance
The release of TYPO3 v8 LTS came closer every day and it will be eventually released tomorrow. So i can say we're just on time to release a TYPO3 v8 LTS compatible version of in2publish_core, which also comes with a new feature. 🎉
The new feature is an experimental file diff-ing and publishing approach, that will allow you to have FAL file uploads on the foreign instance without intersecting identifiers. Please note that it is not stable yet and there is also no guarantee that it will work for you and your 3rd party extension. Red the FAQ section about "How do i handle user generated content?" for more information.
P.S.: Have fun at your local TYPO3 v8 LTS release party tomorrow!
5.4.1 FFS and UI (EV) bugfix
This update includes a bugfix for FAL compatibility and a little UI enhancement (Interface bug).
- Moving files or renaming the parent folder in the file list and publishing that file (state: "moved") via Publish Files Module or as relation via Records led to the exception
Could not execute RPC [...]. An error occurred on foreign: Oops, an error occurred: The target file "[...]" already exists.
- (Enterprise version) After failure of publishing pages in the page or list module the publish button was not reset, nor the page reloaded
5.4.0 Many bug fixes and RealUrl 2.2 support
A lot of things happen in this release. Most of the commits are bugfixes regarding different topics:
- Fixed a bug that would throw an Exception when using PHP7 and the Publish Files Module:
1425467980: Insufficient write permissions for remote file "[...]typo3temp/tx_in2publish_temp_[...]"
- Fixed FFS record info overrule, which resulted in an Exception if the record existed in sys_file on local only.
empty query
- Corrected an error message and added a logger when opening a sftp stream on foreign failed because of other reasons that insufficient permissions
- Enforced permissions on storages on Live. This Exception occurred when publishing a content element with a youtube video
Could not execute RPC [...]. An error occurred on foreign: Oops, an error occurred: You are not allowed to access that file: "[...]"
- Set the creation_date for in2publish tasks again (this does not affect functionality, but that information simply got lost)
- Updated some comments and declarations
- Prohibit the creation of RealUrlTasks when the record in question is not changed
On top of those bugfixes we put some effort in really supporting RealUrl >= 2.2 (with *data instead of *cache tables). The biggest difference is the cleaner approach by simulation the DataHandler API on Live instead of ploughing through the tables.
The RealUrl support for RealUrl version 2.1 and lower stays untouched.
5.3.8 Minor stability improvements
When publishing records which are related to a file on disk it could happen that the state is not set or split correctly for both state dependent publishing actions (publishing data/file). This release prevents exceptions when publishing records with ambivalent "moved" state.
Beyond this some log writings were implemented to be able to track errors better when publishing or an RPC fails.