bfarber

Examples of custom fields that i can foresee on my own site:
Studio or Publisher
Magazine
Season (like Spring / Summer or Fall / Winter collection)
Date of first printing
Checkbox if the photospread is a later revision or update
Etc.
 

In *most* cases, if you get a generic error message that relates to a specific issue, we need to improve that error at the software level rather than have some sort of public list of every error code ever.

It is entirely possible, for what it's worth, to modify your skin template so that if the user has ignored the poster the post doesn't show up at all. Granted, it could make for some confusion (i.e. post #1, post #2, post #4) but that would only be a minor thing.

It is entirely possible, for what it's worth, to modify your skin template so that if the user has ignored the poster the post doesn't show up at all. Granted, it could make for some confusion (i.e. post #1, post #2, post #4) but that would only be a minor thing.

I'm afraid I can't speak as to whether this will be changed or not, but it's still something on our internal discussion tracker. Sometimes it's a little harder to get things that have no real-world impact (but help third party developers) to the top of the list as you can imagine.
 

We are exploring possibilities as Lindy said, including implementing more event-based triggers (which we do in some places already, such as MemberSync extensions) and looking into adjusting the hooking system to allow it to work with traits as well. As Lindy said, we will update everyone with more information in due course.
 

I'm afraid I can't speak as to whether this will be changed or not, but it's still something on our internal discussion tracker. Sometimes it's a little harder to get things that have no real-world impact (but help third party developers) to the top of the list as you can imagine.
 

We are exploring possibilities as Lindy said, including implementing more event-based triggers (which we do in some places already, such as MemberSync extensions) and looking into adjusting the hooking system to allow it to work with traits as well. As Lindy said, we will update everyone with more information in due course.
 

We are exploring possibilities as Lindy said, including implementing more event-based triggers (which we do in some places already, such as MemberSync extensions) and looking into adjusting the hooking system to allow it to work with traits as well. As Lindy said, we will update everyone with more information in due course.
 

You make a good point. I will raise this internally to see if we can improve the template in this case.

There are no settings specific to adsense crawlers in 4.x.

I have already said, if they are getting a blank white page, you will likely need to check your error logs and/or contact adsense to find out why. This is a feature that THEY have built (for the purpose discussed in this topic, as well as others), it's not something *we* support.

If you copied and pasted your form fields, I can say off the top of my head "passowrd" is misspelled, however I wouldn't expect that to throw a blank white page at adsense.

Unfortunately, this is not something we can provide much support on. If the feature Adsense provides is not working correctly, you should let them know.

You can already give Adsense login credentials for your forum to account for forums that can't be accessed by a guest.

4.0 will also allow you to restrict where ads show, which can be used to disable ads in non-guest forums if you prefer.

There is a Geolocation class available in 4.0 out of the box. It is based on IP address and/or physical address input.

Yes

Nice idea.

Remember, this is a "1.0" release of the hooks system. We wanted to keep it mostly simple (but make it as powerful as possible) so that we could gauge what would be useful to both modders and users alike, before going on a rampage trying to incorporate a bunch of things no one would ever use.

We'd also like to give modders a way to handle the updates through the resource site at some point, but haven't worked out details on that yet.

You can already give Adsense login credentials for your forum to account for forums that can't be accessed by a guest.

4.0 will also allow you to restrict where ads show, which can be used to disable ads in non-guest forums if you prefer.

You can already give Adsense login credentials for your forum to account for forums that can't be accessed by a guest.

4.0 will also allow you to restrict where ads show, which can be used to disable ads in non-guest forums if you prefer.

You can already give Adsense login credentials for your forum to account for forums that can't be accessed by a guest.

4.0 will also allow you to restrict where ads show, which can be used to disable ads in non-guest forums if you prefer.

You can already give Adsense login credentials for your forum to account for forums that can't be accessed by a guest.

4.0 will also allow you to restrict where ads show, which can be used to disable ads in non-guest forums if you prefer.

We have some basic ideas about geolocation support in 4.0, however I doubt they will be implemented to the degree you are requesting above. That would likely require a custom plugin to accomplish - but if the infrastructure to perform geolocation lookups is already in place, it should make such an addon much easier.

Generally if you are on shared hosting your site isn't large enough to warrant Sphinx. When it gets to that point, your host will most likely insist you move over to VPS/dedicated hosting where you'll have the ability to use Sphinx.

When realities and wants collide....these are the days of our lives. :(

If the biggest mistake we've made was neglecting the post icons, I think we're doing pretty good myself. :)

I like the idea of auto-expiring moved links. Would save from having to install a task to do this (which I know a lot of people did with 2.3)