Jump to content
David Karich

Module: AIOM+ (All In One Minify) for CSS, LESS, JS and HTML

Recommended Posts

On 24.8.2017 at 3:29 PM, DV-JF said:

Hi,

I switched my site to https and now I can't get AIOM to running. Here are the errors I'm getting:


Mixed Content: The page at 'https://****/' was loaded over HTTPS, but requested an insecure stylesheet 'warning: A non-numeric value encountered in /mnt/****/site/assets/cache/FileCompiler/site/modules/AllInOneMinify/AllInOneMinify.module on line 713/work/roltek/site/assets/aiom/css_b863322778056fb524ea6127cc06763c_dev.css?no-cache=1503581072'. This request has been blocked; the content must be served over HTTPS.
(index):1 Mixed Content: The page at 'https://****/' was loaded over HTTPS, but requested an insecure script 'warning: A non-numeric value encountered in /mnt/****/site/assets/cache/FileCompiler/site/modules/AllInOneMinify/AllInOneMinify.module on line 713/work/roltek/site/assets/aiom/js_656d424f993dafdaf7bd972288171ab2_dev.js?no-cache=1503581072'. This request has been blocked; the content must be served over HTTPS.

When I disable AIOM everything works like it should be. Any ideas?

EDIT: 

In order to debug this error I generated a subdomain without HTTPS encription. Now I get the following error:


Warning: A non-numeric value encountered in /***/site/assets/cache/FileCompiler/site/modules/AllInOneMinify/AllInOneMinify.module on line 713
/site/assets/aiom/js_656d424f993dafdaf7bd972288171ab2_dev.js?no-cache=1503583266

EDIT: 

I've figured out, that the error only happens, when I'm using PHP Ver. 7.1. with PHP Ver. 7.0. everything works like it should be. 

 

Many greets, Jens alias DV-JF

I have the same problem. This is the error in Chrome:

[Deprecation] Resource requests whose URLs contained both removed whitespace (`\n`, `\r`, `\t`) characters and less-than characters (`<`) are blocked. Please remove newlines and encode less-than characters from places like element attribute values in order to load these resources. See https://www.chromestatus.com/feature/5735596811091968 for more details.

Does anybody know how to fix this?

//Solution found:

Change the code in "AllInOneMinify.module" in line 713 to:

            $_timestamp = ((int)$_timestamp + $file['last_modified']);

 

  • Like 1

Share this post


Link to post
Share on other sites

I'm thinking of switching from CSS to SCSS in order to use variables. Very useful for example when you want to change colors. Unfortunately the module doesn't minify scss files. Can someone add this feature?

Sorry I'm new to SASS. If I understand correctly I don't need to include a scss file in html.

Share this post


Link to post
Share on other sites

The module supports less, you can also define variables there

Share this post


Link to post
Share on other sites

I really like your module and it is on every site we make.

I found an odd bug when using core page cache and this module; styles not loading correctly and the page looks like there no CSS at all. Most of the sites have no problem, but this happened to maybe five of them. Not very often though. One of them has no page cache, but others do. It's always certain template / page and not the whole site without CSS. All the sites have https on but pages can use both ways.

Share this post


Link to post
Share on other sites

Hello @all

I have a problem with integrating external stylesheets into AIOM.

Screenshot(7).thumb.png.67bb38e62a5e900e66541abc4ab75285.png

I have toggled the checkbox to allow stylesheets from outside the template folder, but I always get the following message:

PHP Warning: file_get_contents(): Filename cannot be empty in .../site/modules/AllInOneMinify/AllInOneMinify.module:596

So it doesnt find the external stylesheet wich is located in /node_modules/cookieconsent/build/cookieconsent.min.css.

This is how I have tried to integrate it:

    $stylesheets = [
      '/node_modules/cookieconsent/build/cookieconsent.min.css',
      'css/main.less'
    ];

echo '<link rel="stylesheet" href="'.\AIOM::CSS($stylesheets).'">' . "\n";

Independent if I change the path to

