1 users online. Create an account or sign in to join them.Users

Search

I've been running JIT for years and love the extension. Recently, while running Symphony 2.2.2 and JIT 1.10 I started having some funk and assume it's... well me... not you, JIT.

I updated to Symphony 2.2.3 and JIT 1.13, but am having the same apparent issues.

Here's some observations:

  • The Extensions page indicates that JIT is not installed (/symphony/system/extensions/)
  • The Preferences page no longer contains the usual textarea in which I can put safe external sites for images
  • Images on the site that are resized with JIT (e.g. /image/1/64/...) are being resized for sure.
  • When I try to install JIT a) it does not install, b) I get no feedback at the top of the admin page telling me success or failure or that I'm stupid (which might be helpful from time to time).
  • The same is true when I try to uninstall JIT and reinstall it. (i.e., no success in either case)
  • I am able to uninstall/install other extensions as expected

Things I've tried...

  • checking permissions on the manifest folder
  • updating symphony and JIT to current iterations
  • Tequila

Any help you may give is appreciated. I'm stumped.

Here's a screenshot from the extensions page

Again the extension is definitely working, but will not show up as enabled nor does it populate the Preferences page with the textarea allowing me to change the jittrustedsites file through the GUI.

JIT extension not enabled

The most likely cause is that your .htaccess file isn't writable. In fact, I can almost guarantee it.

@designermonkey -- that did it. Kudos and thank you.

@designermonkey -- that did it. Kudos and thank you.

@designermonkey: brilliant!

Could someone please post this as an issue? The extension should check permissions automatically in my eyes.

A try catch is the simplest method for error checking here, but something more verbose would be better.

I had this issue over a year ago, and mentioned it on the forum, yet nothing happened. I agree that we need to fix this now.

Thanks @phoque. Yep, it definitely should check instead of just suppressing the errors...

Thanks @phoque.

I don't see @phoque in this conversation :)

He added the bug to Github.

This discussion is getting multidimensional :)

I'm a ninja, you not seeing me doesn't mean I'm not watching you! :-D

@phoque - Does Allen know about this? -- not the issue but about you being a Ninja?

I sure hope so. I've been enrolled in his Ryu after all. :-)

Create an account or sign in to comment.

Symphony • Open Source XSLT CMS

Server Requirements

  • PHP 5.2 or above
  • PHP's LibXML module, with the XSLT extension enabled (--with-xsl)
  • MySQL 5.0 or above
  • An Apache or Litespeed webserver
  • Apache's mod_rewrite module or equivalent

Compatible Hosts

Sign in

Login details