it looks very strange. you found this in the version as it comes out of the box??

the first issue (JViewLegacy) is really weird (because all views should be "legacy"), but maybe is an error on packing the package.

however the second error looks really strnage to me. maybe it's a codification issue?

I'll take a look at this right away

THANKS a lot for your feedback!

to the environment
Installed clean Joomla 3.1.1 without any 3rd party extensions/templates/plugins and or languages.

Downloaded com_invoices today and installed it as usual.

I've just checked the JViewLegacy and you're right. I've already fixed it.

however the other issue doesn't appear on our packages... it must be some issue with the codification when you open that file. what are you using to open it?

and some more
/components/com_invoices/views/invoices/tmpl/simple.php - Line 53 + 57
/components/com_invoices/views/invoices/tmpl/default.php - Line 81 + 85 + 193 + 197
/components/com_invoices/views/payment/tmpl/default.php - Line 114

removing all the "Â" will remove the notice about "Use of undefined constant - assumed ' ' " in the backend

thanks for the info. I don't know what that is, I can't see the "Â" on our files..
maybe it is somehow generated on packing the zip. I'll keep investigating.

however the other issue doesn't appear on our packages... it must be some issue with the codification when you open that file. what are you using to open it?

downloaded the file com_invoices_1.1.0_pro_3.0.zip and installed directly with the installer from joomla. after that opened the affected files with various editors, all the same.

I've downloaded the file just again and unzipped it with winrar, 7zip, windows inbuild and mac inbuild unpacker, just all the same!?

maybe it's an issue when ZIP packing the files.

hmmmm I'm looking through forums to see what this can be.

thanks.

ok, that's really weird.

My backup archive is permanently synced with dropbox to share one archive over all my computers and phones/tablets. i could investigate that in some of my zip archives are the same problems.

downloaded again and save outside, everything is ok. movin' to my archive synced with dropbox caused the problem with that sign!?

this is really really strange :blink: but interesting to know where errors can arise - in this case it seems to be dropbox's fault :whistle:


sorry for the inconvenience and scare the birds

thanks for supporting

Hi again,

After trying to reproduce my suspicion, i could't confirm that it is just dropbox's fault.

I've tried any type of hard disk and flash drive - even various file systems from Win, Max, Linux (NTFS, FAT, etc...) and more than 10 different ways to extract, upload and install the file in joomla

I hate errors and notices, and i always try to fix them all ( in my own projects ) therefore in all my environments full error reporting is activated.

But such a bug, i've never seen before and i am more and more confused about it.

Some time ago i used a beta version of WinSCP to edit my files. In some cases, if you copy/paste large codeblocks, WinSCP truncated this code at a special sign and put a whitespace at the end.

I noticed that when i upload that via SVN to my repository. After i tried to reproduce the way of copy in WinSCP and paste in Notepad++ i'll see it. Just a whitespace in WinSCP and a black block in Notepad++.


Please do not understand this as personally, there's no evil intend like this one => :evil:

It is just a hint or a tip where we could get a closer look at to solve this problem.

As i wrote before or you can see at the attached image, i'll respaced all curly brackets, and the note about the undefined constant is gone (frontend and backend views).

The only approach i've found on the web is an article from stackoverflow about "bad spaces" after curly brackets.

May this help too...

regards

hello!

I'm as confused as you are.. I had never seen this error before!!

and I can't see them in my files... :S very strange.

it's great that you are investigating this (well, at least you know how to solve it..!)
I'll keep investigating this on my end..!