Unable to view uploaded files
Permalink 1 user found helpful
When I try to add image to my web site using concrete5 add image functions I can not view any of the uploaded images
According to concrete5 is uploads images to
http://aralsf.com/files/9313/4057/1076/b9.jpg...
But when I try to view this url there is nothing there.
How do I modify where concrete5 upload images
Help
According to concrete5 is uploads images to
http://aralsf.com/files/9313/4057/1076/b9.jpg...
But when I try to view this url there is nothing there.
How do I modify where concrete5 upload images
Help
Check the file permissions on the files directory - is it writeable by your webserver?
If I go thru a file manager in my cpanel... the file is actually there and I can view it...
Its just I can not see it in Concrete5 or go to the url the concrete thinks it uploaded the file too
according to cpanel file is located
/public_html/files/9313/4057/1076/b9.jpg
Its just I can not see it in Concrete5 or go to the url the concrete thinks it uploaded the file too
according to cpanel file is located
/public_html/files/9313/4057/1076/b9.jpg
What does your cpanel file manager, or ftp client say the file permissions on that file are? Who is the owner and group on the file (and the parent directories for that matter?
If your files are where they claim to be, I would expect that your domain would respond with the C5 home page, but I get
<!-- SHTML Wrapper - 500 Server Error -->
[an error occurred while processing this directive]
This looks like you've got a server side include index page, which is not something that C5 uses.
Have you got a .htaccess file present I wonder? Does it have some url manipulation in it I wonder?
<!-- SHTML Wrapper - 500 Server Error -->
[an error occurred while processing this directive]
This looks like you've got a server side include index page, which is not something that C5 uses.
Have you got a .htaccess file present I wonder? Does it have some url manipulation in it I wonder?
/public_html/.htaccess
/public_html/.htaccess.predirectoryindex
/public_html/concrete/libraries/3rdparty/securimage/database/.htaccess
# The following rules are used by liveSite.
RewriteEngine on
# When the system is accessed from a sub-directory with an Apache alias
# (e.g.http://192.168.0.1/~example/), then you might need to uncomment the line
# below and update it to point to where the system is installed. The system
# will attempt to automatically set the correct value for the line below during
# installation. You might need to comment out the line below once you launch
# your site at a permanent URL without a sub-directory (e.g.http://www.example.com).
RewriteBase /
# The following rule enables search engine friendly URL's for Pages.
RewriteRule ^pages/(.*) livesite/get_page.php?page=$1&%{QUERY_STRING}
# The following rule enables search engine friendly URL's for Files.
RewriteRule ^files/(.*) livesite/get_file.php?name=$1
# The following rule enables the robots.txt file which helps search engines crawl a website.
RewriteRule ^robots\.txt$ livesite/get_robots.txt.php
# The following rule enables the sitemap.xml file which helps search engines find content.
RewriteRule ^sitemap\.xml$ livesite/get_sitemap.xml.php
/public_html/.htaccess.predirectoryindex
/public_html/concrete/libraries/3rdparty/securimage/database/.htaccess
# The following rules are used by liveSite.
RewriteEngine on
# When the system is accessed from a sub-directory with an Apache alias
# (e.g.http://192.168.0.1/~example/), then you might need to uncomment the line
# below and update it to point to where the system is installed. The system
# will attempt to automatically set the correct value for the line below during
# installation. You might need to comment out the line below once you launch
# your site at a permanent URL without a sub-directory (e.g.http://www.example.com).
RewriteBase /
# The following rule enables search engine friendly URL's for Pages.
RewriteRule ^pages/(.*) livesite/get_page.php?page=$1&%{QUERY_STRING}
# The following rule enables search engine friendly URL's for Files.
RewriteRule ^files/(.*) livesite/get_file.php?name=$1
# The following rule enables the robots.txt file which helps search engines crawl a website.
RewriteRule ^robots\.txt$ livesite/get_robots.txt.php
# The following rule enables the sitemap.xml file which helps search engines find content.
RewriteRule ^sitemap\.xml$ livesite/get_sitemap.xml.php
Aha.
This rule means that any url that starts with files/ will get redirected elsewhere.
Comment out that rule (place a # in front) and try again.
RewriteRule ^files/(.*) livesite/get_file.php?name=$1
This rule means that any url that starts with files/ will get redirected elsewhere.
Comment out that rule (place a # in front) and try again.
wow.. thanks a lot...
that's what happens when you install livesite and then uninstall it.. but uninstall decided to leave stuff behind
Thanks again...
that's what happens when you install livesite and then uninstall it.. but uninstall decided to leave stuff behind
Thanks again...
No problem, glad it's working now. :)