Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Breaks Entity Manager in Flow 3 #4

Closed
Sebobo opened this issue May 27, 2015 · 2 comments
Closed

Breaks Entity Manager in Flow 3 #4

Sebobo opened this issue May 27, 2015 · 2 comments

Comments

@Sebobo
Copy link
Contributor

Sebobo commented May 27, 2015

In the function optimizePublishedFileof the ResourcePublisherAspect class in Flow 2 the absolute path was returned and in Flow 3 only the relative path to the resource.
This breaks the optimizeFile function and leads to an Exception of the Entity Manager when doctrine tries to store a resource.
For some reason the aspect doesn't appear in the Stacktrace.

Fixed it locally by injecting resource.targets.localWebDirectoryPersistentResourcesTarget.targetOptions.path from TYPO3.Flow and using it as prefix to get the absolute path.
Not sure if that is the perfect way.

@dfeyer
Copy link
Contributor

dfeyer commented Jun 3, 2015

This PR fix the issue: #5

I think injecting the value is not correct, because we can have multiple target with different publishing path.

@aertmann
Copy link
Member

aertmann commented Jul 2, 2015

PR merged thanks to @dfeyer

@aertmann aertmann closed this as completed Jul 2, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants