Share this post

Link to post

Share on other sites

# Small NoteInstalling the module via Somas ModulesManager (Lightbox) will only install InputfieldChosenSelect but not InputfieldChosenSelectMultiple. Would be helpful to have a note in the description and/or the error note (if InputfieldChosenSelect is selected for a multi Page Field) that this should be done manually.

Share this post

Link to post

Share on other sites

Updated the module with a newer chosen release (security related) and fixed the hardcoded admin location in the warning about wrongly configured fields.

@kixe

There's already a warning if you're using a multi-page field with the wrong inputfield (because it changed from the first versions of the module). I've added a note about installing it beforehand. But there's also no * in the inputfield select for the field, which should indicate that the inputfield is not meant to be used for a multi page field.

Share this post

Link to post

Share on other sites

That's expected. The chosen library was created to be a seemless enhanced select field (meaning it will be fully useable without js), which is why it does not have any ajax capabilities and therefore has the same problem as all other non ajaxy inputfields when loading a ton of pages.

1

Share this post

Link to post

Share on other sites

Just a heads up that the newest version (ProcessWire 3.0.22 devns) breaks some things, one of which is module settings fields on some modules, this being one of them (the Placeholder Text field will not save any value). (Still looking into the cause and hope to discover fix soon as it also affects my inputfield modules).

**This is now fixed in 3.0.23 devns**

Edited June 26, 2016 by Macruraissue resolved

2

Share this post

Link to post

Share on other sites

suggestion: could you add a css rule that hides the select input right from the beginning? it is hidden afterwards via jquery anyhow but as long as it is visible it leads to some ugly display of the unstyled select field.

Share this post

Link to post

Share on other sites

I fully understand. Hiding the select essentially means the input is unusable if javascript does not work for whatever reason. That's exactly what you want to prevent with any progressive enhancement. It's true, that in the context of the backend it might not be a pressing issue, but I'm not really convinced that showing nothing before js kicks in is much better than showing the original select field. There will always be a layout update.

Share this post

Link to post

Share on other sites

Well you could hide with CSS add a CSS animation to unhide after a few seconds, which would ensure the select to be visible (in theory). Because of the few seconds delay the JavaScript will probably make changes to the DOM so the original select won't be visible. I've used this tecnhique in a site with a loader, to remove the loader even if there's something with JavaScript.

Anyway, I think this kind of FOUC doesn't matter too much in an admin.

Share this post

Link to post

Share on other sites

