Fredi - friendly frontend editing

[kongondo]

@Jozsef

There is no need to ask the same question twice. You already asked this same question in Fredi's support forum here:

I'm moving your post there. One, because Fredi has its own support forum and two, multi-threading is not allowed.

[Jozsef]

I am so busted… Apologies and learning as I go.

[lpa]

I had a problem with Fredi on PW 3.0.69 in a template where I had one field on the default FieldsetTab and two fields on another FieldsetTab. Those two fields (musician_info,arrangement_info) did not save even though the field (preliminary_name) on the default Tab saved without problems.

$o .= $fredi->setText('Edit')->render("musician_info|arrangement_info|preliminary_name",$p);

Before PW3 these fields saved normally:

After moving those fields to the default FieldsetTab all the fields save normally. 

How could this be fixed? I would like to keep those fields on their own FieldsetTab.

[lpa]

@apeisa, do you think you would have time to check my questions above? Could this be some PW3 compatibility issue?

[prestoav]

I'm really interested to see v3 compatibility for Fredi too!

[apeisa]

Sorry guys, haven't used (or developed) Fredi in years. I have no idea what it takes to fully support it in latest PW versions.

First thing to try is to add <?php namespace ProcessWire; as a first line to each php file in the module to prevent PW from compiling the files.

Probably the issue @lpa is describing is something to do with new PW features and requires proper debugging though. 

[Marty Walker]

Would anyone be interested in forking and working on Fredi as a paid gig? I have Fredi running on a big-ish client site that's PW 2.6 and I need it to run happily with v3. Or are there alternatives?

[tpr]

Check FEEL, see my sig. 

[theo]

7 hours ago, Marty Walker said:

 Or are there alternatives?

There is also PageFrontEdit https://processwire.com/blog/posts/front-end-editing-now-in-processwire-3.0-alpha-4/