adrian

@houseofdeadleg It is working fine in a repeater for me - are you getting any errors (debug mode on?) or can you think of anything unusual about your setup?

Hi Ivan, Thanks for reporting that - it should be fixed in the version I just committed. Please let me know how it goes.

Take a look at this thread: https://processwire.com/talk/topic/1176-hiding-uneditable-pages-from-users/page-2 There are several posts by myself that link to some gists and also an attached module that tackle this from different angles. Regardless you should find something in one of those that will get you sorted out.

Just in case anyone is interested and missed my post in the module's support thread, TableCsvImportExport (http://modules.processwire.com/modules/table-csv-import-export/) now supports all the new options that Ryan added with Table 7-beta - single and multiple page-reference fields and multiple options. Export converts page IDs to the title of the page. Import looks up the titles and populates the table with the IDs of the matching pages

Hi everyone, I have just added support for single and multiple page-reference fields and multiple options - requires PW 2.6.4 and Table 7-beta that Ryan released last week. Export converts page IDs to the title of the page. Import looks up the titles and populates the table with the IDs of the matching pages. Please let me know if you have any problems with this new version.

As a more general response (since you have asked other questions lately about compatibility with other tools - PW can be used in conjunction with just about anything because it doesn't dictate any front-end markup. I use PW together with D3js (and various mapping, charting, visualization tools based on D3) and AngularJS. I have also built sites that use Mapnik (using python) with the resulting maps displayed on a PW site. In some cases I let PW handle the data (use the Profields Table field) and sometimes I write manual DB queries to dedicated database tables (if I am dealing with huge amounts of data). In one case I use some custom scripts to query a database of "big data", run it through some algorithms to analyze and synthesize the data, and then populate a Profields Table with the final values that need to be mapped/charted - in this case the analyses is only run once a year and the queries take too long to do on-the-fly. My point in all that is that you can use PW in many different ways to handle certain aspects of a site and still use other tools to query and analyze the data and/or contribute to the final user interface. Hope that helps to provide some insights about what can be done with PW. That said, if there is no need for content management (text, images), user management etc, and the front-end interface is purely about data analysis and manipulation then you might be better off with custom written server-side code that displays your data on the front-end - maybe even something built on nodejs - maybe meteorjs or a MEAN stack which includes Angularjs. So many options

Advanced mode setting - critical if you hide the settings tab, hence my Github issue.

@apeisa - did you read that issue thread that I linked to? I might be wrong, but in my experience, this occurs when the nameContentTab setting is not on but the settings tab is hidden.

Hi there! This module might be your easiest option: http://modules.processwire.com/modules/simple-contact-form/ There are other modules and you can also build a contact form manually, so let us know if this doesn't suit your needs and we can provide more info.

Thanks for reporting. I have fixed this. I was thinking about disabling the module from affecting any pages under the admin, but thought some users may store some settings type pages, so for the moment I have just excluded pages with the "language" template. Please let me know if you have any problems.

Those settings work for me, but only if ACF and HTML Purifier are also off.

@simplesequence - welcome to PW - sorry for the rough start, but looking at your screenshot I see that you are running v2.3. According to the modules directory, kongondo's blog module isn't compatible with this version. It requires 2.4+ PW's current stable version is 2.6.1. Is there any reason you are running 2.3?

Peter, Some things you'll probably need to add: area[!shape,!coords,!href,!target,alt] map[!name] img[alt,!src,width,height,border,usemap] Also, this imagemap plugin for CkEditor might be useful: http://www.martinezdelizarrondo.com/ckplugins/imagemaps.demo/

Not sure if this is related or not, but for my RestrictTabView module I conditionally added a hidden _pw_page_name field to the Content tab to deal with this: https://github.com/adrianbj/RestrictTabView/blob/master/RestrictTabView.module#L90 There is also this Issue that mentions the problems that can occur in certain configurations: https://github.com/ryancramerdesign/ProcessWire/issues/1048

There is an option for changing the "created" date via the API using quiet mode: $page->created = $timestamp $page->save(array('quiet' => true)); This only works for created though, not modified. This is what I use for modified - make sure you do this after the last $page->save() or it will be overwritten. $sql = "UPDATE `pages` SET `modified` = '".date('Y-m-d H:i:s', $timestamp)."' WHERE `id` = '".$page->id."';"; $update = wire('db')->query($sql);

My preference for app development is for ionic. Like onsen.io (thanks for that link - hadn't seen that one) it is based on Angular, which is an awesome option IMO. Here is a comparison thread: http://forum.ionicframework.com/t/pros-cons-vs-onsen-ui/8177 Here are some useful links about setting up and publishing with Ionic and Cordova (the open source codebase that phonegap runs on). http://ionicframework.com/docs/guide/publishing.html https://coderwall.com/p/vvkyra/getting-started-with-ionic If you're on Windows, Phonegap Build (build.phonegap.com) should get you through all the issues of building for iOS without a Mac.

Hi @holmescreek and welcome to the forums. What you need to do is define a separate role - perhaps called "deletor" and give it edit and delete permissions. Now remove the delete permission from the main editor role. Now for the pages that you want the delete option to appear on, give their template edit permission for the deletor role. Something like this:

Hi Peter, This was the first module I ever put together and I still haven't really finalized it - I have it working on a few sites, but it really needs some configuration options - what images field to use, what pages of the PDF to create images for, etc. You might be better off with this module by Richard Jedlička: https://processwire.com/talk/topic/6426-pdf-fieldtypeinputfield/ although since it is a separate fieldtype you might have a little trouble migrating your content from your existing files field. If that is an issue, perhaps just tweak the code in this module of mine to suit your needs, because it sounds like you don't want images for every page, just the cover. Let me know if there is anything I can do to help.

Can you provide the code for the entire module for us to see? Do you have debug mode on? Any errors?

The markup module that comes along with kongondo's blog module is just there as a helper - there is no requirement to use it. Just don't use it and write your own markup - either steal from the markup module, or from Ryan's blog profile as a starting point.

Hey kongondo - I have just started using this on a site for the first time - it is going to be awesome! The one thing I would like to be able to do though is have better control over the row/column selectors. What I need to do is be able to limit the matches to children of the current page because I will be using this field on several page trees on the site that have the same structure, so a template selector will grab all these pages, not just the one under the current parent. I think if the PW core supported 'page' as an argument that could be used for the parent selector I'd be OK. parent=page, template=rows_template Perhaps your module could have an extra config settings to limit to the current page? Or perhaps an option to use custom php code to find the pages - like you can when defining a page field. Is that something you'd be willing to support? Any other thoughts on how to make this work? Thanks again for your work on this! PS Another feature suggestion - any chance of adding a browser warning alert for the reset button? I know that nothing is actually lost until the page is saved, but I bet some users will think they have lost everything already and start typing again, not realizing they can simply reload the page. Maybe the button could also be named "Clear Data" or something more descriptive than "Reset". My thoughts continue I am not sure how to handle this, but I have a checkbox field on each of the pages that make up the columns - this is to determine whether the page should actually be included in the table. The thing I worry about is someone unintentionally unchecking this which will result in data loss the next time the page with the Matrix table field is edited and saved. Other than a warning in the description/notes of the checkbox field, I am not sure how to protect against this. Could you module perhaps warn when rows/column are about to be discarded - with an alert that actually says which ones are being deleted from the matrix table? Any other ideas? Also, what about an API method to create data - it would be nice to make it easier to create an import routine from an existing database.

Thanks SiNNuT - I really appreciate you letting me know that you're finding it so useful.! I hope you'll also like the next little enhancement Edit mode now has hidden and unpublished checkboxes:

Not much help, but I just tested your code (slightly modified so I can just paste into admin.php) and it is working fine here in the latest dev version of PW, so I think you must have something else going on. Can you test on a clean dev install to see if you can help to narrow down the issue?

There is no need to get/find the pages, just use count: $num = wire('pages')->count("parent=/case-references/");

Sorry for all the quick updates, but am using this to populate a huge site and finding new needs so implementing as I go. You can now change the template of each child page in the Edit mode. Because this change happens without warnings, it is controlled by the new "Allow template changes" setting in the module config. Of course the ability to change templates is also additionally controlled by the user's "page-template" permission. Note - you might potentially only want to enable "Allow template changes" while your site is in development and disable once it is live to avoid any disasters. TIP: If you want to change the template for all child pages at once and there are lots of pages, this could still be a little tedious. So instead, use the "Replace" mode, choose the "Child Template" at the top and click Save. This will delete and recreate all child pages with the selected template. This is super fast if the pages don't have any content yet (or child pages of their own), which can often be the case early in development when you are still figuring out which pages will have which templates!