Jump to content
Jonathan Dart

Module: Spex: An asset and template management module

Recommended Posts

I added a toolbar to profile the performance of partials/layouts. Check out the attached screenshot to see what it looks like when the toolbar is open, by default it collapses to just display the totals.

post-1768-0-74476800-1402956868_thumb.pn

  • Like 2

Share this post


Link to post
Share on other sites

noticed on my build of PW 2.4.9 spex white screens if you delete the styles sheet and JS lines in the _init file. 

Share this post


Link to post
Share on other sites

Not sure where this should be addressed, but Spex uses the $config->styles $config->scripts to collect those assets.

But to work with AIOM it needs to be relative to /templates/ folder . But if I want custom modules that for examples adds it's own css to the $config->styles->add() and the path to that will be in the module folder /site/modules/MyModule/MyModule.css it doesn't work. 

Also from time to time third party modules don't happend to have a check if on backend or frontend, and the populate the $config->scripts even on front-end, which results in an error in AIOM.

Wouldn't it be better to have a custom $config->siteScripts $config->siteStyles filearray (same as PW backend) to populate assets? This would be to avoid conflicts.

Share this post


Link to post
Share on other sites

+1 for $config->siteScripts and $config->siteStyles with absolute pathes / urls

Share this post


Link to post
Share on other sites

Hi there,

I've just started to use Spex and am trying to retrofit it to a basic site.

In the <head> section of _base.php, I have the following line:

<?php echo $spex->addStyle($config->urls->templates . 'css/app.css'); ?>

However, the style is not added into the <header>. I've no idea why and would appreciate any thoughts.

Any ideas/help would be much appreciated.

Thanks!

Share this post


Link to post
Share on other sites

Maybe does the example site help that comes with it

https://github.com/jdart/Spex/blob/master/example-site/_init.php#L30

The path for the file is relative to /templates/...  but you got the absolute path.

And you need something like this line to output the styles: here using AIOM (AllInOneMinify) module

https://github.com/jdart/Spex/blob/master/example-site/layouts/_base.php#L16

  • Like 1

Share this post


Link to post
Share on other sites

Hey Soma!

I changed the path to relative and added the AIOM line and bingo, the styles were applied! :)

Many thanks for your insightful and timely help - I really appreciate it!

Cheers.

Share this post


Link to post
Share on other sites

Is this module still maintained cause there's some requests and issues. Kinda sad to not get a response.

Share this post


Link to post
Share on other sites

I hope it is still being maintained, it's a really awesome module that make things very easy.

  • Like 1

Share this post


Link to post
Share on other sites

Is this module still maintained cause there's some requests and issues. Kinda sad to not get a response.

Maybe you can post them on GitHub? There are actually no open issues.

Share this post


Link to post
Share on other sites

Any Info when support for 2.5 is coming? Just tried to update but no luck…

i will not write any dumb post, i will not write any dumb post, i will not write any dumb post

  • Like 1

Share this post


Link to post
Share on other sites

Anyone having troubles with Spex 0.9.9 and Processwire 2.6.10 like addressed here https://processwire.com/talk/topic/8444-modules-crashing-processwire-sites-and-having-other-problems/

That was ProcessWire 2.5.10 mentioned in that post.  We are now at ProcessWire 2.6.1

Make sure you are running PHP version 5.3.8 or higher.  Also make sure that all of your modules are compatible with the ProcessWire version.

Share this post


Link to post
Share on other sites

Oh yes, wrong version, still with 2.6.1 no luck here, still getting 

Compile Error: require(): Failed opening required '/customers/c/c/1/traumawien.at/httpd.www/site/templates/layouts/default.php' (include_path='.:/usr/share/php') (line 186 of /customers/c/c/1/traumawien.at/httpd.www/site/modules/Spex/Spex.module) 

running on PHP 5.6 only with JqueryDataTables, ModulesManager, ProcessBatcher, TextformatterHannaCode, LoginPersist, MarkupSitemapXML, ProcessRedirects, TextformatterVideoEmbed, InputfieldChosenSelect, ProcessWireUpgrade installed.

Any idea?

Share this post


Link to post
Share on other sites

Does you have the folder and file mentioned in the error: site/templates/layouts/default.php? means: does it exist?

AFAIK does SPEX want/need to copy some files during installation to site/templates/layouts/ and in regard of the filesystem settings this may have failed without notice.

But the default files it uses are _base.php and one-column.php, but not default.php.

So, with the template / page you are loading you must have set $spex->setLayout('default');
 

Does that help?

Share this post


Link to post
Share on other sites

Thanks for your help Horst, the problem was that an _init.php file already existed so the layout was nowhere set and the default name for it is of course not one-column, but default.php

Working like a charm now!

  • Like 1

Share this post


Link to post
Share on other sites

Do I have to abandon Spex if I go to Processwire 3? It does not seem to work. Not for me right now anyway.

See this other post.

For all followers: A single line (250) needs to be changed to work with PW 3+.

		$include_fuel ? wire('all')->getArray() : array(),

