Macrura

@Marty - maybe this could help: http://ckeditor.com/forums/Support/Solved-I-cant-embed-tweet-with-the-new-version-4.1.1 also this plugin might be cool: http://ckeditor.com/addon/mediaembed doh! adrian is 1 step ahead

https://processwire.com/talk/topic/8525-cant-import-polymer-elements/

@Peter - how many hanna codes do you usually use on the average site? My usage has been maybe 4-5 hanna codes on a site, or maybe as many as 10 on a really complex/large site; I do think maybe tags could help here on this page in terms of organizing them, but also i don't expect my clients to be interacting with the hanna codes list so this would be more of an admin convenience. sounds trickier than the templates, b/c the hanna codes are used randomly within text areas, or text fields - and are processed at runtime to the output; not that it would be impossible, but it might be a process that needs to run to collect all of that data and could take a lot of processing depending on the # of pages in the site.. I do agree some module to get a "hanna code report" than could generate and be able to process something like 50-100 pages at a time before generating the entire report; this could be very useful, because we might want to see where a particular one is being used; personally I always try and come up with solutions that avoid hanna codes if at all possible and are equally easy and potentially more elegant, and as such i never have more than a handful of hanna codes per site; Perhaps some of your hanna codes could be replaced with other solutions? they are always sort of a risk being that they are inserted into RTE, so not as bulletproof as something like a validated text input.. I always provide complete documentation for all hanna codes including the code itself that can be copied and then usage instructions, using my docs and docs tab system, as well as often inline using the Markup Textareas, so from the end user perspective, they can use any available hanna code right on the page (or also input with the helper module); but i do think that having a description field would be handy, especially if you come back to a project after some time, you could see more easily what each one does, at a glance..

(This is just my opinion and may not be 100% technically accurate, but here it goes) You shouldn't have any issues installing and using processwire, and based on your posts, the only way I can recommend for you to get a clean install is to completely sequester your PW install from all other things on your hosting; so in short: 1.) Create a subdomain from cpanel, and make sure it uses a folder not within any other currently used folder (e.g. not a folder inside your public_html) 2.) setup a new clean database only for PW (for example using mysql database wizard) 3.) upload latest dev of PW into your new subdomain folder 4.) access your subdomain from mysubdomain.mysite.com and run the install post back any errors you see here

sometimes i do wigets with functions, sometimes with render, and sometimes with includes, the latter being explained here: https://processwire.com/talk/topic/8635-simple-example-for-widget-management/

one of the first pieces of wisdom i got from Soma was about making a template from where you can execute api stuff; this is needed on every site, because you'll always need some "api playground" where you can test things and run things to change, add, fix content.. my setup is to have a template called tools, and then a subfolder in the templates where i store all of the scripts that i will run on that tools template, then i just include the one i'm currently using into it and go from there. Sometimes when developing a new part of a live site, i can just clone a template, run it under tools and set the virtual page to anything in the site (example, $page = $pages->get(1012); ) but mostly i'm doing complex imports from other systems like joomla, or from spreadsheets with a lot of custom stuff and dependant/related pages, formatting etc..

@grumpy - right, that is quite a lot of info. Having just now taken a quick look at TNG, both the public and admin demos, i think it would be good to make some points: 1.) The TNG is already it's own CMS of sorts: It has it's own database, admin panel, and it generates a complete frontend website. How this is to be integrated with another CMS is something you have to figure out or plan. Options could include importing all of your TNG data into Processwire, and using it alone as the system for the genealogy; this could be a pretty big task depending on how many of the features of the genealogy system you use. But since you can build just about anything with PW, that is an option. BTW - You may have noticed that there is already a Wordpress integration for it. Not that I would like to steer you away from Processwire, but at the least I think you should look at that option, since it may work 'out of the box'... Processwire itself isn't going to generate any markup for you in terms of the mobile sites, aside from the basic responsive demo frontend it comes with.. Let me know if there are some more specific questions or issues that can be addressed!

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/)