Leaderboard

Committed an little update and upped version to 1.3.3. - added support for PageArray as the third argument. So instead of the root page you give it an PageArray. https://github.com/somatonic/MarkupSimpleNavigation/blob/master/README.md#build-a-menu-using-a-pagearray-instead-of-a-single-root-page So you can do now something like this to build the top level menu entries, where "navigation_entries" would be a page field for selecting pages. $entries = $pages->get("/")->navigation_entries; echo $treeMenu->render(null, null, $entries); Or this would also be possible $menu = $modules->MarkupSimpleNavigation; // get a PageArray from a simple search $entries = $pages->find("template=basic-page"); $options = array("max_levels" => 1); echo $menu->render($options, null, $entries); @sparrow In your case you could now simply do use your "Top_Navigation" as the third argument. $menu = $modules->MarkupSimpleNavigation; $options = array("max_levels" => 1); echo $menu->render($options, null, $pages->get(1)->Top_Navigation);

Generally: hidden prevents pages from being listed in menus, foreach loops and searches, but if you now the path to the page, you will be able to call it, even when being guest (meaning: not having permission to see unpublished pages). Unpublished means hidden in lists (like mentioned above) AND, for users that do not have the permission to see unpublished pages, inaccessible even via its path/URL. I assume you have that page reference construct built in the backend. There, unless actively changed, you are superuser. "Hidden" pages will appear in such a reference field, "unpublished" ones won't.

