Jump to content

Wireframe


Recommended Posts

9 hours ago, adrian said:

@teppo - that looks to have fixed that issue. Something else I have just noticed is this when viewing the Wirefame module settings, although this probably isn't PHP 8 related.

image.thumb.png.85362985d3b7da762a68dc9234ad0590.png

Thanks — this is now fixed as well 🙂

  • Like 1
Link to comment
Share on other sites

  • 1 month later...

Good day, @teppo!

There is a rather empty Patterns and practices section in the docs. I got a suggestion for what to put there. Or should it be in examples? Anyway...

Could you describe how does the template with a controller handle get variables and/or url segments? I do not quite understand that, as I have no prior experience with general purpose frameworks.

  • Like 2
Link to comment
Share on other sites

  • 4 months later...

@teppo

Hi and thanks for the great tool!

Have a small issue with $persistent_cache_name in the current implementation it's not language-aware. Maybe it worth changing it to something like

$persistent_cache_name = 'Wireframe/MethodProp'
  . '/' . $context
  . '/' . static::class
  . '/' . $name
  . '/' . $this->wire('page');

if($this->wire()->modules->isInstalled("LanguageSupport")) {
  $current_language = $this->wire()->user->language;
  $default_language = $this->wire()->languages->getDefault();

  if ($current_language !== $default_language) {
    $persistent_cache_name .= . '/' . $current_language->id;
  }
}

or even move out to a separate hookable method, so we can tune names if needed. 

  • Like 1
Link to comment
Share on other sites

19 minutes ago, Mats said:

Fatal Error: Uncaught Error: Class 'Wireframe' not found in site/templates/layouts/default.php:12

That's a strange one. A couple of checks first:

  • Does your layout file include the ProcessWire namespace? If not, you'd have to call it via \ProcessWire\Wireframe (though adding namespace is always a good idea).
  • Which version of Wireframe do you have installed?

 

  • Like 1
Link to comment
Share on other sites

No, the layout did not include the ProcessWire namespace. I will try that.  

The version is 0.20.2

The namespace solved it. Was pretty sure i tested that, but must have missed it.

Thanks Teppo!

  • Like 1
Link to comment
Share on other sites

Version 0.21.0 released:

### Added
- Hookable method MethodPropsTrait::getMethodPropCacheName(string $name, string $context). Note that when hooking into this method one should refer to the object that implements the trait, such as a specific Controller class.

### Changed
- Include language ID in persistent cache name generated by MethodPropsTrait for cacheable methods.

@Zeka, thanks for bringing the lack of multi-language support for cache names up. While testing I noticed that a site I've been working on recently was in fact also affected. Not a huge deal in this case but it could've caused some confusion.

For the record: I ended up just adding the language ID to the key. If LanguageSupport is not installed it'll be a blank value, but that doesn't really matter 🙂

  • Like 2
Link to comment
Share on other sites

@teppo Thanks for the update.

I'm migrating a live site to the Wireframe and I need to set altFilename to wireframe for specific templates on the runtime via hook or somehow else only for superuser role. 

Is there is a way to do that? 

 

Link to comment
Share on other sites

To be honest I've never attempted anything like that 🙂

Just did a quick test and something along these lines might work — though I'd highly recommend testing first in a non-production environment:

if ($user->isSuperuser()) {
    $wire->addHookBefore('ProcessPageView::execute', function(HookEvent $event) {
	    foreach ($event->templates->find('name!=admin') as $template) {
            $template->filename = 'wireframe.php';
	    }
        $event->removeHook(null);
    });
}

Note: you don't want to set altFilename specifically. I'm not too familiar with how this actually works, but I just tried that, and it seems that ProcessWire is quite keen to save said value (persistently). Managed to break one of my local test sites 😛

(Based on a quick test setting filename seems less problematic.)

  • Like 1
Link to comment
Share on other sites

  • 1 month later...

I'm using the Searchengine module along with Wireframe. When trying to set the view for the ajax return it seems that the default view is called instead. When i add mark up to the default view it shows up in the json.

 if ($this->wire('config')->ajax) {
            // Respond AJAX query with JSON search results.
            $this->view->setLayout(null)->setView('json');
            header('Content-Type: application/json');
            // Return results as JSON.
            $json = $searchEngine->renderResultsJSON([
                'results_json_fields' => [
                    'title' => 'title',
                    'desc' => 'summary',
                    'url' => 'url',
                    'parent' => 'parent.title',
                    'template' => 'template.name',
                    'image' => 'pris_strl_nr_repeater.first.images.first.url',
                    'price' => 'pris_strl_nr_repeater.first.pris'
                ],
                'results_json_options' => JSON_PRETTY_PRINT,
            ]);
            return $json;

        } else {

            // Render search form and results.
            return $searchEngine->render();
        }

 

Link to comment
Share on other sites

Hey @Mats!

Just gave this a try by dropping your code into Search template controller class init method (SearchController::init()) and in my case it worked right out of the box. Where did you place the code? And, just in case, which versions of Wireframe and SearchEngine do you have installed?

