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

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By teppo
      This module tracks changes, additions, removals etc. of public (as in "not under admin") pages of your site. Like it's name says, it doesn't attempt to be a version control system or anything like that - just a log of what's happened.
      At the moment it's still a work in progress and will most likely be a victim of many ruthless this-won't-work-let's-try-that-instead cycles, but I believe I've nailed basic functionality well enough to post it here.. so, once again, I'll be happy to hear any comments you folks can provide
      https://modules.processwire.com/modules/process-changelog/
      https://github.com/teppokoivula/ProcessChangelog
      How does it work?
      Exactly like it's (sort of) predecessor, Process Changelog actually consists of two modules: Process Changelog and Process Changelog Hooks. Hooks module exists only to serve main module by hooking into various functions within Pages class, collecting data of performed operations, refining it and keeping up a log of events in it's own custom database table (process_changelog.) Visible part is managed by Process Changelog, which provides users a (relatively) pretty view of the contents of said log table.
      How do you use it?
      When installed this module adds new page called Changelog under Admin > Setup which provides you with a table view of collected data and basic filtering tools See attached screenshots to get a general idea about what that page should look like after a while.
      For detailed installation instructions etc. see README.md.
       


    • By Gadgetto
      Status update links (inside this thread) for SnipWire development will be always posted here:
      2019-08-08
      2019-06-15
      2019-06-02
      2019-05-25
      If you are interested, you can test the current state of development:
      https://github.com/gadgetto/SnipWire
      Please note that the software is not yet intended for use in a production system (alpha version).
      If you like, you can also submit feature requests and suggestions for improvement. I also accept pull requests.
      ---- INITIAL POST FROM 2019-05-25 ----
      I wanted to let you know that I am currently working on a new ProcessWire module that fully integrates the Snipcart Shopping Cart System into ProcessWire. (this is a customer project, so I had to postpone the development of my other module GroupMailer).
      The new module SnipWire offers full integration of the Snipcart Shopping Cart System into ProcessWire.
      Here are some highlights:
      simple setup with (optional) pre-installed templates, product fields, sample products (quasi a complete shop system to get started immediately) store dashboard with all data from the snipcart system (no change to the snipcart dashboard itself required) Integrated REST API for controlling and querying snipcart data webhooks to trigger events from Snipcart (new order, new customer, etc.) multi currency support self-defined/configurable tax rates etc. Development is already well advanced and I plan to release the module in the next 2-3 months.
      I'm not sure yet if this will be a "Pro" module or if it will be made available for free.
      I would be grateful for suggestions and hints!
      (please have a look at the screenshots to get an idea what I'm talking about)
       




    • By apeisa
      Update 31.7.2019: AdminBar is now maintained by @teppo. Modules directory entry has been updated, as well as the "grab the code" link below.
      ***
      Latest screencast: http://www.screencas...73-ab3ba1fea30c
      Grab the code: https://github.com/teppokoivula/AdminBar
      ***
      I put this Adminbar thingy (from here: http://processwire.c...topic,50.0.html) to modules section and to it's own topic.
      I recorded quick and messy screencast (really, my first screencast ever) to show what I have made so far. You can see it from here: http://www.screencas...18-1bc0d49841b4
      When the modal goes off, I click on the "dark side". I make it so fast on screencast, so it might seem a little bit confusing. Current way is, that you can edit, go back to see the site (without saving anything), continue editing and save. After that you still have the edit window, but if you click "dark side" after saving, then the whole page will be reloaded and you see new edits live.
      I am not sure if that is best way: there are some strengths in this thinking, but it is probably better that after saving there shouldn't be a possibility to continue editing. It might confuse because then if you make edits, click on dark side -> *page refresh* -> You lose your edits.
      ***
      When I get my "starting module" from Ryan, I will turn this into real module. Now I had to make some little tweaks to ProcessPageEdit.module (to keep modal after form submits). These probably won't hurt anything:
      if($this->redirectUrl) $this->session->redirect($this->redirectUrl); if(!empty($_GET['modal'])) $this->session->redirect("./?id={$this->page->id}&modal=true"); // NEW LINE else $this->session->redirect("./?id={$this->page->id}");   and...
      if(!empty($_GET['modal'])) { $form->attr('action', './?id=' . $this->id . '&modal=true'); } else { $form->attr('action', './?id=' . $this->id); // OLD LINE }  
    • By Mike Rockett
      Jumplinks for ProcessWire
      Release: 1.5.54
      Composer: rockett/jumplinks
      Jumplinks is an enhanced version of the original ProcessRedirects by Antti Peisa.
      The Process module manages your permanent and temporary redirects (we'll call these "jumplinks" from now on, unless in reference to redirects from another module), useful for when you're migrating over to ProcessWire from another system/platform. Each jumplink supports wildcards, shortening the time needed to create them.
      Unlike similar modules for other platforms, wildcards in Jumplinks are much easier to work with, as Regular Expressions are not fully exposed. Instead, parameters wrapped in curly braces are used - these are described in the documentation.
      Under Development: 2.0, to be powered by FastRoute
      As of version 1.5.0, Jumplinks requires at least ProcessWire 2.6.1 to run.
      View on GitLab
      Download via the Modules Directory
      Read the docs
      Features
      The most prominent features include:
      Basic jumplinks (from one fixed route to another) Parameter-based wildcards with "Smart" equivalents Mapping Collections (for converting ID-based routes to their named-equivalents without the need to create multiple jumplinks) Destination Selectors (for finding and redirecting to pages containing legacy location information) Timed Activation (activate and/or deactivate jumplinks at specific times) 404-Monitor (for creating jumplinks based on 404 hits) Additionally, the following features may come in handy:
      Stale jumplink management Legacy domain support for slow migrations An importer (from CSV or ProcessRedirects) Feedback & Feature Requests
      I’d love to know what you think of this module. Please provide some feedback on the module as a whole, or even regarding smaller things that make it whole. Also, please feel free to submit feature requests and their use-cases.
      Note: Features requested so far have been added to the to-do list, and will be added to 2.0, and not the current dev/master branches.
      Open Source

      Jumplinks is an open-source project, and is free to use. In fact, Jumplinks will always be open-source, and will always remain free to use. Forever. If you would like to support the development of Jumplinks, please consider making a small donation via PayPal.
      Enjoy! :)
×
×
  • Create New...