Back to Back To Front Support

josh208
josh208

I believe your plugin has a lot of potential. In my particular case, I use relations all over the place and this is causing problems mentioned in the previous topic. I have tried getting the plugin to work now with several of my custom plugins and have run into either the Relation behavior problem (which I am still not sure how to work around), or an error such as:

[2019-06-28 15:39:48] prod-empower-app.ERROR: October\Rain\Exception\SystemException: The partial '_field_markdown.htm' is not found. in /home/joshm/shared/Sites/prod-empower/public/modules/system/traits/ViewMaker.php:91

I have gotten this for markdown, datepicker, fileupload, and relation. I am able to get past the error by touching a file in .../modules/backend/widgets/form/partials, but I am not sure what should be in there, and not sure yet how the frontend will render with just an empty partial because I end up getting stuck on the Relation Render problem.

[2019-06-28 15:45:38] prod-empower-app.ERROR: BadMethodCallException: Call to undefined method Empower\Support\Controllers\Tickets::relationRender() in /home/joshm/shared/Sites/prod-empower/public/vendor/october/rain/src/Extension/ExtendableTrait.php:426

Please help.

Linkonoid
Linkonoid

Hi.Obviously, your question relates to a similar topic https://octobercms.com/plugin/support/linkonoid-backtofront/relations-behavior raised by its author four days ago. Sorry, maybe you are a bit misinformed by my demo, because The version with which you are currently working does not support relation at the top level (the embedded widgets must support, since their redefinition occurs hierarchically). This functionality was added at the request of the author of the previous specified topic and there is no new plugin version (this functionality has been added to the demo to show the author of the previous topic to work on his request). Unfortunately, when implementing, I ran into an intractable problem at the js level (see on the demo site when choosing from the dropdown list and on the search - need to redefine the handler function alias). I have a solution at the change level of an already rendered html, but this is the “wrong way” and I will still try to find the right solution. Please wait, I will try today or tomorrow to lay out a new version of the plug-in, but in it this functionality for the reason indicated above will be raw and positioned as "experimental" (but better this way than without it)

Last updated

josh208
josh208

Thank you for the response, and I look forward to a solution. Is the error that I get for any of the widget fields somehow caused by the Relation Behavior issue, or is that a separate issue? I have not tried a plugin that uses form widgets but not Relation Behavior.

Thanks, Josh

Linkonoid
Linkonoid

As for the first error, all partials and widgets in the plugin are hierarchically programmatically added, incl. all formwidgets. Judging by the file name, it looks like a common partial (and not from the modules/backend/formwidgets). Something is hindering the normal definition of the formwidget, which is why he is trying to find a common partial with a nonexistent name 'markdown'. And somewhere I have already seen this, literally the other day when debugging relations. Therefore, perhaps this error is somehow related to relationships. As for the second log, yes, there is an obvious error related to the absence Relation Behavior

Last updated

Linkonoid
Linkonoid

Hi! Plugin updated to v1.0.2 - adding work with Backend Behaviors: Relation, Reorder, Import/Export Controllers in EXPERIMENTAL mode! This means that this functionality is either unstable or does not work in full. Several fundamental points related to the aliases of these controllers remained insoluble, since it was not possible to change them from my code (it depends on them that the AJAX framework works correctly with my components). Summing up: most of the functions work, but it takes a lot of time for improvements.Unfortunately, current projects do not allow this to be done in the near future.

Regarding your first error from the logs ('_field_markdown.htm') - it really is related to the Relation Controller

1-5 of 5