In case requested view doesn't exist Wireframe should fall back to the default one (a behaviour I'm no longer entirely sure makes sense, but it's been like that since beginning, so not sure I want to change it either...) so you should also make sure that there definitely is a json.php view file for this template.

Link to comment
Share on other sites

On 7/27/2021 at 10:19 PM, Mats said:

I used the code in a search function like you do in the Wireframe docs site.

Following up on this: after taking a look at that example I've realized that... it doesn't work. Thanks for pointing this out — I should probably fix it to avoid any further confusion 😄

In this case the search method of the controller class disables layout and attempts to change the view. First one is doable (layout is rendered after the view), but the second one isn't, since at this point we've already rendered the view (search method is called in the view, after all). Instead this should be done in the init method (triggered as soon as a controller class is loaded) or the render method (triggered when a page using that controller gets rendered). The distinction between init and render usually doesn't matter 🙂

  • Like 1
Link to comment
Share on other sites

Hi @teppo!

I'm trying to use Ryans Functional field on a Wireframe site like this in the home view: 

<?= __text('Email') ?>

But i get an error:

#0 wire/core/TemplateFile.php (327): require()
#1 site/modules/Wireframe/lib/View.php (84): TemplateFile->___render()
#2 wire/core/Wire.php (414): Wireframe\View->___render()
#3 wire/core/WireHooks.php (951): Wire->_callMethod('___render', Array)
#4 wire/core/Wire.php (485): WireHooks->runHooks(Object(Wireframe\View), 'render', Array)
#5 site/modules/Wireframe/Wireframe.module.php(799): Wire->__call('render', Array)
#6 wire/core/Wire.php (417): Wireframe->___render(Array)
#7 /Applications/MAMP/htdocs/stellankram (line 19 of site/templates/views/home/default.php)

Do you have any ideas how to get the Functional fieldtype working with Wireframe?

 

/Mats 

Link to comment
Share on other sites

Hey @Mats!

The error itself is not visible there, just the trace, but first things first: did you follow the instructions in the Functional Fields README?

Asking because I just tried this fieldtype for the first time, and was a bit confused at first: I was too hasty and jumped directly to the "using" part of the blog post, where it seemed to suggest that you can just start using __text() etc. in your template files, while in reality you'll need to create a functional field before that or the functions won't work at all. Without a field the fieldtype file won't be loaded, which also means that the functions.php file won't be loaded, and thus __text() etc. will be undefined.

Anyway, let me know if this wasn't the issue. In my quick test the fieldtype seemed to render at least, but I don't have much experience with it otherwise 🙂

Link to comment
Share on other sites

Right, here is the error: 

Fatal Error: Uncaught Error: Call to undefined function __text() in site/templates/views/home/default.php

I have created and added the field to the template.

When i call the field with $page->myfuncfield it outputs FunctionalWireData.

Link to comment
Share on other sites

2 hours ago, Mats said:

Right, here is the error: 

Fatal Error: Uncaught Error: Call to undefined function __text() in site/templates/views/home/default.php

I have created and added the field to the template.

When i call the field with $page->myfuncfield it outputs FunctionalWireData.

We can rule the missing field issue out, so next question: does your view file have the ProcessWire namespace?

If not, try adding it. Or refer to the __text() method as \ProcessWire\__text().

  • Like 1
Link to comment
Share on other sites

This solved it: \ProcessWire\__text(' Your email', 'email');

I tried to add namespace ProcessWire earlier but got an error that it had to be added at the beginning of the file. 

Thanks @teppo!

Edit: Seems like the field doesn't show up in the editor. The field (label is showing) is there but no field to edit. 

Link to comment
Share on other sites

9 hours ago, Mats said:

This solved it: \ProcessWire\__text(' Your email', 'email');

I tried to add namespace ProcessWire earlier but got an error that it had to be added at the beginning of the file.

That's a strange one, unless of course the namespace declaration wasn't the very first thing in the file, right after the first PHP open tag. It should work fine in view files — in fact I always add the namespace to view files, just in case 🙂

Calling the method via ProcessWire namespace is fine, just a bit verbose.

9 hours ago, Mats said:

Edit: Seems like the field doesn't show up in the editor. The field (label is showing) is there but no field to edit. 

My guess: you'll have to modify the "file mode" setting of the functional field, selecting your view file(s) there. By default functional fields is set to look for function calls from the template file, which means that it won't show up in the editor if it's placed in any other file, including files included/required from the template file etc.

Link to comment
Share on other sites

Actually I have exactly the same problem. Seems to be a quite new bug as it works on all old pages but I get the error message the moment I create a new one... There are ALWAYS problems with this paid modules, probably to force us to pay the access fee to this forum. As much as I loved processwire in the beginning (buying almost all pro modules) the much I started to hate it...

