Macrura

Using this module, in combination with the Template Select module, it is easily possible to show inline related documentation on the edit page. Same setup as above, but adding the template select field on the doc template. could also be further modified to support showing a doc only on a specified page, or children of a page, using selector fieldtype.. example module https://gist.github.com/outflux3/3e76a1338b61d708157c

@cstevensjr - yes, it's super easy, this how i do it... 1.) in site plugins, upload the entire SM2 folder that can be downloaded here: http://www.schillmania.com/projects/soundmanager2/doc/download/ 2.) create an alias variable in the init or in config to the plugins folder, e.g. config: $config->plugins = '/site/plugins/'; or $config->plugins = '/site/templates/plugins/'; or _init $pluginFolder = $config->urls->templates . 'plugins/'; note - this example is using both the player buttons and the bar-ui, thus loading both.. IN THE HEAD <link rel="stylesheet" href="<?=$pluginFolder?>sm2/css/mp3-player-button.css" type="text/css" /> <link rel="stylesheet" href="<?=$pluginFolder?>sm2/css/bar-ui.css" type="text/css" /> in foot <!-- Soundmanager2 ============================================= --> <script type="text/javascript" src="<?php echo $pluginFolder?>sm2/script/soundmanager2-nodebug-jsmin.js"></script> <script type="text/javascript" src="<?php echo $pluginFolder?>sm2/script/mp3-player-button.js"></script> <script type="text/javascript" src="<?php echo $pluginFolder?>sm2/script/bar-ui.js"></script> <script> soundManager.setup({ // required: path to directory containing SM2 SWF files url: '<?php echo $pluginFolder?>sm2/swf/' }); </script> where you want to show the player you can copy the markup from the SM2 examples; for mp3 player buttons you just add the class.. "<a href='{$audio->audio_file->url}' title='{$audio->title} (audio preview)' class='sm2_button tip'></a>";

This is a site for composer, conductor, and NYU composition professor Louis Karchin. http://louiskarchin.com/ The site is based around the works which are presented as a filterable datatable, with inline audio player (soundmanager2).. There is some ajax happening on the works page to pull up details about a work in a popup. a lot of the initial work was importing from the original site as well as from CSV files of the works, so there were various custom import/api scripts used to get all the data in.. As with other recent sites, this site has a admin docs section for reference, as well as inline docs on the edit page, using a simple module based on Nik's page references tab. also this uses the configurable widgets system: and i have an admin page for backups, though the backups run automatically on a cron (using the SmartBackup script): this site benefited from a lot of modules, namely: AdminCustomFiles AdminCustomPages PageDocsTab AdminPageSelectEditLlinks AIOM+ FieldtypeDataStructure FieldTypeTemplates InputfieldSelectExtended HannaCode ProcessRedirects ProcessDiagnostics Profields Table Formbuilder Procache Lister Pro

@Rinaldi, why not try the bitnami stack, make your site and then once it's done come back for some instructions on how to take it live?

@renobird, i would be keen on learning more about having comments as part of an admin page - is it possible to have comments right on an editor page?

@dazzyweb, thanks, this is really cool.

@pwired - so far i have never had to solicit clients.. so far riding the referral chain!

@adrian and diogo - many thanks for looking/commenting! I changed the output and i think it fixed that - thanks for noticing that problem; it was bugging me... was a case of moving the id from the li to the a, so should be correct now.. and thanks to all for checking this out!

This is a recently launched project, proudly powered by Processwire. https://www.bethfalk.com/ Mini Case Study: ...the site was meant to be a quick, simple job, but did get 'interesting' after it started.. The client chose the 'Centum' template, something of a classic by Vasterad (also aval. as a wordpress and drupal theme) but the template had some technical problems and a lot of things were fixed/improved/re-coded. I think this is a great 'theme' for this sort of site.. it's clean and had enough functionality built in to make my job a bit simpler... I'm using the following modules: Admin Custom Files Admin Custom Pages AIOM+ Email Obfuscation Fieldtype DataStructure Profields Table Formbuilder Procache Form Save Reminder Hanna Code (for tabs and accordions) Hanna Code Helper Process Diagnostics Page Lister Pro Site Utilities (custom module, used for populating default slide settings in a table, for homepage slider).. BBCode These topics all relate to functionality that was developed for this project (and some other projects all bundled together during the last 4 months): https://processwire.com/talk/topic/8373-use-delimited-texarea-table-or-yaml-for-settings/#entry81202 https://processwire.com/talk/topic/8635-simple-example-for-widget-management/#entry84623 https://processwire.com/talk/topic/8392-simple-built-in-docs/#entry82915 Other related topics: https://processwire.com/talk/topic/8350-module-fieldtype-yaml/?p=80908 Where possible I tried to use some schema.org microformats; to be continued..

this tutorial shows an application of the field: https://processwire.com/talk/topic/8635-simple-example-for-widget-management/?p=83418 whereby the user is able to select what pages a widget shows on, using a selector, or series of selectors.. so in this scenario, a widget can end up showing under some very complex/flexible circumstances, such as: - all child pages of a particular page - selected pages almost anything you can think of in terms of selecting a page with the selector api

Here's a drop-in paste-in for getting the "view" tab on the edit screen to open in a new window: (put this in your ProcessPageEdit.js ) $(function(){ $('a#_ProcessPageEditView').click(function(){ window.open(this.href); return false; }); });

