kongondo

Glad it's working. What are the outstanding issues?

I get you and I agree there are options worth highlighting for various use cases

Or for dirt cheap (price of 2 pizzas for single version) buy the Pro Version to support the development of ProcessWire . From jacmaes description, he certainly needs the flexibility ....just sayin'...

Oh yes. I think the video shows an older pro version....There's also the 7 days satisfaction guarantee if you wanna take it for a test run yourself...

Ah, got it working. See instructions here: http://ckeditor.com/ckeditor_4.3_beta/samples/replacebyclass.html The textarea also needs the class 'ckeditor'

Hmmm, doesn't work for me....Editor is not loaded

Whoa! Four lines of code! I have to try this...just for fun...lightning...here I come...

Glad you got it sorted. I don't get the bit about the naming conflicts. What 'areas' are you referring to?

Max, Btw, don't know if you've heard about lightning.pw? https://processwire.com/talk/topic/7400-instant-processwire-dev-hosting-lightningpw/ I mention this just in case if you've tried something multiple times and it still doesn't work, you can always set up a test site there for some other person to have a look. Coupled with Nico's excellent 'Template File Editor' {saved me a couple of times when FTP was down}, one can even view your template files right within your PW Admin.

Your code works for me...Are those child pages 'hidden' or 'unpublished'?

I wasn't suggesting that you would necessarily do the hooks yourself. If you are willing to learn, I'm sure others here would help you get started. Don't feel pressured though

Gabe, If you cannot have those options 'pre-installed' and want to create fields on the fly then you would also need an autoload module of some sort, I think. But I am not sure adding fields that way is the way to go. Maybe something to hook into Page Table field...hmmm...Let's hear what others think

Gabe...let's head over to your original thread...

Are you saying then that your custom module file (the shopping cart) is working with your backed-up database? What I am trying to get at is whether you have definitely isolated the issue to the database and not something to do with your module...I am assuming that you did not alter any PW core files and db tables...(you say you reverted all code both from the site and from PW)

$config->urls->MyModuleClassName; echoing that would return: /site/modules/MyModuleClassName/ http://processwire.com/api/variables/config/ or if you want the URL to your site modules directory. $config->urls->siteModules ...and concatenate as you wish... Change 'urls' to 'paths' if it is the absolute path you want...

They also talk of this

Gabe, See my response in your other post. I don't mean to start two conversations but what I am not clear about is whether if the user selects say 'Towing Capacity' as a page field, you want a value set (e.g. 100Kg) to a different page or to the same page. If to the same page, don't know if you know ProcessWire has a show/if feature for fields? I'll try get the link to a demo video somewhere here on the forums and update this post. How they work is that a field will only be displayed if another field is selected (so go beyond the if empty visibility feature that you reference)... Edit Here you go: Inputfield Dependencies https://processwire.com/api/selectors/inputfield-dependencies/

Hi Deltanic, Welcome to the forums and sorry to hear about your troubles. There's a useful debug guide here: http://processwire.com/docs/tutorials/troubleshooting-guide/ Could you also list the 'after working with some modules' modules? Even with turning 'debugmode' on (true) you still don't get any errors? What about Apache errors? PHP and MySQL versions?

If you want to have the settings on one page trigger some other change in some other page then generally you need a hook, probably in an autoload module that will listen to your pages where the initial change is occurring (basically an 'event') and then dynamically/automatically effect changes in a different page(s). I am not all that with hooks (yet) but others here should be able to guide you . Maybe describe your situation further, e.g. a step-by-step sequence of events as well as exactly what needs changing, e.g. fields need to be populated, pages need to be published, etc...Hope this makes sense

Correct

I see now that according to your first post, you have CKEditor version 1.2.0? No wonder it doesn't work ...I am on PW 2.5 with CKEditor 4.4.3. CKEditor is now the default editor in PW. I think your version is the old one from the modules directory. I urge you to upgrade to PW 2.5 . The extra allowed content in PW 2.5 is a textarea. The code I posted above should be entered just as I have shown. One line of code per line. When you upgrade you will also be able to see the 'Beautify....' settings...

Add the following to your Extra Allowed Content (Input tab when editing your field) table[class](*) tr[class](*) td[class](*) tbody[class](*) em[class](*) br[class](*) What the above mean is that those tags will be allowed and they will also be allowed to have 'classes'. Have a read from here downwards for some quirks with HTML5 Also see the setting Beautify Markup Toggles: helps remove empty <p></p> tags and Btw, why do you need the <em> again? You already have that with CKEditor...Also inbuilt lists work just fine for me...No extra <p> added.

In addition to what Craig said, remember that PW 'users' are also pages that use templates. Those templates can be extended to contain other fields if that's part of the issue here.

Password Fieldtype values are hashed and salted. I am curious, why would you want to find pages using their passwords anyway?

Only other thing I can think of is have you double checked that you have defined $header_image in your _init.php as you stated in you OP? If you haven't, it will fail silently - similar to what you are seeing (or to be precise, not seeing!).