Macrura

i use that technique from Raymond and i gotta say, it's pure gold!; saved me many times and helped along a project that i thought would be a nightmare to work on (requirement to work on site while it was in use)..

can't figure out how to install lightwire: 1.) Create skins folder in /site/modules/InputfieldCKEditor 2.) upload skin into folder lightwire 3.) add config.skin = 'lightwire'; in confg-body,js but this doesn't work; any help on installing skins would be appreciated!

@adrian - hey thanks for checking in, i actually tried to locate that exchange we had but can't seem to locate it at all.. Yes - i tried to import users with migrator and something i guess went awry with the roles field; it was that all along, so no major database corruption or anything... it's on a sort of a long-term build so it didn't matter that it was broken... hopefully tracking that down might help someone else coming across a similar issue

nice! gonna need one of those soon

Not sure if this was ever solved, but i just solved a 10 month old problem on a site where i had used migrator and finally narrowed down the problem - somehow the 'roles' field itself had lost the specification of the parent of selectable pages (since the roles field is a page field). So i couldn't view the users lister at all. this was causing that exact error message; i studied the database for a while and then went in and enabled system field, and sure enough, the roles field had no parent page specified.. I will try an find my original post in the migrator thread, and mark that as solved at least..

not sure what you mean.. we are making a menu right? so all that matters is the url you want on the menu item, and that is markup. the URL override in my example means that if a URL is entered into that field, it overrides anything selected in the page select. It has nothing to do with processwire pages at all..

that sounds like it would be perfect and exactly what i was hoping for! i can't think of any reason to edit the PW urls; the external link option should be all that is needed; i'll be testing your module over the next week and will report back on that topic. i think for adrianmak's usage, the menu builder module would be a time saver over doing it the old way with page tree, or using a field on the page to override the page's url for menu purposes.

ok - so for the custom menu, the way i did it in the past on many sites was with a hidden branch of the page tree, usually underneath a page called Settings; Most sites i build do require the menu to be very specific and there is absolutely no way that the menu displayed in the front end can be based on the page tree; in my opinion, the page tree being used as the front end menu is only for very small and simple sites; anything more complicated requires you to build your own menu, and now that we have Kongondo's menu module, this is even easier than ever. If you take a look at that module, there may very well be a way to assign a custom URL override to any menu item; i have not tried it yet, but i am planning on using it for the next site i release which is now in admin development. once you have made your menu page tree (yes manually, one by one), and on each of those items selected the page that the menu item will link to, you can use that code to output your menu, and modify it to your needs in terms of menu markup. You can also configure the override field to be always used if it is populated. If you wish to use the page tree as-is to generate your menu, that is pretty much the same thing; you just need a field to override the page's URL in the menu and then use your output code to check if that field is populated and swap out the value of that field with the default URL of the page.

yeah it must be the server, because that theme/template doesn't have anything out of the ordinary in terms of js

you just make a custom menu tree using a menu type template...

hey - not to rain on anyone's module development parade, but i've been scoping instagram widgets on codecanyon, for an existing client/site who requested it, and i seem to have found at least a handful of decent ones.. @benbyf - are there any limitations that would prevent you from using something like that?

sounds strange - which template is it ? sounds like a javascript rewriting the url for a cdn application. or if this is your server then you must have some module or htaccess that is changing those - is this in a subdomain of another site that may have a script running in the root?

in your custom menu pages, you just need to have a menu override.

yeah, sometimes repeaters are quite essential and un-replaceable, as problematic as they are from the api perspective. where possible i try to use profields table, pageTable, multiplier, or textareas; but once in a rare while, those repeaters are good.

@Mike - have you tried disabling the UpgradeCheck module, if you have that installed? I ran into an issue on Sunday night where i couldn't login to admin, and disabling that module let me back in; i got a clue from this warning [05-Apr-2015 22:36:22 America/New_York] PHP Warning: json_decode() expects parameter 1 to be string, array given in /home/user/dev/site/modules/ProcessWireUpgrade/ProcessWireUpgradeCheck.module on line 57

depending on which field is is you could use htmlentities($str, ENT_QUOTES); can you provide more info on the fields you are trying to match?

@peter knight - this always works for me.. include($config->paths->templates . "hannas/minislidegal.php"); this way you can edit your hanna codes right in your ftp/editor...

for the admin you would need to create a module that would check that field, possibly on the buildForm hook; another possibility would be to use AdminCustomFiles and see if there is a way to check the field for empty using JS and then set the value.. but could be risky with JS...

@diogo- check your code.. <a class="home-link" href="/"><img src="/site-plana/templates/styles/images/plana.png"?></a> the extra ? is causing FF to not load that image

@lindquist - any console errors?

@Nico, been meaning to ask you if we could have your template editor check for this module installed and then have a setting or something to use ace extended for template editing; i'm actually already using this with your template editor, but i hacked your module hardcoded to use this inputfield

it's working for me; if i'm logged in, and i go to the root URL, i see processwire. if i logout and click home icon, i see the non-PW site. make sure that you are not already loading the index.html page because if that is loaded, you are already bypassed PW

just logged in and your site is working fine: Here is the reason why you were having problems: - you created a page called /contact/, but in your root folder there is already a directory called /contact/ so processwire would not process that URL because it is an existing dir. - inside that directory, there was no index.html file; so this was causing the server error page to appear. i added an index.html and you can now see the results of that.

If i were you i would make a totally new folder and move everything there, point the domain to the new folder.

if you PM me an admin login, i can at least check the admin to see if there are any obvious issues there;