-
☆ A M B ☆
- 1,780 Posts
And which of these fields requires a rich text editor? None of these fields, or actually much if any of the profile fields would I ever want a user to be able to edit in rich text.
I'm still very confused. Sorry.
i dont think they want to play detective to understand all those tags..
You are sure, they are knowing what they do, when using a richtext-editor and you allow them to insert html into their profile-page, may be copied/pasted from word or something?
-
☆ A M B ☆
- 1,780 Posts
The fields you posted aren't the kind of fields that really should ever be controlled by a user, which is why I felt confused. The output of those fields should be determined by default for every user. Image size could be a problem, for example. Imagine what a full size image from some dude's camera will do to your output. Much better to wrap the fields with the tags necessary to maintain your layout.
Now, perhaps if there's a long text field for something like a "bio" perhaps, a little inline styles could be something users would want, but even then I'd want to control the output. If you really want users to be able to style stuff like that, a resource or a rich text tv might be a good option. Pull in the content with getResources instead of from the profile fields. Paragraph tags would be my main concern without a rich text editor, and maybe that's what you're looking to overcome.
Consider that extended fields in the profile should provide you with plenty of "choices" for users to input data, but would be choices you can control.
Nevertheless, you should be able to use a front end rich text editor like Aloha for any field in the profile area. I haven't tried and I don't know how, so give it a go and let us know how it works out.
-
☆ A M B ☆
- 1,780 Posts
Is bedtime (past... very past) for me. Took me too long to post and you beat me.
Profile info, is fairly vague but it sounds like you need paragraph tags at minimum.
-
☆ A M B ☆
- 1,780 Posts
Quote from: stevebravo at Dec 31, 2012, 05:24 AM
Why shouldn't it be controlled by a user? Its a functionality the package is offering.. and as far as i have it in use, it works great!
And your statemant about the photo's isnt much of a problem as well, cause i control the input of each photo for a max size of 0,5 mb and with a maximum of 5 pictures. Its a little ugly code i used for it, but it works.. and that is what matters 
I saw no text fields in your example that would need styling. Image, as you've got it works for you. A RTE wouldn't make a difference anyway with that in place.
We're playing forum tag here and losing. I see what you are trying to do now :~}
-
☆ A M B ☆
- 894 Posts
The only front end RTE I suggest you use with MODX is
NewsPublisher it is the most robust and it works with multiple context and template variables and allows you to customize it 100%
FrontPage although nice is broken when it comes to multi context sites and I think it still has a bug where it doesn't render the content area unless you fix a line of code which I documented
here
Using NewsPublisher I have created a user manager on the front end and it works a charm, you just need to spend some time configuring it to your liking for each template you plan on using it on.
Good Luck.
Is there something like newspublisher for evo ?
Yes, it's called NewsPublisher.
