Macrura

it's all working well here, got it on 3 live sites, and have tried various different configurations and it looks great

i just wanted to possibly clarify something - there would not be a directory - the admin is a processwire page, using the admin template, so you won't find that as a directory under FTP. this should leave an error_log somewhere on the server, usually - what does that say? i'm also worried about the subdirectory setup; that could be an issue. further it sort of sounds like you are already using a PHP script for your site and are possibly thinking of bootstrapping processwire to make it from hard coded to content-managed? Can you elaborate on which profile you installed? lastly, you might want to consider creating a subdomain where you could temporarily house your processwire site, until it is ready. something like pw.mydomain.com, or dev.mydomain.com and then you would not be using a subdirectory; not that there is anything wrong with using the subdirectory, but you do need to know how to configure that..

not totally sure, but i think you are trying to render a page without a .php template; how would the system know how to render the widget, maybe i'm not seeing your full picture..

@mr-fan, thanks! with my current workload, i think i would start developing the module slowly and project it to be done by end of May or June; so i'll get back in touch!

hey mr-fan - good idea, makes it easier to setup; hoping at some point to improve this whole thing, including how it displays (needs more styling for the text), and bundle it with the page docs tab, as a module...

want to express my deepest gratitude to the PW folks for selecting this as site of the week! As someone who worships PW and all of the developers and contributors alike, it is a tremendous honor to receive this.

@KentBrockman, couldn't you put this into htaccess? # CSS AddType text/css .css

hey quickjeff - maybe you could post your final code, to see how it was adjust for the use case? cheers!

@quickjeff, i'm not using that module, but the code i posted could probably be adjusted to work for it, because as i see in the module description so wouldn't you be able to use that snippet in some form to see if the menu item's page should be output?

I'm using sort of the same function, and although my setup is different (i have a custom menu generated from a branch on the tree) this might help, i use this right after the opening foreach: $menuVis = true; if($child->menu_roles->count()) { foreach($child->menu_roles as $cmr) { $menuVis = false; $cmrRole = wire('roles')->get("$cmr->name"); if (wire("user")->hasRole("$cmrRole") ) { $menuVis = true; break; } } } if($menuVis == false) continue;

@Ivan, many thanks for looking; yes you're right about the 'about'... it will probably get improved - maybe i'll add the default right column there, so it's not such a dead end. the covers on the catalogue should be around 110px... it's all in a datatable, so more utilitarian focused and each in 1 row so i probably wouldn't go with text under cover, especially as i'm trying to conserve vertical space; for the hover state, yeah that's just how it is because they never enforced a cover ratio, so for now it has to be that way... also because the rows need to all be same height... @Pete - yeah, i originally was going to use ajax data source, but i'm using atttibutes on the <td> like data-sort, and data-filter, and couldn't really get my head around how to ajax that..

i think the datatable is fine to load the # of rows maybe up to 100, and it will take a while for them to have that many albums; the page is procached and loads fast here, even with the datatables having to parse that table.. gtmetrix reports a 2.17s load time, and it gets a decent speed score.. the page is currently 647kb which isn't bad considering it is loading almost 15 years worth of releases; i could probably optimize the joins and increase the speed it takes to create the cached version; procache reports 5.1094s to create the page, but there is a ton of processing going on, like each album has hidden columns with the filter data, which are page IDs for stuff like album artist, performers, genres and label..

@mr-fan - what problem are you seeing? does the minified file have any byte order marks? you might need to check the encoding of the js files, or zap gremlins

@MuchDev - thanks for checking this out! Actually there is no connection between the radio player and the pages, but the radio player will only play tracks that have been checked off for that, and then those same tracks also get the radio icon, so that's why you can see which track from the radio player is on any given album page; The catalogue page is just a filterable list of the albums.. there is also a site search and artist listing/search.. @Peter - it definitely seemed like a lot of data when building it... album template does have a lot of fields, and there is more media/info when the press user is logged in.. The catalogue search is really dead simple, a chosen select that are being used to filter the datatable... it was really the most economical way (time/budget) to build a filterable catalogue, and it is all client side filtering, so the whole table loads on that page, though the album covers load on demand based on the datatables redraw callback..

@cstevensjr - thanks for checking it out and for the compliments, most appreciated! @martijn - thanks! yeah i think you're right; it might be annoying the way it is now with the small link icon to open the album.. maybe i need to lose the icon and then make the link be on the .entry-innerwrap as you suggest.. that would leave more room for the text

