Question Full Screen Pictures Problem in 1.6.2

Hi - I can confirm the same on my site. Images with spaces in the filename won't load in the lightbox. Newly uploaded images (post 1.6.2) with spaces are renamed and display correctly. At least that's the way it seems to work from my testing.

I guess it may be possible to rename all the images and run an sql query to rename the links to the images in the database. However, its not the sort of thing I'd like to do without further advice - perhaps these 'broken' images/links will be fixed when upgrading to the next version..?
I guess what I'm asking is, is this topic archived because it's going to be fixed, or archived because its possible to work around, and what is my best way forward? At them moment I've disabled the lightbox feature in the back end.

Thanks
Rob

The topic is archived because the problem existed before K 1.6.2 but does not exist from K 1.6.2.

The problem was that, before K 1.6.2 there were other issues with Kunena. We fixed those issues but, in fixing those issues, some people had already uploaded images with spaces in the filenames and its those filenames that are causing the current problem. However, with K 1.6.2 it's not possible to upload images with spaces in filenames. Therefore there isn't a new problem any more.

We know the problem. You know what to do to fix the problem. Does that explain why this topic has been archived?

I don't, however, know the extent of the problem. I don't, for example, know how many people have this problem (where they uploaded images whose filenames had spaces in them), something that was tolerated before K 1.6.2 but that is not tolerated now. I therefore do not know how "important" it is that the installer process somehow "fix up" any files that were uploaded before. Do you understand what I'm trying to say?

Hi sozzled
Thank you for the reply.

I do understand exactly what you are saying. From my point of view though (and I except that I'm being somewhat subjective here) a problem has been created (didn't pre 1.6.2 does post 1.6.2). Images that did load correctly in to the lightbox before, now do not. Obviously the bigger picture is that larger issues have been fixed - great - that is what we all want, so please don't take this as a complaint.

However, I don't know how many (10's, 100's, 1000's??) images are suffering this problem on my site - yet.

What I need to do to resolve this is rename all my images - removing spaces - and run an sql query against my db to identify and update image links containing spaces. I can do this, I'm, not 100% comfortable with it, but I will be once I've taken the time to test the process before committing to the change on a live site. If though this fault was known and was due to be addressed as part of the next version upgrade process then I'd have been happy to work around the problem and wait.

I know how strongly you advise against modification of the database and core files and, this is partly my reason for caution up to now. I'm going to work now on my own solution to this problem, I'll report the process back to this thread over the next week or so - all being well, just in case there are other's in my situation.

I remember when migrating to 1.6 some fairly major changes were made to the file structure and database around image/file storage, I wasn't sure if this was a bug, as a part of that process - I don't know exactly when the problem was introduced.

Thanks for the clarification - I guess its a fine line between a bug and an known minor issue affecting a minority of users!


Cheers


Rob

edit: I agree this is an archived issue - for tidiness - I feel it's still worthwhile updating the thread with developments.

teratyke wrote: However, I don't know how many (10's, 100's, 1000's??) images are suffering this problem on my site - yet.

Yes, I understand.

Y'know, there's an enormous amount of folklore - I'm as much a believer in folklore as the next guy, too - that went like this: back in the bad old days of DOS you couldn't have spaces in filenames. Even after Windows NT came about, and you could use spaces, I rarely used spaces because I had this feeling that it wasn't really a very good idea to do that. And so, instead of having a file called "my favourite zebra.job" I would create a file called my_favourite_zebra.jpg. It avoids those kinds of problems.

Anyway, this isn't a Kunena problem, really. This is a file management problem and I don't really know what you can do about it. Tough problem; difficult to know what to advise. Won't be fixed by the Kunena project team in the next 24 hours, that's a certainty.

Hi sozzled,
You've got to let go of those DOS days, its not healthy. 8.3 filenames, never again...

Anyway back to the point.
I fixed my images today and just for the sake of completeness I'll post the process I followed here. I was very cautious - I'm sure there are more elegant and efficient methods.

Firstly I downloaded all my images /media/kunena/attachments - I skipped the legacy directory as these images don't have the thumbnail functionality in kunena so far as I can tell. I don't have convenient SSH access to my host, hence the downloading and uploading process. I renamed all the files to replace spaces with _'s. I used a tool called ReNamer available free through cnet. I re uploaded - effectively duplicated the files now with no spaces - I have a list of files containing spaces to delete at some point in the future. I also did this for the image's thumbnails.

I did an SQL export of the jos_kunena_attachments table and using excel built a list of SQL statements to update the table with the new data in the format of...

UPDATE `mydb`.`jos_kunena_attachments` SET `filename` = 'filename_with_no_spaces.JPG' WHERE `jos_kunena_attachments`.`id` =3767;

One of these for each image that required modification.

I like using excel for this kind of stuff, because Its pretty fast and I can check the output before I commit it to the db. Also, I'm not confident enough in SQL to do this any other way!

And that's it - so far so good. I would say though that we have a relatively small forum (busy and lots of images, well used, but small) and this was effecting around 300 images, so it was a significant problem for us and couldn't really be left.

I can't say I'd recommend the process.

Thanks
Rob