phpwcms Support Forum

When browsing through the phpwcms folders I noticed that there are a lot of different places where images are stored and I think this is very confusing. It is probably a result from the ongoing development where new components are added to the system all the time but I think it is a good idea to do a big cleanup here.

A good start would be to completely integrate the excellent file management system in the wysiwyg editor. This would work *much* easyer. That way the /picture folder can be removed.

Further maybe a separation can be made between the frontend images (move to phpwcms/template folder) and the backend images.

I also do not completely understand the phpwcms/ftp folder. I think it would be the most userfriendly if ftp was not necessary anymore.

Is there anyone else with some ideas on this?

johanvanderwijk wrote:
I also do not completely understand the phpwcms/ftp folder. I think it would be the most userfriendly if ftp was not necessary anymore.

Is there anyone else with some ideas on this?

It is where you upload the files you want to "take over" with phpwcms, eg if you have 100 pix you can via the backend easy get generated thumbnails for all the images just with 1 click

johanvanderwijk wrote:When browsing through the phpwcms folders I noticed that there are a lot of different places where images are stored and I think this is very confusing. It is probably a result from the ongoing development where new components are added to the system all the time but I think it is a good idea to do a big cleanup here.

~Actually~ NOT
I believe they have been planned, from the beginning, to be carefully separated on purpose. Grouped by function(purpose), front or back end, whether changed often or not. etc.

johanvanderwijk wrote:A good start would be to completely integrate the file excellent management system in the wysiwyg editor. This would work *much* easyer. That way the /picture folder can be removed.

The variety of WYSIWYG editors have their own varying degrees of support for control of file-browsing and means of changing locations. Also, some are adversely affected by URL rewriting schemes. I'm sure any enhancements in this area by you would be welcome additions to phpWCMS

johanvanderwijk wrote:Further maybe a separation can be made between the frontend images (move to phpwcms/template folder) and the backend images.

This appears to be the current means of organization with the exception of "/picture" folder for individual's use

johanvanderwijk wrote:I also do not completely understand the phpwcms/ftp folder. I think it would be the most userfriendly if ftp was not necessary anymore.

If, by that you mean, that multiple file transfers via PHP take place... it is my understanding that this has proven itself unreliable. If, not... by what "other means", what do you suggest? All wisdom about implementations is welcome and desirable

Okay, so now I know what the phpwmcs_ftp folder is for

I still think that it would make the tool even better if the file management part would be integrated in the WYSIWYG editor (maybe it would help if only one editor would be available?). I have been uploading all the images I wanted to use for my website through the file manager and organized them in a clear folder structure and now I am having some trouble in using them in the editor. Of course this might be caused by a lack of knowledge on my side, but it just does not 'feel' very userfriendly.

Please do not think I am an arrogant &%$$$# who thinks he knows everything better than the developers because this is not the case. I am just an enthousiastic new user who is strugling a bit

johanvanderwijk wrote:Okay, so now I know what the phpwmcs_ftp folder is for

I still think that it would make the tool even better if the file management part would be integrated in the WYSIWYG editor (maybe it would help if only one editor would be available?). I have been uploading all the images I wanted to use for my website through the file manager and organized them in a clear folder structure and now I am having some trouble in using them in the editor. Of course this might be caused by a lack of knowledge on my side, but it just does not 'feel' very userfriendly.

I see a good piont in that - I guess O.G do the same, so maybe he will make it Or one of you?

OK my statement:

I will not change the way of handling image folders. WYSIWYG is something that needs time - early users can remember - I have never planned to use WYSIWYG (I don't like such editors - lot of trouble). And there was no time to write a file browser for WYSIWYG editors. Sorry.

The picture folder was planned for use related to {IMAGE..} replacement tags only. It's better to have these separated from internal file manager

I'm planning to integrate a chooser especially for these replacement tags.

Oliver

One thing that would be helpful with regards to the backend file manager would be to provide info to the client/end user as to what prefix is used in the cataloging of uploaded images.

This would allow for somewhat faster identification of images for the client/end user in WYSIWYG. As far as I know when uploading an image the original is first place in the tmp folder:

File Manager: upload new image: bluebuild.jpg 586 x 340 21KB
Goes directly to Thumb Preview: no resizing:
File/Path becomes: phpwcms_tmp/thumb_preview/1_16_NlelvlCBj2.jpg
Original Image: 21KB New Image 26K (GD JPEG COMPRESSION*) -
* Got a question about this - see the very end of end of this post

Basically this image exists as a resource in the file manager. Until requested by content/images of content/images/text it will not show up in the phpwcms option of the WYSIWYG editor. Once requested by either of these options, it becomes (path/file):

content/images/1_16_NlelvlCBj2-538x.jpg
(538 reflecting original width - no sizing)

content/images/1_16_NlelvlCBj2-300x.jpg
(300 reflecting resizing)

What would be nice would be these two features:

(Feature 1) If explicitly made public, a copy of the original would automatically be placed in the content/images folder, thus bypassing the need to generate this listing in the WYSIWYG editor by invoking the content/images function.

(Feature 2) Some means in the file manager to provide end user info as to what prefix is being used by phpwcms to refer to the image file. Something like:



This way accessing the image in WYSIWYG could be found quite quickly:



I just wanted to offer this an an idea to consider in making the great system as it exists now, a little more user friendly to clients........who might benefit from this feature. Having said this, I am not sure how easily this would be to implement (Feature 2) or whether there are file security issues in (Feature 1)

*One last question regarding the upload compression size. Is the original jpg image recompressed by GD2 and if so is the compression setting changed via php.ini?

Cheers,
jsw

No - that will not be very helpful.

The Spaw image chooser is a snug based on users wishes.

I recommend the use of {IMAGE...} replacement tags only. A new chooser for anywhere use will be implemented which delivers the right tag.

Oliver

"A new chooser for anywhere use will be implemented which delivers the right tag."

As I guessed, your approach would be a 'step ahead' - more powerful and practical. Looking forward to its release!

Wanted to ask...are the GD compression settings controlled via php.ini? I think I remember seeing them there, but can't be quite sure. Also if imagemajick is installed, will that yield superior jpeg compression. Just a question.

Cheers, jsw

no - compression is controlled by phpwcms itself.

Check "imagick.convert.inc.php" and $qual. Reset this to set higher compression. Maybe compression is set to a different value anywhere in the code.

I will implement new var to set it for every image resizing also if sharpened or not - only availabe for ImageMagick.

Oliver