PXLated - 28 June 2005 07:25 AM

the MetaWeblogAPI functionality

Haven’t tried that yet. What are the limitations?
Seems I read that the APIs work great for a blog but are very limited if you have custom fields, etc. Could you fill us in?
Thanks!

The metaweblog API is limited to 4 fields (the big 4 in the weblog world).  So you can map 4 custom fields to main fields.  For instance, I have Body -> Body (oh that’s just so original), excerpt -> mood, summary -> keywords and I’ve ignored extended so far

The other limitation is the fields have to be textareas to be chosen in the EE Control Panel. 

I use MarsEdit and have no problems with it.  I set up 4 metaweblog APIs for 4 different weblogs that I post to the most.

Another limitation is that I have totally failed to get any dashboard widgets to work.  RapidDash or whtever it is connects, but it only sends the title (not an EE problem, since MarsEdit works ;p), and the other one doesn’t work at all, it never figures out the connection. But I haven’t tried it since 2 days after 10.4 so I’m not sure if that’s fixed.

Thanks for the sneak peak. The new CP looks very nice indeed.
I would agree with those who asked for fast publishing template
(all options on one page without additional clicks).

personally, i dig the new publish system. less clutter works best for me. i don’t mind the extra clicks if it simplifies things. thanks rick.

Nice! I so can’t wait!!!!

Nice work overall, but I’m not too happy with the Publish panel. Extra, unnecessary clicks just to get a story posted… Date, Categories and Options should be one. Was there something wrong with the old Publish panel? On iPodlounge.com, getting news, reviews, and articles posted in a fast, efficient manner is important to our bottomline.

Agreed… I’m gonna hear a lot of complaints from my editorial staff about the increased clicking and how it’s going to slow everything down.  Yes it sounds petty I know, but I guarantee it will happen.

Agreed… I’m gonna hear a lot of complaints from my editorial staff about the increased clicking and how it’s going to slow everything down.  Yes it sounds petty I know, but I guarantee it will happen.

Yep got the same complaints here.

Would it be possible to have only the backend upgraded and the frontend as it is right now?

Les Jenkins - 26 June 2005 04:10 PM

Just wanted to take a moment and say that the new ability to add custom tabs to the control panel is simply wonderful. I hop in and out of several modules regularly so having them right on the list of tabs is fantastic.

My thoughts as well. Though it would be great if we could set custom tabs for all users. Of course that’s just me being lazy, when I first saw it, I though cool, we can create a tab to our application that isn’t using EE, and still have users think its all one system. But the note says only the person who created the tab will see it.

Otherwise the interface is super slick. But does present some interesting data entry issues. Such as I our biggest data entry issue is getting users to properly add categories, so having it be on a second page just means more users will skip right over them. But I’m assuming, we can change the display of the primary tab, without creating custom stand-alone data entry screen (hopefully).

Rick Ellis - 24 June 2005 07:17 PM

If you’re curious to see what the 1.3 control panel looks like, here’s a preview.

cant log in with AOL 9.0 (windows XP)

cant log in with AOL 9.0 (windows XP)

File bug report here so the development team knows.

oooh!Thanks for the preview! So far, it seems quite nifty but will certainly require some getting used to!

Just curious at how much editing there’s going to be for those custom themes for the control panel. Or are you guys taking care of porting the existing themes into the new CP Styles?

(did that makes sense to anyone else but me?)

Love the new publish function!  Excellent.  Well done guys.  Good to know my EE purchase continues to be money very well spent.

Nice look and all, but where’s the “View Rendered Template” when you change a template, or does this only appear after having edited a template—which we are not allowed to do, of course?

ErikV - 30 June 2005 05:24 AM

Nice look and all, but where’s the “View Rendered Template” when you change a template, or does this only appear after having edited a template—which we are not allowed to do, of course?

Here’s a slimmed down screen shot:

Thanks Sue,

I thought we were supposed to know how it would look. I’m not good enough at coding to estimate what a change will look like, though, so this is a relief.

Michel (NL) - 29 June 2005 04:50 AM

Would it be possible to have only the backend upgraded and the frontend as it is right now?

I prefer the classic view too. I dont know exactly why, but I just prefer it.