Thread

In the absence of a release candidate (which you really should be putting out), are you able to confirm which outstanding bugs will be fixed and document any changes to functionality we can expect? (or confirm there won’t be any)

thanks

I’d feel a lot better about all this if the fate of custom field support in SAEFs was known.  Not really excited about taking a huge step backward in that respect.

Also WTB extension hooks!

I’m concerned about this as well, still no word from anybody in the threads where this was mentioned to my knowledge. Anybody please feel free to correct me if I’ve overlooked it.

I’d feel a lot better about all this if the fate of custom field support in SAEFs was known.  Not really excited about taking a huge step backward in that respect.

Also WTB extension hooks!

I’m concerned about this as well, still no word from anybody in the threads where this was mentioned to my knowledge. Anybody please feel free to correct me if I’ve overlooked it.

can anyone ELs reply?

For sake of my sanity, is there a URL from which I can download the latest 1.6 documentation? All searches on the current, updated docs are returning dead links for me.

Any help would be great. Thanks…

Oh… and congratulations on having 2.1 out!

Hi, mindreactor -

You can see the legacy docs at http://expressionengine.com/legacy_docs

The EE 2 docs are here: http://ellislab.com/expressionengine/user-guide/

You can download the docs for offline browsing from your download area.

Thank you!

Thank you for spelling it out for me Lisa…. as always, you’re the best!!!

So, about all these missing hooks…? Is there any documentation on how I would go about adding a new column to the edit tab entries table in EE2? Without this kind of capability it’s going to be hard for me to present the argument that ExpressionEngine is a adaptable and genuinely suitable solution for our clients… more often than not the control panel needs to be customised to fit the clients needs and the hooks we had in 1.6 allowed us to achieve this… what now???

Sorry Nathan, I must have missed the notification email on your first reply!

Most of the extension hooks that were used to modify the control panel are flat out unnecessary in 2.x.  Between Accessories, the new APIs, and unfettered access to the view files, you can do things for your client that you couldn’t do in 1.x, and usually more easily.

You’re right about the edit page table though, so we can look into making that available.  I don’t recall any developer speaking up for extensions on this page during the developer preview, so we didn’t even examine it.  I’m really puzzled that you’re only bringing this up now.

Why am I only bringing this up now? I guess I assumed that EE2 would build upon what we already had in 1.6, not remove features…  a quick search on Devotee would have given you the data you need though…

  http://devot-ee.com/hooks/ee/edit_entries_additional_celldata/

If you are able to work towards re-instating the 1.6 hooks in a future release it would make EE2 a much more viable platform for us moving forwards. 😊

Nathan this is exactly why we had a multiple months long developer preview.  As was stated on the developer preview mailing list when we first released with no extension hooks, the new CP was rewritten from the ground up, and new methods provided to help you modify the CP.  All extension hooks were removed and we added back in only hooks that modified data instead of markup, and ones that developers spoke up about during that preview, which you were a part of.

If you are able to work towards re-instating the 1.6 hooks in a future release it would make EE2 a much more viable platform for us moving forwards.

We’re not going to look backward in a general sense about hooks that were already intentionally removed.  That was again deliberate, and that time for decision and feedback took place over a year ago.

A method to add information to the edit table is an exception, and won’t likely use the same method because it does not translate to 2.x’s more extensible control panel.  If you have others that you feel you can’t move forward without, please collect them and send it to me in an email.

Hi Derek, appreciate what you’re saying… I wish we would have had more time here @ninefour to play with the developer preview but our feedback was mostly limited to the UI.

It’s only during this last month that we’ve had a suitable project arise that has given us the opportunity to use the public beta in earnest… nearing the end of development on this project we turned to tweaking the control panel to meet the clients requirements and the inability to migrate any EE1 extension which modifies the edit table became clear.

Anything you can do to make it possible again to build upon the edit table would be fantastic. 😊

Is there somewhere I can find the RSS templates that are supposed to be linked from the EE 1 RSS Module documentation?  The link is broken.  The same link is actually included in the EE 2 documentation, although that also includes 2 other links to sample RSS and Atom feeds.

Hi, Jesse - my apologies about the RSS template links.  I’ll get those added to the docs.  For now, I have attached the two templates in a single text file for you.

Thanks Lisa.

Also is the CI site getting a facelift to bring it in line too??