Custom Profile Fields




Looks like a config issue on your site. I'm taking a look.
The field type available for selection of my added CPFs are different from those bundled. Is this normal?
I think you're saying that there are fewer type options when editing a CPF compared to when adding a CPF. This is normal, as you can only edit to another field type that uses the same underlying storage method (integer, string, etc).
Become a fan of Composr on Facebook or add me as a friend. Add me on on Mastodon. Follow me on Minds (where I am most active). Support me on Patreon
- If not, please let us know how we can do better (please try and propose any bigger ideas in such a way that they are fundable and scalable).
- If so, please let others know about Composr whenever you see the opportunity or support me on Patreon.
- If my reply is too Vulcan or expressed too much in business-strategy terms, and not particularly personal, I apologise. As a company & project maintainer, time is very limited to me, so usually when I write a reply I try and make it generic advice to all readers. I'm also naturally a joined-up thinker, so I always express my thoughts in combined business and technical terms. I recognise not everyone likes that, don't let my Vulcan-thinking stop you enjoying Composr on fun personal projects.
- If my response can inspire a community tutorial, that's a great way of giving back to the project as a user.






I think both these problems are external to Composr, I couldn't reproduce them myself. You may want to try a VPN if that is possible to you, for a more 'reliable' connection. I just added the "Area" CPF to your site without a problem.
The JavaScript error ("An error has occurred") should no longer happen as I've made it a bit smarter. But again I don't think it was a Composr bug, but some kind of networking issue.
Become a fan of Composr on Facebook or add me as a friend. Add me on on Mastodon. Follow me on Minds (where I am most active). Support me on Patreon
- If not, please let us know how we can do better (please try and propose any bigger ideas in such a way that they are fundable and scalable).
- If so, please let others know about Composr whenever you see the opportunity or support me on Patreon.
- If my reply is too Vulcan or expressed too much in business-strategy terms, and not particularly personal, I apologise. As a company & project maintainer, time is very limited to me, so usually when I write a reply I try and make it generic advice to all readers. I'm also naturally a joined-up thinker, so I always express my thoughts in combined business and technical terms. I recognise not everyone likes that, don't let my Vulcan-thinking stop you enjoying Composr on fun personal projects.
- If my response can inspire a community tutorial, that's a great way of giving back to the project as a user.


Chris Graham said
Hi,
I think both these problems are external to Composr, I couldn't reproduce them myself. You may want to try a VPN if that is possible to you, for a more 'reliable' connection. I just added the "Area" CPF to your site without a problem.
The JavaScript error ("An error has occurred") should no longer happen as I've made it a bit smarter. But again I don't think it was a Composr bug, but some kind of networking issue.
From “Post #1,372”, 19th December 2016, 9:15 pm
Using Chrome 55 x64 is not okay but Edge works like a champ.




Thanks.
The orders do get stored counting from zero, while they are usually displayed counting from one. That's inconsistent, so I'll fix.
I think we should left-align both on mobile actually.
Become a fan of Composr on Facebook or add me as a friend. Add me on on Mastodon. Follow me on Minds (where I am most active). Support me on Patreon
- If not, please let us know how we can do better (please try and propose any bigger ideas in such a way that they are fundable and scalable).
- If so, please let others know about Composr whenever you see the opportunity or support me on Patreon.
- If my reply is too Vulcan or expressed too much in business-strategy terms, and not particularly personal, I apologise. As a company & project maintainer, time is very limited to me, so usually when I write a reply I try and make it generic advice to all readers. I'm also naturally a joined-up thinker, so I always express my thoughts in combined business and technical terms. I recognise not everyone likes that, don't let my Vulcan-thinking stop you enjoying Composr on fun personal projects.
- If my response can inspire a community tutorial, that's a great way of giving back to the project as a user.


Chris Graham said
I think we should left-align both on mobile actually.
From “Post #1,378”, 20th December 2016, 3:29 pm
A matter of opinion, though bold and normal font is a differentiation, using left and right alignment make it even clearer.



kitonline said
Chris Graham said
I think we should left-align both on mobile actually.
From “Post #1,378”, 20th December 2016, 3:29 pm
A matter of opinion, though bold and normal font is a differentiation, using left and right alignment make it even clearer.![]()
From “Post #1,380”, 20th December 2016, 3:34 pm
It would, but just in English we don't normally right-align stuff except for small phrases.
I have just reviewed all the previews and simplified them. There was a lot of junk on the previews that didn't need to be there, it'll now either show a nice looking preview (which is implemented for quite a few content types), or it will just show the basic text fields with Comcode rendered.
Become a fan of Composr on Facebook or add me as a friend. Add me on on Mastodon. Follow me on Minds (where I am most active). Support me on Patreon
- If not, please let us know how we can do better (please try and propose any bigger ideas in such a way that they are fundable and scalable).
- If so, please let others know about Composr whenever you see the opportunity or support me on Patreon.
- If my reply is too Vulcan or expressed too much in business-strategy terms, and not particularly personal, I apologise. As a company & project maintainer, time is very limited to me, so usually when I write a reply I try and make it generic advice to all readers. I'm also naturally a joined-up thinker, so I always express my thoughts in combined business and technical terms. I recognise not everyone likes that, don't let my Vulcan-thinking stop you enjoying Composr on fun personal projects.
- If my response can inspire a community tutorial, that's a great way of giving back to the project as a user.