Leaderboard

PrevNextTabs Module Github: https://github.com/outflux3/PrevNextTabs Processwire helper modules for adding page navigation within the editor. Overview This is a very simple module that adds Previous and Next links inline with the tabs on the page editor. Hovering over the tab shows the title of the previous or next page (using the admin's built in jqueryUI tooltips.) Usage This module is typically used during development where you or your editors need to traverse through pages for the purpose of proofing, flagging and/or commenting. Rather than returning to the page tree or lister, they can navigate with these links. Warnings If you are using PW version 2.6.1 or later, the system will prevent you from leaving the page if you have unsaved edits. For earlier versions, to avoid accidentally losing changes made to a page that might occur if a user accidentally clicks on one of these, make sure to have the Form Save Reminder module installed. http://modules.processwire.com/modules/prev-next-tabs/

Update: Version 0.1.1 And, we are back! Thanks for waiting! Fixed bug relating to getLanguageValue() (issues #22 and #25). Thanks @all who reported, tested,and fixed the issue. Fixed bug where 'has_children' would not be applied to a menu item whose children were included 'natively'. Switched to $this->wire('pages') from wire('pages') (and similar). As per request at issue #18, added option 'default_class' to enable application of a default CSS class to every menu item at API level. Thanks @jlahijani. You can use this API-level option to add custom CSS class(es), e.g. Bootstrap or Foundation ones.

Modalception for ProcessWire GitHub: https://github.com/thetuningspoon/AdminModalception Direct Download: https://github.com/thetuningspoon/AdminModalception/archive/master.zip Modalception improves the usability of ProcessWire's modal dialog/popup windows when opened from within another modal window. The parent window is expanded to take up the full screen behind it so that additional modals can be opened without the inner windows becoming progressively smaller and less usable. The outer windows' toolbars are hidden from the user to help reduce confusion. * Screencap also features the Page Field Edit Links module

Massive update! As for field templates, how about distinguishing them by templates? For example: body.php for all templates, body-home.php for body field for home template, body-contact.php for th contact template?

If you really want to compile the sass files on the server via PHP, there is http://leafo.net/scssphp/. Only works for scss syntax, though. When you start working with sass/scss, I'd encourage you to follow the already proposed workflow: compile locally -> upload compiled css to server.

ProcessSlider Module (alpha version) Repository https://github.com/mauricius/ProcessSlider Introduction Like many of you, I came to ProcessWire from Wordpress and immediately I fell in love with its power and its clean syntax. I have to say that PW has become my default choice for building websites. However there is only one thing that me and my clients miss from WordPress and is the ability to visually build image sliders through plugins (Nivo, Revolution Slider, LayerSlider, just to name a few). So I decided to create a module for this purpose. ProcessSlider essentialy is an editor for the wonderful Jssor plugin (http://www.jssor.com/) which is absolutely free. The module creates a new page under the Setup menu which allows users to easily add image sliders on the site using an intuitive visual editor. To each slider you can easily add images and other custom and animate them using the transition effects provided by the Jssor slider. The ProcessSlider module in reality is composed by three different modules: ProcessSlider: the main module InputfieldSlider/FieldtypeSlide: allows the user to use an existing slider inside a page MarkupSlider: converts the slider into Jssor compatible markup and optionally provides the necessary initialization script Features Custom slider size Drag and Drop interface Move and resize elements Slides background with images from existing PW pages Slider Preview (with the provided MarkupSlider module) Predefined style classes for Elements Add or remove Slides Add or remove elements Change slide order visually Jssor skins and bullets support Visual Timeline Optional responsive/fullwidth slider Predefined elements: Images, Text, Links, Image as link, Div blocks, Youtube Videos Animation Options (In and Out): Animation type, Delay, Duration The editor is built with Vue.js+Webpack and uses jQuery for D&D and resize functionalities. Release I'm going to release the module in a couple of weeks, there are still some minor tweaks and improvements that I would like to add. Demo Screencast (be sure to watch it at least at 720p) I hope it will be helpful to the community and I would be glad to get feedback or suggestions for improvement! Please also consider that it is my first PW module, so probably I'm missing some best practices, hopefully the most experienced developers can throw me some hints

And for some unbeknown reason such 'invalid' fieldnames still work! Have tested several times. The latest one was last week.

if(in_array($child->id, $dropdown_id_array)){ // echo text + children }else{ // echo link and no children } As long as you want to arbitrarily exclude children from the menu you need to specify the pages with dropdowns in code. You could also use any field value of those pages if there's one for differentiating between dropdown/no-dropdown pages.

can you check the error logs and see if there are any errors? When you say you added some pages to a page, do you mean a page table field? I'll also include the boilerplate troubleshooting below... ----- In order to provide the best chance of help, could you provide the following info: Processwire Version Apache, MySQL & PHP Versions List of installed modules details of any applicable/related errors in your error log (assets/logs/errors.txt) Browser you are using In addition make sure to take the following steps before reporting errors: Upgrade to the latest stable version of PW Upgrade all modules to the current version Install the diagnostics module check that your server environment meets the minimum server requirements Repair database tables address any existing warnings or failures Try increasing your .ini variables like memory, and execution time *Note, if you cannot even run processwire due to WSOD or other fatal error, please try a clean install, and then import the site folder and database, prior to posting issue reports. When reporting errors that happen on a form such as the editor, please open the chrome console, or FF/firebug, and see if there are any network or JavaScript errors. Please report those errors along with your issue.

I replaced $timeFormatJS = str_replace('h24', 'h', $timeFormatJS); with $timeFormatJS = str_replace('hh24', 'HH', $timeFormatJS); in InputfieldDateTime.module (line 160).

I didn't see this thread before, but I came up with an alternate solution to this as well: https://processwire.com/talk/topic/11930-module-modalception/

This one is also worth reading: URL Segments in category tree example: http://wiki.processwire.com/index.php/URL_Segments_in_category_tree_example

They don't have to be configured as hidden/unpublished. It all depends on your use case. You may want to show them (i.e.. Year, Model, etc) as menu sub-dividers for instance. Other than hiding them, If you don't want them to show up in menus, you could also remove them from the returned PageArray prior to outputting your menu.

Don't know if that is possible (I know one can view their liked content though)...How about doing it the 'old-fashioned' way, ctrl-D . I do that often (not just bookmarking threads but posts as well) but also use SearchMark to search through contents of my bookmarks. Edit: Welcome to PW and the forums

What was the question? You used no single >?<.... Ok on the menu thing - Processwire is ment to have this pagetree stuff - so you could build your content in this order and use some kind of Markup Module to create a menu a good menu tool is https://processwire.com/talk/topic/1036-markupsimplenavigation/ You build your own menu builder with a pagefields for example. https://processwire.com/talk/topic/2296-confused-by-pages/ http://wiki.processwire.com/index.php/Page_Field If you mean ProcessMenuBuilder from kongondo i can't find any issue from you. http://modules.processwire.com/modules/process-menu-builder/ Important tip use google to search the forum... https://processwire.com/talk/topic/7298-google-custom-search-for-your-browserbookmarks/ @all after this some tips in german only to make things short ============================================= - Kein Fragezeichen - Keine Frage - Kein Problem - Processwire ist ein wenig anders als andere CMS - Module sind mehr oder weniger nur optional - und nicht wie bei anderen CMS nötig um ans Ziel zu kommen. - Versuche immer exakte Fragen zu formulieren und dein Ziel möglichst genau zu beschreiben. - Verlinke auf verwendete Module und Quellen damit diese nachvollziehbar sind. - Kein Englisch + Deutsch - das sollte ein englisches Supportforum bleiben. - Es wird auch bei schlechtem Englisch geholfen. Best regards mr-fan

I forgott to mention that it shows usefull information directly in the pagetree: total number of pending items and current states of the queues via icons

@Christophe, I am not sure about this module with repeaters, but the built-in field-level access control seems to work great with repeaters. If you have PW 2.6.2+ there is an "Access" tab for each field (in the field's settings) that controls which user roles can see and edit it. Does that take care of your needs?

I really don't know how to help you. Just make sure that $page->get('slider') returns a valid slider ID otherwise it will throw that error because you're trying to render NULL.

I'm starting to think that the documentation is not clear enough on this point, I should definitely add more information. Let's try to explain better how the module works: Create your slider using the module, suppose that this slider is called Slider1. Define a field of type Slider and give it a name. I'm calling it slider. Add this field to an existing template, for example on the home template. Now go to your pages tree and edit the home page. On the slider field select the slider that you want to display on the page. On your template file use the code $page->get('slider') to get the ID of the Slider1 slider, and pass it to the MarkupSlider module.

Perhaps a silly question, but is $page actually the page on which you filled in the Slider1 field?

This kinda works: Default theme: Reno theme: Add this to "/site/ready.php":

This module doesn't work with URLs with format http://www.youtube.com/watch?v=<video-id>, because oembed service doesn't recognize such URLs. I changed in module source the way of building $oembedURL: $videoID = $matches[2][$key]; $oembedURL = "http://www.youtube.com/oembed?url=" . urlencode("http://youtube.com/watch?v=" . $videoID) . "&format=json&maxwidth={$this->maxWidth}&maxheight={$this->maxHeight}";