Martijn Geerts

if $idsToExclude are checkboxes and some are checked then those who are checked are excluded. //$idsToExclude = fieldtype Page, parent=articles, Multiple pages (PageArray) $idsToExclude = $page->pageField; $articlesWithoutExcluded = $pages->find("parent=/articles/, id!=$idsToExclude");

I'm using your theme the whole day. It looks great but feels even better. thank you...

Fijne feestdagen en een gelukkig nieuwjaar voor iedereen!

Good to see other people searching solutions for images. Soma, told somewhere he's using repeaters for images within WYSIWYG. Don't know his solution but like to see what he came up with. Maybe there are more people over here having the same struggle or solved it somehow and want to post their solutions/options about this topic.

Hi Jos, Sorry to hijack your topic. I love to strip out almost all tags in WYSIWYG editors. I don't want to give away the H1 for example. On every project I decide which headers are static set in the templates and which I provide to the editors. What I see is that editor don't think about SEO when typing text. Often I see it happen that editors use <strong> when they mean <h3> or <h4> A year ago, I created a stylesheet for tinyMCE which contains alot of ::after & ::before pseudo classes that contains the explaination of what the tags are. So basicly I could describe: paragraph, main header, sub header, etc.. h2:before { content: 'main header'; position: relative; height: 14px; line-height: 14px; margin: -14px 0 0 0; display: block; etc.... } That way I thought I could trigger an editor to use the proper html tags. I discussed it with a colleague but he didn't liked it. So I never used it in the "real" world. Also a thing where I'm struggling with is images. For some Images they are the most beneficial when they are in the right text content. But as we all know give an editor a few pixels & they will mess up. Last projects I started to automatically create a "photo album" when there are more then a X amount of images on the page & The editor didn't checked the checkbox "don't show album". The fight continues ...

You're doing great jobs over here Jos. I'm glad you joint the community. Just want to shout out my opinion about styling the back-end tinyMCE Setting a site style to tinyMCE is my opinion a bad idea. To mimic it al to almost the same as in the front, can confuse customers who are working with tinyMCE. They aspect the output on the front exactly the same as on the front. If you don't style and leave as it is standard, those expectations won't be there & saves you a lot of time. Proper use of HTML tags is in more important then eye-candy.

One thing I can imagine is to have a second image that can be used as watermark with processwire. I think this is a nice addition. Although I don't know how it should be added.

Search in field(s): name Type of search: Equals (a=b) These settings works for me.

If you add an images field to a template say: "basic" template ( the name is up to you. ) Then, a page using that template wil create a folder in: /site/assets/files/id-of-the-page/ and put those images in that folder. So basically images are attached to a page. ( Not that you ever have to know where the images physical are stored ) To use those in tinyMce, you have to click on the image button. If you want to reuse images, say you want images for a header, storing those images in the home template could be a nice option. Then assumed that your images field called images is populated with images and is the home page, you can get those images in every page like: $home = $pages->get('/'); $imagesArray = $home->images;

Which version you have there? I think there was one version Ryan excluded the users from searches. Searching for users in 2.2.10 is no problem. You even can Limit to template "user" on the advanced panel.

@diogo: +1

just fitchet skunk

Tabs is more easy then you espect: in YourModuleName.js: if($("#YourModuleName-tabs").size()) { $("#YourModuleName-tabs").WireTabs({ items: $("#div-or-form-with-this-id, #an-other-id"), id: 'tabs', rememberTabs: 1 }); } In your module: $this->modules->get('JqueryWireTabs'); $output = "<div id='{$this->className}-tabs'>"; $output .= " <div id='div-or-form-with-this-id'>bladibla</div>"; $output .= " <div id='an-other-id'>content blabla</div>"; $output .= "</div>";

have you set the viewport in the header ? if not, this one works for me: <meta name="viewport" content="width=device-width,initial-scale=1,maximum-scale=1" />

Glad you care about the forum. Thanks Pete.... Shit can happen.

The same trick as fluid video see link diogo. ( the same trick ryan lately have added to videoEmbed ) or: http://css-tricks.co...dWidthVideo.php here's the original I think: http://www.alistapar...tios-for-video/

The input select menu is used on mobile most likely. To turn off js there is just a little harder then on normal desktop environment. So most people don't tough the js setting at all. A solution with a button: wrapping a submit button in a <noscript> tag. Then if javascript is turned off you will see the submit button. ( never done this, but probably work )

Responded again to your post onjegolders. ( 1 more to go again )

Ryan & Apeisa wrote some usefull stuff about it: http://processwire.c...ax-width-issue/

Nice one-liner Nik: "If you’re not embarrassed when you ship your first version you waited too long."

onchange part if you have jQuery: If you have jQuery loaded, this example look nicer I think. ( although your inline js is quicker ) // check if input select exists & stick the onchange part to it if($("#mobile_menu").size() > 0) { $("#mobile_menu").change(function() { window.location = $(this).find("option:selected").val(); }); }

Welcome to the forum ohthanks! I recommend using pages instead. Maybe something like this: product-page - table-page (data-template) - row-page (data-template) - row-page (data-template) - row-page (data-template) - row-page (data-template) - table-page (data-template) - row-page (data-template) - row-page (data-template) - row-page (data-template) - row-page (data-template) - table-page (data-template) - row-page (data-template) - row-page (data-template) - row-page (data-template) - row-page (data-template) fields in the template: - data1 - data2 - data3 - data4 In the table-page (parent) it is used for the headers. The row-page (child) it is used for data. The template doesn't need a file, only used for storing data. Only populated fields in the table-page (parent), filled with header names are used for the table headers Now you know wich fields to use from the child pages. Each child page is a row in your html table. --- For large amount of data, you can use the import CSV to pages module. ---- I like to use the MarkupAdminDataTable. look in: /wire/modules/Markup/MarkupAdminDataTable/MarkupAdminDataTable.module it's straight forward & not that difficult to understand. here some sort of example: $table = $this->modules->get("MarkupAdminDataTable"); $table->setEncodeEntities(false); $table->setSortable(true); $table->headerRow(array('name', 'of', 'header', 'items')); foreach($table as $row) { $table->row(array($row->data1, $row->data2, $row->data3, $row->data4)); } echo $table->render();

If you need all those plug-ins & you bought it & It functions. why the hell you want to change it to processwire ? ( Not that I want to work with an other CMS now a days )

love the hexcode thingy !

Welcome on the forum jayvansantos, Processwire core has cover a lot of things other CMSses need a plug-ins for. The Processwire Api is very wel thought & very straigh forward. If you're explain more, maybe we can help or route you.