( see this post: https://processwire.com/talk/topic/12298-update-273-to-308-processwiregetarray-does-not-exist/#entry114410 )

  • Like 2

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 MoritzLost
      This module allows you to integrate hCaptcha bot / spam protection into ProcessWire forms. hCaptcha is a great alternative to Google ReCaptcha, especially if you are in the EU and need to comply with privacy regulations.

      The development of this module is sponsored by schwarzdesign.
      The module is built as an Inputfield, allowing you to integrate it into any ProcessWire form you want. It's primarily intended for frontend forms and can be added to Form Builder forms for automatic spam protection. There's a step-by-step guide for adding the hCaptcha widget to Form Builder forms in the README, as well as instructions for API usage.
      Features
      Inputfield that displays an hCaptcha widget in ProcessWire forms. The inputfield verifies the hCaptcha response upon submission, and adds a field error if it is invalid. All hCaptcha configuration options for the widget (theme, display size etc) can be changed through the inputfield configuration, as well as programmatically. hCaptcha script options can be changed through a hook. Error messages can be translated through ProcessWire's site translations. hCaptcha secret keys and site-keys can be set for each individual inputfield or globally in your config.php. Error codes and failures are logged to help you find configuration errors. Please check the README for setup instructions.
      Links
      Github Repository and documentation InputfieldHCaptcha in the module directory (pending approval) Screenshots (configuration)

      Screenshots (hCaptcha widget)

       
       

       
    • By joshua
      This module is (yet another) way for implementing a cookie management solution.
      Of course there are several other possibilities:
      - https://processwire.com/talk/topic/22920-klaro-cookie-consent-manager/
      - https://github.com/webmanufaktur/CookieManagementBanner
      - https://github.com/johannesdachsel/cookiemonster
      - https://www.oiljs.org/
      - ... and so on ...
      In this module you can configure which kind of cookie categories you want to manage:

      You can also enable the support for respecting the Do-Not-Track (DNT) header to don't annoy users, who already decided for all their browsing experience.
      Currently there are four possible cookie groups:
      - Necessary (always enabled)
      - Statistics
      - Marketing
      - External Media
      All groups can be renamed, so feel free to use other cookie group names. I just haven't found a way to implement a "repeater like" field as configurable module field ...
      When you want to load specific scripts ( like Google Analytics, Google Maps, ...) only after the user's content to this specific category of cookies, just use the following script syntax:
      <script type="text/plain" data-type="text/javascript" data-category="statistics" data-src="/path/to/your/statistic/script.js"></script> <script type="text/plain" data-type="text/javascript" data-category="marketing" data-src="/path/to/your/mareketing/script.js"></script> <script type="text/plain" data-type="text/javascript" data-category="external_media" data-src="/path/to/your/external-media/script.js"></script> <script type="text/plain" data-type="text/javascript" data-category="marketing">console.log("Inline scripts are also working!");</script> The type has to be "optin" to get recognized by PrivacyWire, the data-attributes are giving hints, how the script shall be loaded, if the data-category is within the cookie consents of the user. These scripts are loaded asynchronously after the user made the decision.
      If you want to give the users the possibility to change their consent, you can use the following Textformatter:
      [[privacywire-choose-cookies]] It's planned to add also other Textformatters to opt-out of specific cookie groups or delete the whole consent cookie.
      You can also add a custom link to output the banner again with a link / button with following class:
      <a href="#" class="privacywire-show-options">Show Cookie Options</a> <button class="privacywire-show-options">Show Cookie Options</button> This module is still in development, but we already use it on several production websites.
      You find it here: PrivacyWire Git Repo
      Download as .zip
      I would love to hear your feedback 🙂
      CHANGELOG
      0.1.1 Debugging: fixed error during uninstall 0.1.0 Added new detection of async scripts for W3C Validation 0.0.6 CSS-Debugging for hiding unused buttons, added ProCache support for the JavaScript tag 0.0.5 Multi-language support included completely (also in TextFormatter). Added possibility to async load other assets (e.g. <img type="optin" data-category="marketing" data-src="https://via.placeholder.com/300x300">) 0.0.4 Added possibility to add an imprint link to the banner 0.0.3 Multi-language support for module config (still in development) 0.0.2 First release 0.0.1 Early development
    • By bernhard
      --- Please use RockFinder3 ---
    • 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 (pending approval) If you are interested in learning more, the README is very extensive, with more usage examples, code samples and usage instructions!
    • By Craig
      I've been using Fathom Analytics for a while now and on a growing number of sites, so thought it was about time there was a PW module for it.
      WayFathomAnalytics
      WayFathomAnalytics is a group of modules which will allow you to view your Fathom Analytics dashboard in the PW admin panel and (optionally) automatically add and configure the tracking code on front-end pages.
      Links
      GitHub Readme & documentation Download Zip Modules directory Module settings screenshot What is Fathom Analytics?
      Fathom Analytics is a simple, privacy-focused website analytics tool for bloggers and businesses.

      Stop scrolling through pages of reports and collecting gobs of personal data about your visitors, both of which you probably don't need. Fathom is a simple and private website analytics platform that lets you focus on what's important: your business.
      Privacy focused Fast-loading dashboards, all data is on a single screen Easy to get what you need, no training required Unlimited email reports Private or public dashboard sharing Cookie notices not required (it doesn't use cookies or collect personal data) Displays: top content, top referrers, top goals and more
×
×
  • Create New...