This site was recently launched and has been running great for the last few weeks. It is probably the largest PW project I have done; there is a lot of media to keep organized, this label has about 70 albums and over 400 artists... http://www.newfocusrecordings.com/ the homepage displays 12 random albums the catalogue page, uses datatables and loads the cover images on demand; the filtering is all done with the datatable, and the urls are updated without page reload... the album page: the pw version replaces a joomla version that was used for about 6 years.. and was a pain to work with; some modules: AdminCustomFiles AdminSaveActions AdminTemplateColumns AIOM+ FieldtypeColorPicker FieldTypeSelectFile (for selecting huge media instead of uploading into PW) FieldtypeTemplates (for selecting which template a certain support doc should show on) FormBuilder FormSaveReminder ImportPagesCSV (used to import some of the data from Joomla and Zoo) InputfieldSelectExtended (used to show additional info after a select action) PageReferencesTab PageTreeAddNewChildsReverse (new albums need to be at top of list) ProcessCustomUploadNames (to ensure the asset naming matches the catalog numbers) PageListerPro ProcessRedirects (for some legacy URLS) ProFields TextformatterBBCode (used for formatting of track and album titles with special characters, superscripts, bold, italic) VersionControl HannaCode SiteUtilities - a custom module that controls many helper functions, read id3 tags, move audio files, rename stuff etc.. some forum threads that relate to this project, and as always thank you to everyone who helped and more generally who take part in the forum! https://processwire.com/talk/topic/8366-setup-sharrre-sharing-widget-in-5-minutes/ https://processwire.com/talk/topic/8392-simple-built-in-docs/ https://processwire.com/talk/topic/8350-module-fieldtype-yaml/ I also work for this label, and have designed about 10 of the covers.. - - - - Special Features: Press View There is a user role called press, and on the user profile, site admins can select certain albums to allow access to for that press user. When the user logs in they can see which albums they have extended access to and then when they view the album there is an extended view and additional media and content. The page audio player will play full streams of the tracks, whereas the public view only plays the edited preview files; the presence of the full stream is indicated with a radio/wave icon.. left widget showing some extra content:

@adrian - not sure - i copied it from that referenced thread, and i had assumed it only applied to the page tree, but i'll try taking out that part and see if it still works..

@Peter - there are 2 drop ins for admin custom files that force the view links to open in new windows (one from the edit and one from the page tree).. pretty much essential for my clients; also you can install the form save reminder (http://modules.processwire.com/modules/form-save-reminder/)

you could also hook into page path and do your custom page name without the trailing slash, so the page references render the correct url;

if you need the view links in the page list to open in new window (which i do on almost every project), got this from here: https://processwire.com/talk/topic/1769-view-in-admin-template/?p=74946 $(document).ajaxComplete(function(){ addtargetblank(); }); function addtargetblank(){ $('li.PageListActionView a').each(function(){ if($(this).attr('target') == undefined){ $(this).attr('target','_blank'); } }); if($('#_ProcessPageEditView').attr('target') == undefined){ $('#_ProcessPageEditView').attr('target','_blank'); } } add to ProcessPageList[something].js

yeah, it's weird because it happens randomly and doesn't leave any error log; once it happens the module no longer appears in the modules list until it is deleted from the database. it also is absent from the cache entries; the issue can be fixed by either deleting the database entry of the module, or adding the entry to the json in the cache; so therein seems to lie the issue, the module is apparently installed to some part of the system (it is in the table), but not in the caches and therefore this conflict causes it to be unavailable as a theme module, so defaults to the backup old admin theme;

the issue happens either way, being set in config or per user; i had to remove the config setting for now, until it gets resolved... definitely a strange issue and that it only seems to blow out the adminthemereno module; though Wanze reported it happening with another module..

i think hanna code does need it's own version of ace, since a lot of people won't use this module; unless it is a really simple one, i mostly do hanna codes as files on the server, so the hanna code just includes the file (thx to soma for this idea); would be cool if i Nico's template editor module could have a setting somewhere to select the inputfield type and then one could set it to use this if it is installed; the use cases for the backend ace editor are many though - definitely people wanting to have a markdown editor could use this... I'm also doing YAML settings field with this.

I was working with someone yesterday on a site and this happened again – this is on a totally different environment than mine (GoDaddy hosting), and using the latest dev. Right after installing a module with modules manager, the whole site flipped back to the pre-module admin; we had to go into the user account and reselect the default theme to get back the core admin module theme;

fyi for anyone testing this out today, ace extended won't work if the initial field is set to collapsed only when blank..