Link to comment
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 MarkE
      This fieldtype and inputfield bundle was built for storing measurement values within a field, rendering them in a variety of formats and converting them to other units or otherwise modifying them via the API.
      The API consists of a number of predefined functions, some of which include...
      render() for rendering the measurement object, valueAs() for converting the value to another unit value, convertTo() for converting the whole measurement object to different units, and add() and subtract() for for modifying the stored value by the value (converted as required) in another measurement. In the admin the inputfield includes a checkbox (which can be optionally disabled) for converting values on page save. For an example if a value was typed in as centimeters, the unit was changed to metres, and the page saved with this checkbox selected, said value would be automatically converted so that e.g. 170 cm becomes 1.7 m.

      A simple length field using Fieldtype Measurement and Inputfield Measurement.
      Combination units (e.g. feet and inches) are also supported.
      Please note that this module is 'proof of concept' at the moment - there are limited units available and quite a lot of code tidying to do. More units will be added shortly.
      See the GitHub at https://github.com/MetaTunes/FieldtypeMeasurement for full details and updates.
    • By tcnet
      File Manager for ProcessWire is a module to manager files and folders from the CMS backend. It supports creating, deleting, renaming, packing, unpacking, uploading, downloading and editing of files and folders. The integrated code editor ACE supports highlighting of all common programming languages.
      https://github.com/techcnet/ProcessFileManager

      Warning
      This module is probably the most powerful module. You might destroy your processwire installation if you don't exactly know what you doing. Be careful and use it at your own risk!
      ACE code editor
      This module uses ACE code editor available from: https://github.com/ajaxorg/ace

      Dragscroll
      This module uses the JavaScript dragscroll available from: http://github.com/asvd/dragscroll. Dragscroll adds the ability to drag the table horizontally with the mouse pointer.
      PHP File Manager
      This module uses a modified version of PHP File Manager available from: https://github.com/alexantr/filemanager
       
    • By tcnet
      This module implements the website live chat service from tawk.to. Actually the module doesn't have to do much. It just need to inserted a few lines of JavaScript just before the closing body tag </body> on each side. However, the module offers additional options to display the widget only on certain pages.
      Create an account
      Visit https://www.tawk.to and create an account. It's free! At some point you will reach a page where you can copy the required JavaScript-code.

      Open the module settings and paste the JavaScript-code into the field as shown below. Click "Submit" and that's all.

      Open the module settings
      The settings for this module are located int the menu Modules=>Configure=>LiveChatTawkTo.

       
    • By tcnet
      Session Viewer is a module for ProcessWire to list session files and display session data. This module is helpful to display the session data of a specific session or to kick out a logged in user by simply delete his session file. After installation the module is available in the Setup menu.

      The following conditions must be met for the module to work properly:
      Session files
      Session data must be stored in session files, which is the default way in ProcessWire. Sessions stored in the database are not supported by this module. The path to the directory where the session files are stored must be declared in the ProcessWire configuration which is by default: site/assets/sessions.
      Serialize handler
      In order to transform session data easier back to a PHP array, the session data is stored serialized. PHP offers a way to declare a custom serialize handler. This module supports only the default serialize handlers: php, php_binary and php_serialize. WDDX was dropped in PHP 7.4.0 and is therefore not supported by this module as well as any other custom serialize handler. Which serialize handler is actually used you can find out in the module configuration which is available under Modules=>Configure=>SessionViewer.

      Session data
      The session data can be displayed in two different ways. PHP's default output for arrays print_r() or by default for this module nice_r() offered on github: https://github.com/uuf6429/nice_r. There is a setting in the module configuration if someone prefers print_r(). Apart from the better handling and overview of the folded session data the output of nice_r() looks indeed nicer.

      Links
      ProcessWire module directory
      github.com
    • By Robin S
      Repeater Easy Sort
      Adds a compact "easy-sort" mode to Repeater and Repeater Matrix, making those fields easier to sort when there are a large number of items.
      The module also enhances Repeater Matrix by allowing a colour to be set for each matrix type. This colour is used in the item headers and in the "add new" links, to help visually distinguish different matrix types in the inputfield.
      Screencasts
      A Repeater field

      A Repeater Matrix field with custom header colours

      Easy-sort mode
      Each Repeater/Matrix item gets an double-arrow icon in the item header. Click this icon to enter easy-sort mode.
      While in easy-sort mode:
      The items will reduce in width so that more items can be shown on the screen at once. The minimum width is configurable in the field settings. Any items that were in an open state are collapsed, but when you exit easy-sort mode the previously open items will be reopened. You can drag an item left/right/up/down to sort it within the items. The item that you clicked the icon for is shown with a black background. This makes it easier to find the item you want to move in easy-sort mode. You can click an item header to open the item. An "Exit easy-sort mode" button appears at the bottom of the inputfield. Configuration
      In the field settings for Repeater and Repeater Matrix fields you can define a minimum width in pixels for items in easy-sort mode. While in easy-sort mode the items will be sized to neatly fill the available width on any screen size but will never be narrower than the width you set here.
      In the field settings for Repeater Matrix you can define a custom header colour for each matrix type using an HTML "color" type input. The default colour for this type of input is black, so when black is selected in the input it means that no custom colour will be applied to the header.
      Exclusions
      The easy-sort mode is only possible on Repeater/Matrix fields that do not use the "item depth" option.
       
      https://github.com/Toutouwai/RepeaterEasySort
      https://processwire.com/modules/repeater-easy-sort/
×
×
  • Create New...