Extension, Plugin

Archived
Forum
(read-only)

Minimee

ExpressionEngine 2

Back to this add-on's main page
View Other Add-ons From John D. Wells

Minimee  >  Thread
     

Minimee Config Variables & Front-End Server Error

General

Sneed's Feed & Seed
Posted: 07 October 2013 02:16 PM
Sneed's Feed & Seed

This is in response to this post: http://devot-ee.com/add-ons/support/minimee/viewthread/8195

I wanted to let you know that I was having a similar problem on Master Config, but just manually re-typing the array didn’t fix the problem. What ultimately fixed it for me was taking the config variables out of the array and making them separate config items:

$env_config['minimee_cache_path'] = $base_path . '/assets/cache';
 $env_config['minimee_cache_url'] = $base_path . '/assets/cache';
 $env_config['minimee_combine_css'] = 'yes';
 $env_config['minimee_combine_js'] = 'yes';
 $env_config['minimee_minify_css'] = 'yes';
 $env_config['minimee_minify_js'] = 'yes'; 

Not sure why that worked when an array wouldn’t, especially considering I’m using arrays for configuration of a couple other add-ons without issue. Anyway, thought it might be helpful for anyone having this problem in the future.

This was happening on WAMP running Apache 2.2 and PHP 5.3.

EE 2.6.1, Minimee 2.1.8.
 
John D Wells
Posted: 11 October 2013 07:16 AM # 1
Developer
John D Wells

Hi Kristen,

While the alternative syntax you’ve noted does work (it’s legacy 1.x formatting), the array syntax does work I can promise.  When you manually re-typed the configuration settings, there still must have somewhere been a hidden character wreaking havoc.

It is caused by the syntax highlighting plugin I’m using in Minimee’s docs, and I’ve finally found a report of the problem:

https://bitbucket.org/alexg/syntaxhighlighter/issue/174/double-click-and-copy-spaces-copied-as-c2

I’ve actually only now been able to find that issue report (apparently my googling skills were poor before!), and it mentions a hidden config to disable the double-click to copy feature that’s causing trouble.  So I’ve at least been able to disable that function.  The downside is that copying code will be more cumbersome, but at least the code can be safely copied to your code without problem.

Cheers,
John
 
Sneed's Feed & Seed
Posted: 25 October 2013 03:30 PM # 2
Sneed's Feed & Seed

**UPDATE: Nevermind, that wasn’t the problem at all. Still investigating…

——————

I figured out what my problem was: my $base_path and $base_url variables had a trailing slash, so the concatenated paths for ‘cache_path’ and ‘cache_url’ had a double slash (/var/www/public_html//cache).

And that apparently freaked Minimee out quite seriously.

FYI.
 
John D Wells
Posted: 26 October 2013 08:12 AM # 3
Developer
John D Wells

Hi Kristen,

Thanks for taking a second look at this.  However I’m fairly confident that the double slashes is not an issue either - Minimee makes a concerted effort to scrub extra slashes from the path & URL values.

Unless - by chance is your $base_url *only* a slash?  Because if your $base_url is just a slash, and then if your $cache_url begins with a slash, when combined that equals two slashes at the start of the URL - at which point it looks like a protocol-relative URL (http://www.paulirish.com/2010/the-protocol-relative-url/), which it is specifically built to support.

If you have the excellent EE Debug Toolbar (http://devot-ee.com/add-ons/ee-debug-toolbar) extension installed, Minimee adds a special debug panel to the Toolbar, where you can easily read each of Minimee’s debug notices, including what it’s attempting to use as it’s base & cache paths & URLs, as well as the status of each file it processes.

If your issue wasn’t the protocol-relative URL possibility, would you be able to copy-and-paste an example of how you are configuring & using Minimee?  I can let you know if I spot anything else that might be causing trouble.

Cheers,
John
 
 
← Template Caching breaks Minimee call_user_func(JSMin::minify) error on production but not local →