-
Notifications
You must be signed in to change notification settings - Fork 207
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
FileHelper::ClassInfo() regex not coping with windows newlines with XAMPP #1517
Comments
thank you @tskodaw this is a very good input. I am going to add some test cases and add your fix thank you! What would be an example for insufficient class name? |
@tskodaw i just pushed a fix, could you please try again with the latest dev-master on luya-core? |
@nadar works fine for me under win7 "Importer run successfully" :) for BlockImporter::saveBlock($fullClassName) -> insufficient as testcase would be just |
I think this could be dangerous as its possible to have such a namespace and is therefore not invalid. Can we close your issue? |
hmm good point, |
I know what you mean. The problem is that every module or application can attache classes to the importer process as its very common routine, so therefore we can not stop, but maybe adding a hint "block importer has warning(s) XYZ" or sth like this. I am waiting for the yii2 console table output helper (which should released soon) then i will rewrite things anyway. Thanks again for your report. |
What steps will reproduce the problem?
What is the expected result?
correct program termination.
What do you get instead? (A Screenshot can help us a lot!)
Comment
basic problem:
in luya-core FileHelper::ClassInfo() line 82, the regex
does not match windows newlines (CRLF), at least on my xampp-installation ,
changing it to:
solved the situation and worked fine on linux too,
additionally:
perhaps in luya-module-cms\BlockImporter::saveBlock
an error handling could be fine when BlockImporter::saveBlockByPath calls it with insufficient class name?
Additional infos
The text was updated successfully, but these errors were encountered: