Mike said:To give an example using a new system, we're currently spending time building a generic payment framework. This is designed not only to allow different payment processors (not just PayPal)
I for one much appreciate this sort of system. How add-ons are required to expend SQL queries with joins is fragile, and very easy to get wrong.We have split off the main "official" updates into a separate thread. This thread should still be used for discussion.
I have just posted a separate update with some code examples if you're interested: https://xenforo.com/community/threads/xenforo-2-0-development-updates.113262/#post-1044323
Could you explain this some more? Its clear that a generic framework will make it easier to reuse existing custom fields functions. But many addon developers need more than the custom fields currently available in XF1.As a specific example, both prefixes and custom fields are ideas used in multiple content types and add-ons. Previously, each required effectively duplicating whole files of code with minor changes. These are now built on a generic framework that can be reused for the core functionality, while simultaneously being extendable so specific features can be added where needed.
Some advanced fields from popular addons:Can you give an example of what you would define as an "advanced custom field"?
I wouldn't necessarily say these are difficult to implement now. Certainly it should be possible to add similar stuff in XF2.Some advanced fields from popular addons:
- Star Rating selection
- Date Picker selection
- Upload file
- Address autocomplete with Google MAPS
- Pros & cons
Display locations for user fields are still currently only a single selection. Grouping fields to be used in different nodes sounds to me like something that would be type dependent. As does multiple display locations, actually. I would say that it would be fairly simple to add these things for different custom field types.Often its possible to select the primary and secondary display location. (under/below content, sidebar, item listing, etc)
With some addons its possible to group fields so that its easy to attribute large numbers of fields to nodes.
The common use case is that admins create the fields that they need, which are mostly different field types and re-use this group to apply it to different nodes.Grouping fields to be used in different nodes sounds to me like something that would be type dependent. As does multiple display locations, actually. I would say that it would be fairly simple to add these things for different custom field types.
A few more examples:I wouldn't necessarily say these are difficult to implement now. Certainly it should be possible to add similar stuff in XF2.
Yep, there are times it is necessary to fire the customer.Such a poor understanding.. no, the customer is NOT king. And no.. the customer isn't always right. In fact, in some cases it's cheaper to tell a customer to "hit the door" than keep putting up with their unrealistic demands/expectations (from a business aspect) as they cost WAY more than what they bring in.
Yep, there are times it is necessary to fire the customer.
And then you have those customers that are very rarely satisfied - as they want it exactly the way THEY want it to work and believe that the world should bend to their needs. Those are the type of customers that are not "cost efficient" and are the ones that need to be shown the door. It's not an inability to "adapt to their business model" but the inability of the user to realize that , as Spock said, "The needs of the many outweigh the needs of the few ...... or the one".Customers can be difficult but the pay you to find solutions and while you may never satisfy all their needs you may satisfy enough to keep them as your customer.
And then you have those customers that are very rarely satisfied - as they want it exactly the way THEY want it to work and believe that the world should bend to their needs. Those are the type of customers that are not "cost efficient" and are the ones that need to be shown the door. It's not an inability to "adapt to their business model" but the inability of the user to realize that , as Spock said, "The needs of the many outweigh the needs of the few ...... or the one".
In an ideal world this works... but a review of previous history of some (pretty sure ex now) licensees - their demands (and yes, I said demands) were a "tad" outrageous. As I said in my earlier post - the type of user that believes the world revolves around them are frequently not "cost efficient" to keep as a customer.If I came here and posted what I had to have in a mod to be successful I wouldn't be told XF doesn't support that and GLHF, but rather I would be told to put in a suggestion where I can get feedback and possible solutions others have come up with that maybe I haven't.
We use essential cookies to make this site work, and optional cookies to enhance your experience.