Can't start threads in many cases
I first off wanted to point out that some of the +thread buttons are not working, or at least not for me right now and I can't figure out why.  I am logged in - I could start this thread by clicking on the +New Thread at the top of the list of Threads in the Forum view - but the forum options on the right side (Public Forums, iWiccle Foums, Wiccle Forums) - none of the  +thread buttons work - they highlight but nothing happens when clicked.  And in the Wiccle Forums, I can't start a thread using any of the buttons there.

Edit tools
I also don't see any of the edit tools used to, ie bold text, etc.)?

Anyways - to my questions:

Admin Area skin
Why does the admin area of the website seem to have a different skin than the rest of my site?

{I sent you the login info and you can view the site here: http://174.132.77.99/~rispoli/community until I get it up and running with domain pointed.}

Site Pages
I see that there are several pages created within the site module (I see this simply because there are links at the bottom of the site to About Us, Privacy, etc) - but I can't seem to figure out where to find a list of what pages exist.  Is there one?  Sort of scary to think I could delete a link on the site as reference to a page and then have no way in the future to know what pages are

Also, I see in the admin area under Site/Page Builder that is states:
To edit pages with Wiccle Builder, browse to the page or page type you wish to modify and click the Start Builder link at the top right of the screen. You can create new pages just by typing in the URL you want and starting the builder.  Are you planning a more user-friendly way to do this? (Most if not all of my clients would be intimidated looking at one of the Wiccle URLs and know what that means to "type what URL they want", and likely they would not get it right.

Page Editor not working?
Also, when I did go to the Privacy page to edit the contents, and I selected to "Use Editor", there was no editor - that is, I am hoping there is a WYSIWYG editor?  ...otherwise I can't expect my client to edit content with code in it?  Is this a bug?

Module Description
The module description that appears when the cursor moves over one of the main menu items does not go away when the cursor is moved away.  Can this be changed so that it does?  I see in the code for each menu item there is a command but none for when the mouse moves away.  I personally think it would be nicer to have it go away when the cursor moved away.

Module Associated URL
In the Edit Module pane, there is an "Associated URL". How is that used?  When would that come into play?

The formatting is a bug with this 3rd party editor, we are working on fixing it in the next update. Try use different browser such as Chrome if this happens again as a temp fix. 

Markus will look into these issues and questions as soon as he gets the chance, we are going through a massive change here that will be very good for all members with new updates to both iWiccle, WWB and Wiccle.com. Reading through your questions, we have many of these end-user fixes on the way in the next update as we build the GUI controls to interact with some of the features in the system that can only be done through code. There is alot of power in there, so it's nothing new just the abilities to select them. :) 

These type of questions we love here to help us what you and everyone needs. Also a new Trac system is going to be introduced so you can see what we have in the plans towards the end of the year on both systems.

Thank you Keith, I look forward to the detailed feedback.  

Not knowing what a "massive change" is, can you give me an idea what I am looking at - ie are we talking a day or a week?

Thanks again,

The massive change I was on about is a string on new updates to iWiccle and WWB over the coming months - we have been slow in updates in recent months due to other tasks on the table that are now coming to a close. Other changes include the new Wiccle.com website, and then we want all members to share in the molding of the site during our stage 2 development of it where we are looking at the Community sections / support systems on improvements. Another change to note - we have just moved into a much larger office within Webworks as our expansion continues towards the end of the year as we are break out from the start-up position to extablishment.

Hi David,

As noted in the other thread, I believe a browser hiccup is responsible for this. Do you have javascript turned off by chance? That'd definitely stop the editor from loading and the +Thread links from working. It would also cause the WYSIWYG editor to not load on your site.

On the rest of the questions:

Admin Area skin

The admin area uses the Pro skin to ensure custom skins don't interfere with Admin CP display. If you want to remove this, you can open up /core/config_misc.php and comment out the following lines:

if (!empty($_GET['module']) && $_GET['module'] == "admin")
    $core['init']['default_skin'] = "pro";

I have made this optional and configurable under $core['sys']['force_admin_pro_skin'] for the next build.

Site Pages

When you open up the builder, you can see all existing pages in the "Layout" dropdown at the top of the view. The "New Page" feature and some more friendly features are in works for the next upgrade. If there's something in particular you want to see in the builder, let us know what else you're missing.

Module Description

Yes, this is easy enough to change. In skin_menus.php, add the following inside the onmouseout="" parameter in $skin['main_menu_rollovers']:

onmouseout="justHide('toparea_ajax');"

This'll make them close when your mouse moves away from the menu button.

If you want to make it close after rolling over it (by default it closes by clicking), in skin_wrappers.php, find the following line:

Module Associated URL

This is currently not used anywhere, it's just a part of the module credits metadata.

Thanks.

Just for anyone else wanting to make the change above under Admin Area Skin, the file you need to modify is core/config_misc.php rather than core/config_mapper.php.

Good catch, post edited. Thanks!