/node_modules/cookieconsent/build/cookieconsent.min.css or

./node_modules/cookieconsent/build/cookieconsent.min.css or

../node_modules/cookieconsent/build/cookieconsent.min.css

there is no difference.

 

Technical data:

AIOM 3.2.3

PHP 7

PW latest dev

 

Is there something else I am missing?

 

Share this post


Link to post
Share on other sites
On 25.11.2015 at 11:17 PM, Russ Parker said:

Any ideas how to stop it minifying the spaces in CSS calc?

I've the same problem, but found no solution. Can you give me a hint?

Many greets!

Share this post


Link to post
Share on other sites
5 hours ago, Juergen said:

 

Independent if I change the path to

/node_modules/cookieconsent/build/cookieconsent.min.css or

./node_modules/cookieconsent/build/cookieconsent.min.css or

../node_modules/cookieconsent/build/cookieconsent.min.css

there is no difference.

 

Did you try this?

../../node_modules/coo...

 

Share this post


Link to post
Share on other sites
20 hours ago, theo said:

Did you try this?

../../node_modules/coo...

I have tried it with several combinations and also with absolute pathes - no difference. ???

Share this post


Link to post
Share on other sites

Hello all,

I'm experiencing serious issues when using PW built in template cache together wit AIOM.


When a page is loaded from cache and you then change any of your CSS or JS assets, the rebuilding of the combined/minified versions is not being triggered at all. This explains @anttila's problem mentioned above.

Also when you use the button in the module config screen to clear the asset cache, the template caches are not being cleared. So next time a page is loaded from cache, it will point to old asset files that do not exist anymore.

I also did extensive testing with @matjazp's fork. But same problem there.

After looking at the module code, I think that the problem lies in the module hooking into Page::render. But this never gets called once pages are cached. Please correct me if I'm wrong here.


One possible solution would be to hook into PageRender::renderPage instead. This always gets called for every page request and returns a cached version if available or a fresh Page::render.

I forked @matjazp's version as it seems to be the most up to date and will try to fix these issues...

  • Like 1

Share this post


Link to post
Share on other sites

Can anyone tell me please, if I load Processwire from another site using 

require('/home/othersite/public_html/wire/core/ProcessWire.php');
$site = new \ProcessWire\ProcessWire('/home/othersite/public_html/site/');

What do I need to change 

<script src="<?php echo AIOM::JS('script.js') ?>" type="text/javascript"></script>

to, in order to get it to work? At the moment it just causes an error.

Share this post


Link to post
Share on other sites
1 hour ago, cjx2240 said:

At the moment it just causes an error.

Can you tell us the error message?

Share this post


Link to post
Share on other sites
25 minutes ago, zoeck said:

Can you tell us the error message?

I couldn't at first til I realised I needed to enable debug on the central site.

Maybe I just need right folder permissions on the folder where the js goes?

Error: Uncaught exception 'ProcessWire\WireException' with message 'The combined js file can not be written. Check if the script has sufficient permissions.' in /home/othersite/public_html/site/modules/AllInOneMinify/AllInOneMinify.module:483
Stack trace:
#0 /home/newsite/public_html/index.php(315): AllInOneMinify::JS('script.js')
#1 {main}
thrown (line 483 of /home/othersite/public_html/site/modules/AllInOneMinify/AllInOneMinify.module) 

Share this post


Link to post
Share on other sites

Hello,

I always get this warning with Tracy:

PHP Warning: A non-numeric value encountered in .../site/modules/AllInOneMinify/AllInOneMinify.module:713

This is the line of code:

 $_timestamp = ($_timestamp + $file['last_modified']);

It seems that one of the two values is not in the right format.

Best regards

Share this post


Link to post
Share on other sites

HELLO, found that AIOM is not compiling the following code which is pretty annoying, if any one knows of any works around that would be great.

Think i got it working now, for some reason i couldnt see it but might have been a caching issue. 😐

@supports(display: grid) {
    .two-up {
        @media screen and (min-width: @small-screen) {
            display: grid;
        }
    }
}