Is it somehow possible to use this in the frontend? (I'm new to PW, sorry for the question) .

Feature Request: Also, i have the multiple field using pages that have children (nested categories). Would it be possible to visually clarify this relation? Right now all the pages are listed (which is a good thing) but the user can't tell the difference between main categories and sub categories…

BTW, love your module, it's the easiest to use to select relations imho.

Share this post

Link to post

Share on other sites

Is it somehow possible to use this in the frontend? (I'm new to PW, sorry for the question) .

Feature Request: Also, i have the multiple field using pages that have children (nested categories). Would it be possible to visually clarify this relation? Right now all the pages are listed (which is a good thing) but the user can't tell the difference between main categories and sub categories…

BTW, love your module, it's the easiest to use to select relations imho.

Share this post

Link to post

Share on other sites

Frontend editing implies the native processwire functionality for that, not apropos building your own forms;
when you build your own forms you can use any jquery plugins that you want, so you can just load the chosen assets and init the field on your form.

Recently Browsing
0 members

Similar Content

I am trying to make a simple wiredata module that lets me select a page I want all visitors to be redirected to. I have this working in ready.php but then I decided on putting it in a module and I can't get it to work. Here's the relevant bits:
public function ready()
{
$this->addHookBefore('Page::render', $this, 'redirectUsers');
}
public function redirectUsers(HookEvent $e)
{
$page = $e->object;
// The page we want to redirect to.
$redirect = $e->pages->get($this->redirectPage);
if ($page->id == $redirect->id) return; // Prevent infinite loop.
if (!$e->user->isLoggedin()) {
$e->session->redirect($redirect, false); // 'false' indicates 302 temp redirect.
}
}
I left some checks out for simplification. Whenever I'm not on the page that I want to redirect to, an infinite redirect loop starts. Could anybody explain why that is?

I just happened upon something that I think is curious, and I'm wondering if this is default behavior. So help me because I know nothing.
While writing a module, i logged something in wire('log') inside the module's init() function. I was surprised to see that the text was being logged multiple times continuously. So I tried to open a small random module and logged something in its init() function as well, and the same thing happened - the text being logged many times.
My question is, is this supposed to happen? I just want to understand what's going on. My concern is that if I do something huge in the init function, it will get called repeatedly, as with the log, and cause performance issue. Please note that these are both autoload modules. I was expecting them to log at least once when I refresh, but not continuously like what happened.
Please let me know. Thanks.

I am a bit confused, because I don't know how to solve this problem.
When I install the module Languages Support - Page Names, my web falls apart.
I have all the necessary modules installed as Language support for example.
This is the error I get in the admin panel.
Warning: Invalid argument supplied for foreach() in /hosting/www/antoibaprogramming.com/public/wire/modules/LanguageSupport/LanguageSupportPageNames.module on line 107 Warning: Invalid argument supplied for foreach() in /hosting/www/antoibaprogramming.com/public/wire/modules/LanguageSupport/LanguageSupportPageNames.module on line 198 Warning: Invalid argument supplied for foreach() in /hosting/www/antoibaprogramming.com/public/wire/modules/LanguageSupport/LanguageSupportPageNames.module on line 1011 Warning: Invalid argument supplied for foreach() in /hosting/www/antoibaprogramming.com/public/wire/modules/LanguageSupport/LanguageSupportPageNames.module on line 1011 Warning: Invalid argument supplied for foreach() in /hosting/www/antoibaprogramming.com/public/wire/modules/LanguageSupport/LanguageSupportPageNames.module on line 1041
And this in the front-end.
Warning: Invalid argument supplied for foreach() in /hosting/www/antoibaprogramming.com/public/wire/modules/LanguageSupport/LanguageSupportPageNames.module on line 107
Fatal error: Call to a member function get() on null in /hosting/www/antoibaprogramming.com/public/wire/modules/LanguageSupport/LanguageSupportPageNames.module on line 605 Fatal error: Call to a member function get() on null in /hosting/www/antoibaprogramming.com/public/wire/modules/LanguageSupport/LanguageSupportPageNames.module on line 605

The Module Blog for ProcessWire replicates and extends the popular Blog Profile.
Blog is now in version 2.
Please read the README in the Github link below in its entirety before using this module
Blog Documentation is here (Work in Progress!)
See this post for new features in version 2 or the readme in GitHub.
To upgrade from version 1, see these instructions.
##################################################
Most of the text below refers to Blog version 1 (left here for posterity).

Blog version 1 consists of two modules:
ProcessBlog: Manage Blog in the backend/Admin.
MarkupBlog: Display Blog in the frontend.
Being a module, Blog can be installed in both fresh and existing sites. Note, however, that presently, ProcessBlog is not compatible with existing installs of the Blog Profile. This is because of various structural and naming differences in respect of Fields, Templates, Template Files and Pages. If there is demand for such compatibility, I will code a separate version for managing Blog Profile installs.
In order to use the 'Recent Tweets Widget', you will need to separately install and setup the module 'MarkupTwitterFeed'.
Please read the README in the Github link below in its entirety before using this module (especially the bit about the Pages, etc. created by the module).
I'll appreciate Beta testers, thanks! Stable release works fine.
Download
Modules Directory: http://modules.processwire.com/modules/process-blog/
Github: https://github.com/kongondo/Blog
You can also install from right within your ProcessWire install.
Screenshots (Blog version 1)