-
AuthorPosts
-
saganomics Friend
saganomics
- Join date:
- July 2011
- Posts:
- 32
- Downloads:
- 0
- Uploads:
- 11
- Thanks:
- 3
- Thanked:
- 2 times in 1 posts
February 9, 2013 at 8:46 am #184816I am getting the following 500 error when I enable dev mode with T3 blank. This is from the latest github pull.
Cannot create css cached file in development folder: t3-assets/dev
I assure you, it is writable. In fact, it if creating the file, templates.responders.us.less.bootstrap.less.css. I can’t figure out why. If I turn off dev mode it works, but I need to use it. Ideas?
Ninja Lead ModeratorNinja Lead
- Join date:
- November 2014
- Posts:
- 16064
- Downloads:
- 310
- Uploads:
- 2864
- Thanks:
- 341
- Thanked:
- 3854 times in 3563 posts
February 9, 2013 at 6:19 pm #482964With this problem you need to contact system administrator on your hosting to check userweb permisssions and allow write privilege to the folder t3-assets/dev
saganomics Friendsaganomics
- Join date:
- July 2011
- Posts:
- 32
- Downloads:
- 0
- Uploads:
- 11
- Thanks:
- 3
- Thanked:
- 2 times in 1 posts
February 9, 2013 at 6:29 pm #482966Okay. I have solved the issue. I don’t really know how, but I’ll throw out some things that might have affected it:
I adjusted the open_basedir in php.ini; I believe this would have no affect here but inspecting the file I found I didn’t like the setting.
I reinstalled with a slightly changed template package, because I noticed when dumping the variables from less.php in buildCss, the cache file had many dots. My template name had a dot in it, so I thought if there was a explode by dots in the code somewhere it could not read it after writing. That time it worked.Now, do I believe any of that solved the issue? No. It was probably some bonehead maneuver that I overlooked, but at I least I got it resolved.
saganomics Friendsaganomics
- Join date:
- July 2011
- Posts:
- 32
- Downloads:
- 0
- Uploads:
- 11
- Thanks:
- 3
- Thanked:
- 2 times in 1 posts
February 9, 2013 at 6:59 pm #482970<em>@saganomics 359454 wrote:</em><blockquote>Now, do I believe any of that solved the issue? No.</blockquote>
False! It was the dot. Don’t put a dot in you template name if using T3; it hoses the caching mode for dev mode.I ran my clean Akeeba a few times switching from dot to no dot to be sure.
April 11, 2014 at 10:18 am #530538The same problem: http://hugh-jackman.info
I updated T3, and now I have Error 500.
Attributes: 777Help me, please!
arthurjohnston Friendarthurjohnston
- Join date:
- November 2010
- Posts:
- 170
- Downloads:
- 152
- Uploads:
- 16
- Thanks:
- 58
- Thanked:
- 27 times in 2 posts
April 12, 2014 at 3:57 am #530639I receive the same 500 error. I found if closing my browser, then restarting solve the problem. But, if you are in development mode why would you require a cache?
April 12, 2014 at 5:52 am #530642To solve my problem, I replaced all the files in T3 plugin folder with older version of them, and my site began work. Then I replaced all the files with new versions of T3, and the site works without Error 500.
I didn’t manage to re-install plugin, because I got an error, too. So I just replaced the files. -
AuthorPosts
This topic contains 7 replies, has 4 voices, and was last updated by celebrian 10 years, 8 months ago.
We moved to new unified forum. Please post all new support queries in our New Forum