// edit

was given this by @Christophe which was super useful to anyone using css grid

https://www.smashingmagazine.com/2017/06/building-production-ready-css-grid-layout/

"The challenge is Microsoft Edge, the only modern browser that, as of this writing, still uses the old grid specification. It returns true for @supports (display: grid) {}, even though its grid support is spotty and non-standard. Most relevant for our example is the lack of support for the grid-template-areas and grid-area properties and for the minmax() function. As a result, a feature query targeting display: grid would not exclude Microsoft Edge, and users of this browser would be served a broken layout. To resolve this issue and serve up grid layouts to Microsoft Edge only when the browser gets full support for the specification, target one of the unsupported features instead:

@supports (grid-area: auto) {}

Share this post


Link to post
Share on other sites

Hi,

I'm struggling with AIOM.

I installed this module and now I want to use my less file. In the head I have this, which doesn't work:

<link rel="stylesheet" type="text/css" href="<?php echo AllInOneMinify::CSS('assets/css/main_design.less'); ?>">
or
<link rel="stylesheet" type="text/css" href="<?php echo AllInOneMinify::CSS('assets/css/main_design.css'); ?>">

This f.e. works:

<link rel="stylesheet" type="text/css" href="<?php echo $config->urls->templates?>assets/css/main_design.css" />

The less file has the same styles like the css file. 

 

The source code shows me this:

<link rel="stylesheet" type="text/css" href="&lt;br /&gt;
&lt;b&gt;Warning&lt;/b&gt;:  A non-numeric value encountered in &lt;b&gt;/www/htdocs/w005e302/physio/site/assets/cache/FileCompiler/site/modules/AllInOneMinify/AllInOneMinify.module&lt;/b&gt; on line &lt;b&gt;713&lt;/b&gt;&lt;br /&gt;
/site/assets/aiom/css_a3d1005d4a254bfaf5c76d729e0773fb_dev.css?no-cache=1530095993">

In the AIOM module configurations, the only thing I did, is the activation of the html-minify and the dev-mode.

 

 

Edited by neophron
solved

Share this post


Link to post
Share on other sites

It looks like there is a syntax error in your less file "A non-numeric value encountered"

  • Like 1

Share this post


Link to post
Share on other sites

There could also be an issue with AIOM and PHP 7.x

There are more threads with this issue - see below:

I'd bet you find a solution in them for your problem.

  • Like 1

Share this post


Link to post
Share on other sites

Hi guys,

thanks for the help. It's the php version. With php 7.0 it's ok, all above doesn't work.

Share this post


Link to post
Share on other sites

Glad it works this way.

You might consider using PW ProCache. It does all this minifying and compiling stuff PLUS awesome and reliable caching. It's paid I know but it's worth every cent.

  • Like 1

Share this post


Link to post
Share on other sites
1 hour ago, wbmnfktr said:

Glad it works this way.

You might consider using PW ProCache. It does all this minifying and compiling stuff PLUS awesome and reliable caching. It's paid I know but it's worth every cent.

Thanks for the tip. I'll check this out.

I'm using the ProFields modules and they are worth every penny.

Share this post


Link to post
Share on other sites

Hum, I working on a website, and as soon as I put the website on my server for testing  (OVH, not a dedicated server)  I have an error saying I don't have the permissions to open the js file ... ?  😞

"You don't have permission to access ... /js_ee2fc073cb5c1c887f4d8e31963c7461_dev.js on this server." 

 

 

 

Share this post


Link to post
Share on other sites

Hi,

just found an strange bug. If I activate the »HTML minify« option, a simple gallery (uikit v3) with this structure

<ul class="uk-slideshow-items">
        <li class="uk-active uk-transition-active" style="transform: translateX(0px); z-index: 0;">
        	<img src="/site/assets/files/1080/sample01.jpg" uk-cover="" class="uk-cover" style="width: 1828px; height: 934px;">
        </li>
  		. . .
  		. . .
</ul>

