Frog CMS

If your config says assets dir is /assets or assets it means files are being uploaded to wrong directory. The file should exist in:

http://173.45.236.219/frog/assets/bk-leftPanel.gif

Do I understand correctly you have installed Subdirectory frog instead of document root?

Yes I did install frog as a subdirectory. The folder is in /var/www/frog

My images currently get uploaded into /var/www/frog/admin/assets what do I need to change to make sure the images go into the correct dir?

Tuupola where you host your website, and Kinemas for example…becouse as i have realized now my problem is in hosting service…i guess

BTW, Tuupola, you remember our conversation about disabling Assets plugin and when enabling again you have to provide the paths to Assets again? I agreed with you a good program won’t leave stuff behind after uninstallation?

Well, I need to upgrade a site from 094 to 095, and was reading the update instructions:

5. Login to the admin section of your 0.9.4 installation and disable all
plugins. (plugins generally shouldn’t remove data from the database when being
disabled, so this shouldn’t be a problem.)

Maybe this, as I assume this installation method will be around for some time, would beg for a code change for now anyway. Just a suggestion.

@tuupola

I use the plugin, without the code modification/addition.

Works for me, but Page-not-found-plugin needs to be disabled and enabled after adding Assets/Image-Resize and the lot.

I don’t have to wait for a reload to see the images that need to be generated. They will popup after some time.

The only time I have to reload is if I use PHP to create some special sized version of an image. E.g. see my little marketplace. There I build the images on the basis of subpages, with a special page part for the image that becomes an thumbnail.

@tuupola, if you could build it into the code to push Page-not-found to be executed later/last, that would be great, but otherwise state this procedure in the readme/instructions.

Dependancies, dependancies… O well. Code is more high maintenance than women, and sometimes it seems all logic is lost on it. (Although we know it’s just complexity that we are grappling with).

@BlueFrog: If you leave out the second part of step 8 (the php-call) it should be working also. Maybe you could test that, so image resize will not be called twice.

So the bug in combination with the Page Not Found plugin has a fix, but now I still have a white-boxes problem.

The plugin writes my thumbnails with the SERVER path instead of a ‘web path’: so it points an <IMG> element’s SRC to ‘/var/www/webapps/username/assets/foo/file.jpg’ instead of ‘/assets/foo/file.jpg’. Any ideas?

UPDATE

Together with Tuupola we figured it out. In my case it had to do with a Webfaction hosted account. Webfaction changed the DOCUMENT_ROOT and added an underscore ““ to it (dunno why). My $_SERVER[‘DOCUMENT_ROOT’] became e.g. _”/home/username/webapps/“_ That last underscore prevented Tuupola’s code from working.

There is a fix on the Webfaction Support site. The complete text is below. I followed the instructions and it worked!

HOW DO I SET MY PHP DOCUMENT_ROOT?

If your PHP application is reporting ‘/home/username/webapps/_’ as DOCUMENT_ROOT and you need it to be something else, do the following:

Assuming your Static/CGI/PHP app is named “my_app”…

Create ~/webapps/my_app/set_document_root.php with the following contents:

<?php 
  $_SERVER['DOCUMENT_ROOT'] = '/home/username/webapps/my_app'; 
?>

Create ~/webapps/my_app/.htaccess (if it does not exist already) and add the following to it:

<IfModule php5_module>
    php_value auto_prepend_file "/home/username/webapps/my_app/set_document_root.php"
</IfModule>