@everfree.. it would be good to have a definitive module that combines all of the ideas and features needed to have this working in all possible scenarios, and all different page select (asm, autocomplete, list) types.. Being able to set what fields it applies to is probably a much needed feature.. Originally the module I made was borne out of a need on a a site that i'm finishing now, a record label where the albums need to have artists added as pages... but then once you add or create a new artist you need to go right away and do some settings, like type, instruments, bio, sort name etc. so it would have been difficult to go and search for the artist you just added in order to do those settings... I have now used it on 2 additional new projects and implemented it on 3-4 other sites and i do find it pretty much indispensable.., and it will likely be in every site from now on..

@ajben - very nice - some of my 'older' clients would probably benefit from a simpler admin (even though pw admin with Reno is IMHO state of the art..)! Would be willing to contribute, help in any way to push forward alternative admin themes!

@everfree.. did you see my version of this - might be similar.. (yours looks a lot more definitive..) my version is super simple, just enables a feature that as Soma pointed out is already in the core; and then using some jQuery, enables the editing of pages in other types of page selects like autocomplete, page list select etc.. https://processwire.com/talk/topic/8477-adminpageselecteditlinks-module-for-enabling-edit-links-on-multipage-selects/?p=82020

@adrianmak - it would be a standard page set to hidden, on the settings tab; or it also works to put sharrre.php in the root if you don't want to use pw pages..

i only read the last post.. but if you have repeaters and want to output them as pages... i think you may need to use segments, and then in the repeater have a required field for the page name; then in the parent page check for the URL segment1, and compare it to the available repeaters; if it is a match then output the data from the repeater; if not output a 404. you may want to break out your code into some include files, or use functions if you are getting lost in nested stuff; online_tools sounds like a simple case of using the new api for imploding; https://processwire.com/talk/topic/5098-new-wirearray-api-additions-on-dev/?p=49166

@Roope - thanks - really appreciate the reply! Will take a look at the options and come up with a workaround for this site... thanks again for making this module..

@roope - i downloaded the latest version, and replaced it, but it still picks up the retina images, which are marked up like this: <a href="/" class="retina-logo" data-dark-logo="/site/templates/images/lk-logo-dark@2x.png"> i guess there is no way to prevent this sort of thing, because i see in the code that the module will exclude head, images and forms.., but this is a link with a data attribute... but maybe there could be an option to allow the module to only work on parts of the page in a setting, for example, "container classes to apply the obfuscation to", then it would be possible for designers to limit to only specific places in the page, which would reduce the chance of it picking up images with the @ symbol.. thanks..!

@Roope - ok awesome - many thanks ! I will be back on the project soon and will report back..

@Roope - great module! Used on a recent site; And now trying to use it on a new site, but having 2 issues: 1.) There was a point where there was accidentally an email address in the meta description of the site, and that triggered the emo, which broke the page; any way to disable it in the head section? 2.) the emo is triggering on a retina image (@2x in the image name...) Thanks!

@adrianmak, the widget include file should contain all of the necessary markup to render the widget; for example, here is a simple text widget, that is being used in a bootstrap based site: <div class="col-md-4 bottommargin<?=$wClass?>"> <?php echo $widget->body?> <?php if($widget->page_select) { ?> <a href="<?=$widget->page_select->url?>" class="more-link">Read More</a><? } ?> <div class="clear"></div> </div> here's another widget that is being used in a "call to action" <?php $image = $widget->images->first(); $image = $image->width(720); $description = $image->description; $markdown->format($description); ?> <div class="col-md-4 bottommargin <?php echo $widget->widget_type->name?><?=$wClass?>"> <div class="entry clearfix"> <div class="entry-image"> <?php if($widget->page_select) { ?><a href="<?=$widget->page_select->url?>"><?php } ?> <img src="<?=$image->url?>" class="image_fade" alt="<?=$widget->title?>"> <?php if($widget->page_select) { ?></a><?php } ?> <div class="caption"><?php echo $description?></div> </div> <?php if($widget->page_select) { ?> <a href="<?=$widget->page_select->url?>" class="more-link">Read More</a><? } ?> </div> </div>

@pravin, you would have maybe 3 different options, the 1st 2 being server-side: 1.) Create a page called /tag/ or /category/ and then have it accept URL segments; then you would analyze the url segment and use that in a selector to get the pages to show. /tag/css/ (where css is the segment), and then you would use $input->urlSegment1 to tell which pages to get. 2.) use a URL with a querystring, like this: mysite.com/?category=css then use $input->get to build your selector. 3.) have category page that lists all the projects and have filters for category and tag, using e.g. isotope.

you should maybe reference the name which is already the 3 letter code; the title also can be the same uppercase code; where you are echoing you could use a function to convert to the right entity function get_cur_symbol($price,$cur) { $symbol = ''; switch($cur) { case 'USD': return '$'.$price; break; case 'AUD': return 'AU$'.$price; break; case 'CAD': return 'CA$'.$price; break; case 'GBP': return '£'.$price; break; case 'JPY': return '¥'.$price; break; case 'EUR': return '€'.$price; break; case 'CHF': return 'C'.$price; break; case 'CZK': return 'K'.$price; break; case 'DKK': return 'k'.$price; break; case 'HKD': return '圓'.$price; break; case 'HUF': return 'F'.$price; break; case 'SGD': return 'S$'.$price; break; case 'NOK': return 'k'.$price; break; case 'NZD': return '$'.$price; break; case 'PLN': return 'z'.$price; break; case 'SEK': return 'k'.$price; break; } }

@kongondo - truly awesome work! Can't wait to check this out.. i'm sure this has some wide applications.. will report back!

looks like only the footer is loading, no header or body content