Jump to content

Fredi - friendly frontend editing


apeisa

Recommended Posts

  • 5 months later...

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:

intab.png.74d9871bc1a0c147246fb5dfc834f152.png

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

outsidetab.png.9bcdb30a5eb39c4d8679cb7c4caa8503.png

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

Link to comment
Share on other sites

  • 4 months later...
  • 3 weeks later...

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. 

Link to comment
Share on other sites

  • 3 months later...

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...