IF there is a template file for those pages. Often for select fields I create a Tools template which is just an empty template with no file. That way I can set up things like selects (where I don't want them to be pages on the site) and not worry about anyone guessing the URL. I always set them to hidden. Unpublished implies you're not wanting to use a page yet.

What you are thinking is something that certainly is not wrong and should work fine, and this has also been discussed in the past on this forum. The native forum search isn't the best but if you do a Google search like this 'site:processwire.com/talk single page website' you should get some interesting results. Stuff like this could be good reads for you to get some inspiration: https://processwire.com/talk/topic/1283-a-single-page-site-using-pw/ https://processwire.com/talk/topic/5919-hide-children-of-home-from-indexing-single-page-site/ https://processwire.com/talk/topic/2845-single-page-websites/ https://processwire.com/talk/topic/3036-one-page-website-template-setup/

Update: Apertus is abandoned in favor of a fork of the far more advanced Admin Theme Reno, "SuperReno". Download the current version on GitHub: https://github.com/marcus-herrmann/AdminThemeSuperReno An AdminTheme meant for developers Still en route to an enhanced version of the Knowledge Base Site Profile I'm now releasing an AdminTheme suited for said profile, sharing its design. This is, as usual, an early, not yet heavily tested release. It is intended to be activated for superusers only, since other themes such as Modesta or the default one are much more apt to customers and editors. Requirements Current ProcessWire 2.4.X Developement version A modern browser (but I think that's the last thing a developer is missing) Download | Project on GitHub Features Some of us work on a large number of ProcessWire installations at once. The following options aim to customize your backends to that extent that you can tell them apart within miliseconds and without looking at the URL. Therefore, within the theme's configuration (meaning: the module's settings), you can change the following: Environment indicator When using a development, staging and production version of a project, use this little switch in the theme's setting to indicate which installation you're currently on. Set main color In order to not confuse installations using Apertus, "color brand" them. Use hex, rgb(a), hsl(a), or named CSS values to your liking, but remember to apply a relatively dark color to prevail contrast. Set project name Lastly, name project backends. Shortcuts Search the forums from within every page of your ProcessWire backend Have all the important API documentation links at hand Check for new modules from every page using the tools upper right (refresh icon) Installation Copy all files from the ZIP archive to your /site/modules/ApertusAdminTheme/ directory. Click "Check for new modules" in ProcessWire Admin Modules screen. Click install for the module labeled: "Apertus Admin Theme". Background The design of this Admin Theme is based on my Knowledge Base Site Profile. Also, it is created to accompany a newer version of said Site Profile. This is the first version of Apertus, not yet heavily tested and therefore bleeding edge. Please use with caution. I named it "Apertus" (latin for open, uncovered) because of the default state of the main navigation (Page, Modules, Access,...). This is a pre-release (0.0.1) needing current dev version of PW to prepare for ProcessWire 2.5. Please help me improving the theme by reporting bugs on GitHub. Thanks! Roadmap Things I intend to implement/change in future versions: Making useful links configurable Proper responsive behaviour Refactoring JS Remove Compass dependency when compiling theme's CSS /edit: Added screenshots clarifying where to find theme's settings

Hi, I like to introduce a newly built site to you. http://www.travelinluxury.nl Without Processwire it would have been much more complex to built it. The first left menu you see is not a simple menu but a list of types of trips that are added to all destination pages through the use of a multiselect pagefield. After a click it searches the complete site and selects parts of the world and countries where destinations are to be found with what you selected with final menus to the destinations. With a normal CMS it would have been a real problem to create something like that. The tabbed blocks on the destination pages are built with Jeasyui and in the admin the blocks are separate template fields. Beside that I use the MapMaker Module and FormBuilder (see newsletter and "offerte aanvraag"). Also multilanguage fields (Dutch and German). See the link in the botton (NEDERLANDS - DEUTSCH).. Every page has it's own slideshow for which I used the Jquery cycle plugin with Maximize (thanks my form posts and the suggestion of MadeMyDay...). Check the small cross next to the slideshow controls..... Plus a lot of Jquery and finally pocketgrid for the css grid to make it responsive (tablet only). There are still some little issues, that will be finished the coming weeks. Using Processwire for this site was a learningpass but I enjoyed it much

Looks great and loads fast from Southern California.

I found the answer myself. In the Foundation Site Profile, $useMain is initially set to true in _init.php and checked in _main.php: /templates/_init.php (line 40) /* * Whether to include the _main.php markup file? For example, your template * file would set it to false when generating a page for sitemap.xml * or ajax output, in order to prevent display of the main <html> document. * */ $useMain = true; /templates/_main.php (line 14) // if any templates set $useMain to false, abort displaying this file // an example of when you'd want to do this would be XML sitemap or AJAX page. if(!$useMain) return;

I am doing a module to show tables of contents like widgets. The problem is that I receive the code footer before the tables. Any ideas? Sample: The code: public function ___execute() { $noticias = wire('pages')->find('template=noticia, limit=5'); $salida .= "<table style='width:30%; margin-right: 3%;' class='widget_admin'> <tr> <td colspan='3' class='cabeceraplugin' style='width:100%; background-color:#FF7F50; color:#fff;'><a href='#'><i style='margin-right:10px;' class='fa fa-home'></i>Últimas noticias</a> <a class='crearboton' href='{$config->urls->admin}page/add/?id={$noticia->parentID}'>Crear <i class='fa fa-plus'></i></a></td> </tr><tr>"; foreach($noticias as $noticia) { $salida .= "<td><a href='{$config->urls->admin}page/edit/?id={$noticia->id}'>{$noticia->title}</a></td> <td style='width:5%'> <a href='{$config->urls->admin}page/edit/?id={$noticia->id}'><i class='fa fa-edit'></i></a></br> <a href='{$config->urls->admin}page/delete/?id={$noticia->id}'><i class='fa fa-times'></i></a></td> </tr>"; } return $salida;

Quite an interesting site, I must say. Love the fact that it's just different. With regards to the font, all my browsers are rendering just fine. The issue at hand is with regards to DirectWrite. If it's turned off, it doesn't look so good at all. But, as stated already, it should be on by default now, so the majority of Chrome users will see the correct rendering. With regards to the grey button, that's a silly IE thing that Redmond has never, ever bothered to change. Alternatively, it's the order of your CSS rules. By that, I mean that you are declaring a color for all buttons after you're declaring them for the menu in particular. Still, that seems to be an IE thing, because no other browser has an issue. I think adding !important to the rule for the menu button should fix it. I know, using that flag is bad. But sometimes, you just gotta use it anyway, because it does its job. I find it quite interesting that you chose to use a strike-out on the bottom menu links when viewing a page. Any particular reason why you chose to do that?

Very nice site I just have a few nits to pick from a user experience point of view: The top menus' anchor tags do not fill to the size of their menu blocks <div class="mymenu bn block">...</div> This means that I have to click on the actual anchor link. Whereas, you did this with the menu on the left, making it easier to click on each item. (Only thing I noticed with the left menu is that the anchor tag for "Luxury Honeymoons" goes past the length of the black parent container. Oh, and these links also don't seem to show which one is currently being viewed, i.e a 'current' class.) Same concept with the Top 10 drop down. I should be able to click on any part of that, instead of just the drop down arrow. I think more work could be done with how the site responds to different screen sizes. As soon as I scale down my browser, or use the device renderer, everything starts overlapping everything else. Unless, of course, you did not intend for the site to be responsive, which is what I've gathered. Despite this, I really do like the simplicity and usability of the site. It isn't overly complicated, and anything you need to click on is shown to you straight away, which makes it a friendly site. Kudos!

new german updates for actual PW dev 2.4.13 (16 August 2014). Zip contains only updated/added files (in comparison to the default 2.4 lang pack). updated files: wire--core--inputfield-php.json wire--modules--process--processtemplate--processtemplate-module.json added files: wire--core--fieldgroups-php.json wire--modules--process--processtemplate--processtemplateexportimport-php.json pw-lang-de-dev-update.zip

Here are mr-fan's, manfred62's and diogo's cool solutions https://processwire.com/talk/topic/7298-google-custom-search-for-your-browserbookmarks/

now I made it for Firefox! Take a look at this site: http://www.searchplugins.net/generate.aspx Search URL: https://www.google.com/search?q=site:processwire.com%2Ftalk+TEST Suggestion URL (optional): https://www.google.com/search?q=site:processwire.com%2Ftalk+TEST Search plugin title: ProcessWire Forum Search Icon: uploaded a small copy of the PW favicon result: <SearchPlugin xmlns="http://www.mozilla.org/2006/browser/search/" xmlns:os="http://a9.com/-/spec/opensearch/1.1/"> <os:ShortName>ProcessWire Forum Search</os:ShortName> <os:Description>ProcessWire Forum Search</os:Description> <os:InputEncoding>UTF-8</os:InputEncoding> <os:Image width="16" height="16">data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABAAAAAQCAYAAAAf8/9hAAAAAXNSR0IArs4c6QAAAARnQU1BAACxjwv8YQUAAAAgY0hSTQAAeiYAAICEAAD6AAAAgOgAAHUwAADqYAAAOpgAABdwnLpRPAAAAAlwSFlzAAALEgAACxIB0t1+/AAAARFJREFUOE+lj78vBFEUha8/Y2u9RrOtVrQSlUqrVqlIyCYaGqIQsYVssQ2VKES22yBRkGCtyWQQM3atf+DIh7s/srNidyb55r533znn3TeW267Jsnzje3VlwSYOn/QX+XKg6aNQk6UgVWcIBrFw/qKVy7jN3GnUp7Wp40BpIN64TvpAy4XusZmTUN3MV561+mvcum30BLBnIiZzj82eRQKMSxdvQvQf1q9iMaVhXKy+ave+OTT4jB9vHSWApxpjYz6ofwykGP2c7QeNHg1eW76Jtfn4LkSlsNWurNP23sOD19buEhUeOgEu8EAPomIC9PjAvEHdCZvfeI81Y3uv+8zDzE2jVmNU4CZfD1OtnHwqC1/QKAe2frywFgAAAABJRU5ErkJggg==</os:Image> <os:Url type="text/html" method="GET" template="https://www.google.com/search?q=site:processwire.com%2Ftalk+{searchTerms}" resultDomain="google.com"> </os:Url><os:Url type="application/x-suggestions+json" method="GET" template="https://www.google.com/search?q=site:processwire.com%2Ftalk+{searchTerms}" resultDomain="google.com"> </os:Url><os:Url type="application/opensearchdescription+xml" method="GET" template="http://www.searchplugins.net/createos.aspx?number=81717" rel="self" resultDomain="searchplugins.net"> </os:Url> </SearchPlugin> Then create the plugin and install it in FX. EDIT: give the new plugin in Firefox a keyword (character), so you don't need to change the search. My example character is p. E.g. you type p field dependencies in the adressbar, hit enter --> ready