This seems like a very interesting project. Will you look at getting the bugs out of the Drupal 6 version before porting to Drupal 7, or are you planning to port / release this soon and develop both branches?

Insert doesn't really cut it from a usability POV, so this, Wysiwyg ImageField or WYSIWYG image upload modules definitely look like the way forward.

Comments

deciphered’s picture

I've started the D7 port, and I would like to work on both branches in tandem. If I do get the D7 port finished soon I will likely concentrate on it as the primary branch and backporting to D6, as I've started moving all my development to D7 and wish to use WF on my own D7 sites.

While I am biased, I wouldn't recommend Wysiwyg ImageUpload as it doesn't use a CCK field to store the data, good for some, but it means that it doesn't get the advantage of native CCK extending module support, such as your own ImageField Extended.

Cheers,
Deciphered.

alan d.’s picture

Are you developing on git for the port? I'm just starting my first real Drupal 7 site (ie: not just a sandbox install) and would love to see the potential of a tightly integrated system that this module appears to promise. I may be able to help out, but I've got two medium projects to develop in the next month....

deciphered’s picture

Yes, you can find the current 7.x-1.x branch at https://github.com/Decipher/wysiwyg_fields/tree/7.x-1.x

The primary holdup is the Javascript, as the format of the CCK Fields is completely different so the majority of the selected and manipulation code needs re-writing, but I'm definitely open to having a second developer take a look at it.

alan d.’s picture

Right, it is low down on my list of things, but I'll try and use it in the project and note down any issues / fixes that I can. Thanks

alan d.’s picture

OK, I found a big issue straight away, but I couldn't really debug it to give much feedback sorry.

With a cleared cache, the direct includes at the top of the module caused some sort of error / loop that prevented the page from loading. When the require_once was commented out, the cache was loaded correctly and the system ran. This was only happening when viewing a node_view() page.

deciphered’s picture

Alan,

Done a touch on D7 and wasn't able to reproduce that particular issue. When you say node_view() page are you referring to a standard node page, or are you using a menu callback with node_view()?

Cheers,
Deciphered.

dwalker51’s picture

+1

ranx’s picture

subscribe

klonos’s picture

deciphered’s picture

More work has been done on this recently, just not committed anywhere yet. It is a top priority to get this module going, but my time is very limited.

I will try to get the updated code committed within the next few days.

deciphered’s picture

Version: 6.x-1.x-dev » 7.x-1.x-dev

A dev release is currently available, thanks to the sponsorship by Realityloop.com and Tieto.com, not a 100% fully functional port yet, but further work is underway.

deciphered’s picture

Status: Active » Fixed

Marking this issue as fixed, while the port hasn't yet been 100% completed, this issue holds no purpose.

klonos’s picture

Yep, we can file separate, follow-up issues for any remaining tasks or problems that we encounter as we go on.

Thank you Stuart for the time and effort put in this and thanx Realityloop.com and Tieto.com for the sponsorship!

Automatically closed -- issue fixed for 2 weeks with no activity.