is converting into this structure:

<ul class="uk-slideshow-items">
	<li class="uk-active uk-transition-active" style="transform: translateX(0px); z-index: 0;">
		<strong>
			<strong>
			<img src="/site/assets/files/1080/sample01.jpg" uk-cover="" class="uk-cover" style="height: 0px; width: 0px;">
			</strong>
		</strong>
	</li>
    . . .
    . . .
    . . .
</ul>

 

Does it make sense to count on this module for the future? Cause to me it looks like, as if there is no longer support for this module. 
Are there alternative solutions? 

 github.jpg.1c6222933afa1a5758d7287829943b16.jpggithub.jpg.1c6222933afa1a5758d7287829943b16.jpg

 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By Gadgetto
      SnipWire - Snipcart integration for ProcessWire
      Snipcart is a powerful 3rd party, developer-first HTML/JavaScript shopping cart platform. SnipWire is the missing link between Snipcart and the content management framework ProcessWire.
      With SnipWire, you can quickly turn any ProcessWire site into a Snipcart online shop. The SnipWire plugin helps you to get your store up and running in no time. Detailed knowledge of the Snipcart system is not required.
      SnipWire is free and open source licensed under Mozilla Public License 2.0! A lot of work and effort has gone into development. It would be nice if you could donate an amount to support further development:

      Status update links (inside this thread) for SnipWire development
      2020-07-03 -- SnipWire 0.8.7 (beta) released! Fixes some small bugs and adds an indicator for TEST mode 2020-04-06 -- SnipWire 0.8.6 (beta) released! Adds support for Snipcart subscriptions and also fixes some problems 2020-03-21 -- SnipWire 0.8.5 (beta) released! Improves SnipWires webhooks interface and provides some other fixes and additions 2020-03-03 -- SnipWire 0.8.4 (beta) released! Improves compatibility for Windows based Systems. 2020-03-01 -- SnipWire 0.8.3 (beta) released! The installation and uninstallation process has been heavily revised. 2020-02-08 -- SnipWire 0.8.2 (beta) released! Added a feature to change the cart and catalogue currency by GET, POST or SESSION param 2020-02-03 -- SnipWire 0.8.1 (beta) released! All custom classes moved into their own namespaces. 2020-02-01 -- SnipWire is now available via ProcessWire's module directory! 2020-01-30 -- SnipWire 0.8.0 (beta) first public release! (module just submitted to the PW modules directory) 2020-01-28 -- added Custom Order Fields feature (first SnipWire release version is near!) 2020-01-21 -- Snipcart v3 - when will the new cart system be implemented? 2020-01-19 -- integrated taxes provider finished (+ very flexible shipping taxes handling) 2020-01-14 -- new date range picker, discount editor, order notifiactions, order statuses, and more ... 2019-11-15 -- orders filter, order details, download + resend invoices, refunds 2019-10-18 -- list filters, REST API improvements, new docs platform, and more ... 2019-08-08 -- dashboard interface, currency selector, managing Orders, Customers and Products, Added a WireTabs, refinded caching behavior 2019-06-15 -- taxes provider, shop templates update, multiCURL implementation, and more ... 2019-06-02 -- FieldtypeSnipWireTaxSelector 2019-05-25 -- SnipWire will be free and open source Plugin Key Features
      Fast and simple store setup Full integration of the Snipcart dashboard into the ProcessWire backend (no need to leave the ProcessWire admin area) Browse and manage orders, customers, discounts, abandoned carts, and more Multi currency support Custom order and cart fields Process refunds and send customer notifications from within the ProcessWire backend Process Abandoned Carts + sending messages to customers from within the ProcessWire backend Complete Snipcart webhooks integration (all events are hookable via ProcessWire hooks) Integrated taxes provider (which is more flexible then Snipcart own provider) Useful Links
      SnipWire in PW modules directory SnipWire Docs (please note that the documentation is a work in progress) SnipWire @GitHub (feature requests and suggestions for improvement are welcome - I also accept pull requests) Snipcart Website  

       
      ---- INITIAL POST FROM 2019-05-25 ----
       
    • By Sten
      Hello
      Till now I hacked something with the twig template but it works no more with new PW versions so I look forward to create a module. I am working on a site in multiple languages : French, English, Italian, German, Spanish, Portuguese, Hebrew, Russian. The new posts are entered in any language with a field for language. Till now, I got twig files to get the translations with constants defined for each part of the pages.
      So I'd like to create a module to include theses files added according to the url /fr/en/...
      Have you some observations to do before I begin about the direction to take ?
      Thank you
    • By ukyo
      Mystique Module for ProcessWire CMS/CMF
      Github repo : https://github.com/trk/Mystique
      Mystique module allow you to create dynamic fields and store dynamic fields data on database by using a config file.
      Requirements
      ProcessWire 3.0 or newer PHP 7.0 or newer FieldtypeMystique InputfieldMystique Installation
      Install the module from the modules directory:
      Via Composer:
      composer require trk/mystique Via git clone:
      cd your-processwire-project-folder/ cd site/modules/ git clone https://github.com/trk/Mystique.git Module in live reaction with your Mystique config file
      This mean if you remove a field from your config file, field will be removed from edit screen. As you see on youtube video.
      Using Mystique with your module or use different configs path, autoload need to be true for modules
      Default configs path is site/templates/configs/, and your config file name need to start with Mystique. and need to end with .php extension.
      Adding custom path not supporting anymore !
      // Add your custom path inside your module class`init` function, didn't tested outside public function init() { $path = __DIR__ . DIRECTORY_SEPARATOR . 'configs' . DIRECTORY_SEPARATOR; Mystique::add($path); } Mystique module will search site/modules/**/configs/Mystique.*.php and site/templates/Mystique.*.php paths for Mystique config files.
      All config files need to return a PHP ARRAY like examples.
      Usage almost same with ProcessWire Inputfield Api, only difference is set and showIf usage like on example.
      <?php namespace ProcessWire; /** * Resource : testing-mystique */ return [ 'title' => __('Testing Mystique'), 'fields' => [ 'text_field' => [ 'label' => __('You can use short named types'), 'description' => __('In file showIf working like example'), 'notes' => __('Also you can use $input->set() method'), 'type' => 'text', 'showIf' => [ 'another_text' => "=''" ], 'set' => [ 'showCount' => InputfieldText::showCountChars, 'maxlength' => 255 ], 'attr' => [ 'attr-foo' => 'bar', 'attr-bar' => 'foo' ] ], 'another_text' => [ 'label' => __('Another text field (default type is text)') ] ] ]; Example:
      site/templates/configs/Mystique.seo-fields.php <?php namespace ProcessWire; /** * Resource : seo-fields */ return [ 'title' => __('Seo fields'), 'fields' => [ 'window_title' => [ 'label' => __('Window title'), 'type' => Mystique::TEXT, // or InputfieldText 'useLanguages' => true, 'attr' => [ 'placeholder' => __('Enter a window title') ] ], 'navigation_title' => [ 'label' => __('Navigation title'), 'type' => Mystique::TEXT, // or InputfieldText 'useLanguages' => true, 'showIf' => [ 'window_title' => "!=''" ], 'attr' => [ 'placeholder' => __('Enter a navigation title') ] ], 'description' => [ 'label' => __('Description for search engines'), 'type' => Mystique::TEXTAREA, 'useLanguages' => true ], 'page_tpye' => [ 'label' => __('Type'), 'type' => Mystique::SELECT, 'options' => [ 'basic' => __('Basic page'), 'gallery' => __('Gallery'), 'blog' => __('Blog') ] ], 'show_on_nav' => [ 'label' => __('Display this page on navigation'), 'type' => Mystique::CHECKBOX ] ] ]; Searching data on Mystique field is limited. Because, Mystique saving data to database in json format. When you make search for Mystique field, operator not important. Operator will be changed with %= operator.
      Search example
      $navigationPages = pages()->find('my_mystique_field.show_on_nav=1'); $navigationPages = pages()->find('my_mystique_field.page_tpye=gallery');
    • By Robin S
      This is a module I made as an experiment a while ago and never got around to releasing publicly. At the time it was prompted by discussions around using Repeater fields for "page builder" purposes, where the depth feature could possibly be used for elements that would be nested inside other elements. I thought it would be useful to enforce some depth rules and translate the depth data into a multi-dimensional array structure.
      I'm not using this module anywhere myself but maybe it's useful to somebody.
      Repeater Depth Helper
      This module does two things relating to Repeater fields that have the "Item depth" option enabled:
      It enforces some depth rules for Repeater fields on save. Those rules are:
      The first item must have a depth of zero. Each item depth must not be more than one greater than previous item depth. It provides a RepeaterPageArray::getDepthStructure helper method that returns a nested depth structure for a Repeater field value.
      Helper method
      The module adds a RepeaterPageArray::getDepthStructure method that returns a multi-dimensional array where the key is the page ID and the value is an array of nested "child" items, or null if there are no nested children.
      Example

      The module doesn't make any assumptions about how you might want to use the depth structure array, but here is a way you might use it to output a nested unordered list.
      // Output a nested unordered list from a depth structure array function outputNestedList($depth_structure, $repeater_items) { $out = "<ul>"; foreach($depth_structure as $page_id => $nested_children) { $out .= "<li>" . $repeater_items->get("id=$page_id")->title; // Go recursive if there are nested children if(is_array($nested_children)) $out .= outputNestedList($nested_children, $repeater_items); $out .= "</li>"; } $out .= "</ul>"; return $out; } $repeater_items = $page->my_repeater; $depth_structure = $repeater_items->getDepthStructure(); echo outputNestedList($depth_structure, $repeater_items);
       
      https://github.com/Toutouwai/RepeaterDepthHelper
      https://modules.processwire.com/modules/repeater-depth-helper/
    • By MoritzLost
      Cacheable Placeholders
      This module allows you to have pieces of dynamic content inside cached output. This aims to solve the common problem of having a mostly cacheable site, but with pieces of dynamic output here and there.  Consider this simple example, where you want to output a custom greeting to the current user:
      <h1>Good morning, <?= ucfirst($user->name) ?></h1> This snippet means you can't use the template cache (at least for logged-in users), because each user has a different name. Even if 99% of your output is static, you can only cache the pieces that you know won't include this personal greeting. A more common example would be CSRF tokens for HTML forms - those need to be unique by definition, so you can't cache the form wholesale.
      This module solves this problem by introducing cacheable placeholders - small placeholder tokens that get replaced during every request. The replacement is done inside a Page::render hook so it runs during every request, even if the response is served from the template cache. So you can use something like this:
      <h1>Good morning, {{{greeting}}}</h1> Replacement tokens are defined with a callback function that produces the appropriate output and added to the module through a simple hook:
      // site/ready.php wire()->addHookAfter('CachePlaceholders::getTokens', function (HookEvent $e) { $tokens = $e->return; $tokens['greeting'] = [ 'callback' => function (array $tokenData) { return ucfirst(wire('user')->name); } ]; $e->return = $tokens; }); Tokens can also include parameters that are parsed and passed to the callback function. There are more fully annotated examples and step-by-step instructions in the README on Github!
      Features
      A simple and fast token parser that calls the appropriate callback and runs automatically. Tokens may include multiple named or positional parameters, as well as multi-value parameters. A manual mode that allows you to replace tokens in custom pieces of cached content (useful if you're using the $cache API). Some built-in tokens for common use-cases: CSRF-Tokens, replacing values from superglobals and producing random hexadecimal strings. The token format is completely customizable, all delimiters can be changed to avoid collisions with existing tag parsers or template languages. Links
      Github Repository & documentation Module directory If you are interested in learning more, the README is very extensive, with more usage examples, code samples and usage instructions!
×
×
  • Create New...