All Low add-ons are now owned by EEHarbor. Read the blog post.

Support archive

CSS and JS paths not correct for Reorder

Liam 19 Oct 2010 23:05 problem, complete

Hi,

I've installed reorder 1.0.6 on EE 2.0.1
It all installed fine - but my install doesn't seem to be picking up the correct paths for JS and CSS.

This is the path it is generating for the CSS:

index.php?S=a53c231c6e4cad7b031468f258b211db362685d5&D=cp&C=css&M=third_party&package=home/rwr/Home/public_html/rwr_sites/rwr_nz/system/expressionengine/modules/low_reorder&file=low_reorder

Does that appear correct? I'm guessing I don't have CSS or JS in the correct places - but have tried copying into themes folder etc and it doesn't make a difference.

Can you let me know what the actual location of these files should be so I can check if the files are there.

Thanks
Liam

Replies

  1. Low 20 Oct 2010 04:44

    Hey Liam,

    I cannot reproduce in the current EE version. Can you try and upgrade your EE install? 2.0.1 was a beta, so things changed a bit when 2.1.0 came out...

  2. Liam 20 Oct 2010 04:50

    Hey - sorry I actually meant I was on 2.1 - i.e. the latest.
    I'm sure it is just a path issue? Are you able to tell me where the module install should put the CSS/JS and what the correct path is? I can just manually copy the files there if needed..

    Also - does the link above in my first post look correct? i.e. should it have the full file path to the module?

    Cheers

  3. Low 21 Oct 2010 14:19

    Hey Liam,

    The url doesn't seem right, no. Instead of the full path, it should only show "package=low_reorder". The CSS/JS files should stay where they are.

    Have you put the low_reorder folder in the /system/expressionengine/third_party/ directory? It should not go inside the /system/expressionengine/modules/ directory.

    Liam 21 Oct 2010 21:34

    Hi - I tried changing the package path as decribed above and the css/js paths were resolved correctly. So it got me thinking I must have a config issue. It turns out I had uploaded the module it to the module folder - as well as the third party folder - as soon as it was removed from the modules folder it figured the path out correct. Thanks for your help!

  4. Low 1 Nov 2010 07:52

    Cool, glad you got it working, Liam.