Mark

{datetime="whatever" dateonly="true"}  

If you're a developer, you can also use the GPS of mobile devices quite easily (we actually use this in IP.Nexus to make the address input field autocomplete, you usually only need to enter your house number and it knows the rest), though I wouldn't recommend it for things like location-based advertising.

With GPS location, it requires both the user to have GPS-compatible hardware, and them to specifically allow access. While that's fine for specific cases, most users aren't going to allow access to their precise location unless they know what you want it for. And for things like location-based advertising, getting it based on their IP is specific enough (I assume you're going to do ads based on their country, or maybe state, but you're not going to show different ads to different streets, presumably ).


The methods available are:
/* IP address */ IPSGeoLocation::getByIp( $ipAddress ); /* Latitude and longitude (such as returned by the GPS) */ IPSGeoLocation::getByLatLong( $latitude, $longitude ); /* Manually */ $geolocation = new IPSGeoLocation; $geolocation->addressLines = array( '123 Fake St.' ); $geolocation->city = 'City'; $geolocation->country = 'US'; So, if you wanted it, it's there. You'd just need to write the JS to ask the user for permission and post the values (which is just a couple lines of JS).

If you're a developer, you can also use the GPS of mobile devices quite easily (we actually use this in IP.Nexus to make the address input field autocomplete, you usually only need to enter your house number and it knows the rest), though I wouldn't recommend it for things like location-based advertising.

With GPS location, it requires both the user to have GPS-compatible hardware, and them to specifically allow access. While that's fine for specific cases, most users aren't going to allow access to their precise location unless they know what you want it for. And for things like location-based advertising, getting it based on their IP is specific enough (I assume you're going to do ads based on their country, or maybe state, but you're not going to show different ads to different streets, presumably ).


The methods available are:
/* IP address */ IPSGeoLocation::getByIp( $ipAddress ); /* Latitude and longitude (such as returned by the GPS) */ IPSGeoLocation::getByLatLong( $latitude, $longitude ); /* Manually */ $geolocation = new IPSGeoLocation; $geolocation->addressLines = array( '123 Fake St.' ); $geolocation->city = 'City'; $geolocation->country = 'US'; So, if you wanted it, it's there. You'd just need to write the JS to ask the user for permission and post the values (which is just a couple lines of JS).

If you're a developer, you can also use the GPS of mobile devices quite easily (we actually use this in IP.Nexus to make the address input field autocomplete, you usually only need to enter your house number and it knows the rest), though I wouldn't recommend it for things like location-based advertising.

With GPS location, it requires both the user to have GPS-compatible hardware, and them to specifically allow access. While that's fine for specific cases, most users aren't going to allow access to their precise location unless they know what you want it for. And for things like location-based advertising, getting it based on their IP is specific enough (I assume you're going to do ads based on their country, or maybe state, but you're not going to show different ads to different streets, presumably ).


The methods available are:
/* IP address */ IPSGeoLocation::getByIp( $ipAddress ); /* Latitude and longitude (such as returned by the GPS) */ IPSGeoLocation::getByLatLong( $latitude, $longitude ); /* Manually */ $geolocation = new IPSGeoLocation; $geolocation->addressLines = array( '123 Fake St.' ); $geolocation->city = 'City'; $geolocation->country = 'US'; So, if you wanted it, it's there. You'd just need to write the JS to ask the user for permission and post the values (which is just a couple lines of JS).

IPB does try to detect if Minify will work and disable it if not.
If for whatever reason the detection doesn't work you can disable it in the ACP - if you'd had contacted support from the start they would have recognised the problem straight away ;)

The main problem for Minify not working and IPB not being able to detect it is due to it's reliance on changing the include path - I did contact Minify a little while ago about this and they told me they would be changing that.

Well that would be a bug which should be reported ;) I've never heard of or seen this issue.

Have you tried clicking the "Get Help With This Page" link on the user agent page?
It will take you to here: http://community.invisionpower.com/resources/official.html?record=293

If you feel that article can be improved, you need to let us know what it's missing... that is what the comment feature is for.

Although it does answer the question being asked:



If you're interested in learning more about Regex, this is a good place to start.
With regards to "." vs "\." though - "." in Regex represents any character, so for the sake of detecting "bestsearchengine.com" - it doesn't really matter if you enter "bestsearchengine.com" or "bestsearchengine\.com".

Updated with conversions information.

We do, as do most web designers. Not to mention, the SEO fanatics would have your head for saying that ;)

We do, as do most web designers. Not to mention, the SEO fanatics would have your head for saying that ;)

I'm rather curious about this statement. In reviewing your account history, it appears nearly all of your tickets are answered within a matter of a few hours. Some within a matter of minutes. The only one I've found that's been open for a lengthy amount of time was your upgrade request, which was initially answered within an hour. We didn't have the necessary FTP information, thus there was a slight delay in that. We then, as a courtesy, worked with you to transfer language packs from other forums (something not typically within the scope of our support service) and resolved character set issues. I feel we've been quite accommodating, hence my confusion with this post. It's quite possible that you're referring to another ticket that I've overlooked, in which case, I do apologize. Naturally, we're not perfect and issues do occasionally fall through the cracks. On the whole, we strive for prompt, efficient service. With scheduling, this works out to be almost 24/7 -- we've recently ramped up basic weekend support.

There's always room for improvement -- I simply want to ensure we're on the same page. :)


Luke: No, it does not.

Updated with conversions information.

Do not submit a support ticket - it's a beta - we won't be able to assist.

If you are experiencing a problem and you're sure you [url=" everything correctly, please file a bug report so a developer can look into it.
It sounds like Depotoir you didn't uninstall the original chat application first, which the instructions says to do (in bold, prefixed by the word "Important")





:rolleyes:

No it's not.
IP.Shoutbox is developed by members of the community who very admirably give up their time to provide it for other members of the community.
IP.Chat is developed and will be supported by IPS much like Blog or Gallery.

Incidentally, if you don't want to use IP.Chat, don't - it's an addon that will at it's most basic level be provided for free - you never paid for it, we never mentioned it before, and if you don't use it, it doesn't really affect anyone here.
Although, it is frustrating how you've based your opinion that IP.Chat has "installation problems" that deem it unusable on a beta - it's this sort of thing that makes me wonder if it's worth releasing public betas at all if people clearly don't understand the concept.

No it's not.
IP.Shoutbox is developed by members of the community who very admirably give up their time to provide it for other members of the community.
IP.Chat is developed and will be supported by IPS much like Blog or Gallery.

Incidentally, if you don't want to use IP.Chat, don't - it's an addon that will at it's most basic level be provided for free - you never paid for it, we never mentioned it before, and if you don't use it, it doesn't really affect anyone here.
Although, it is frustrating how you've based your opinion that IP.Chat has "installation problems" that deem it unusable on a beta - it's this sort of thing that makes me wonder if it's worth releasing public betas at all if people clearly don't understand the concept.

Note the "Installation" header.



No help or instruction indeed... :rolleyes:

I've thought about this a few times before.

I wonder if there should be an option added to hide the language chooser (especially if you only have one language anyway) , I know you can simply skin it out ;) , in fact I've added a quick article on doing this for 3.0. (as I have done for other versions at the time), but the same thing could be said for the skin chooser too, and there is an option to disallow anyone (easily, at least) choosing skins by hiding it.

I'm merely thinking along the lines of tidiness as with only one language present, it does not appear serve a real purpose as far as I can tell. :)

It's just a number guys, don't let it get to you ;)

:rolleyes: Let's not get into debates about encoding and whatnot.

Our standards of service state quite clearly that we do not offer refunds. It is of course disappointing to hear that the product is for whatever reasons not suitable for your needs, but we do not offer refunds due to the fact that we cannot stop the software working if you've already downloaded. We make this policy quite clear in the frequently asked questions section of our website.

If you're actually having a technical problem, I would encourage you to contact technical support - if you have done so and are not happy with the way it's being dealt with, please let us know.
If however, the issue is simply that you don't like the product, I'm not really sure what we can do - we offer demos of up to a week long and have plenty of avenues for asking pre-sales questions.


I'm going to close this thread since discussions about reselling licenses and such which we're getting into isn't really appropriate for these forums - if anyone has any questions about the refund or reselling policies please contact account assistance via the client area :)

:rolleyes: Let's not get into debates about encoding and whatnot.

Our standards of service state quite clearly that we do not offer refunds. It is of course disappointing to hear that the product is for whatever reasons not suitable for your needs, but we do not offer refunds due to the fact that we cannot stop the software working if you've already downloaded. We make this policy quite clear in the frequently asked questions section of our website.

If you're actually having a technical problem, I would encourage you to contact technical support - if you have done so and are not happy with the way it's being dealt with, please let us know.
If however, the issue is simply that you don't like the product, I'm not really sure what we can do - we offer demos of up to a week long and have plenty of avenues for asking pre-sales questions.


I'm going to close this thread since discussions about reselling licenses and such which we're getting into isn't really appropriate for these forums - if anyone has any questions about the refund or reselling policies please contact account assistance via the client area :)

Whether or not the software logs an IP address is kind of irrelevant as the server will log the IP address of every visitor.

Also, if the software cannot log IP addresses, it causes technical issues... there are various features that rely on knowing the IP address, including security features such as IP matching, account locking, et al.

Furthermore, an IP address is not regarded as private information (like a name or email address), nor can it be used to identify you.
Some people seem to have an idea that every computer has a predefined IP address and anyone who knows it can find out your name and address... simply not true. Sure, your ISP has that information, but that's not public... think of your IP address like your library card number ;)

The way we see it, there are thee types of documentation:

- General Questions "How do I do this?", "What does this button do?", etc.
This is provided through the inline ACP docs (a logical place since you'll probably be on the page when you think of these questions) - when viewing a page in the Admin CP, if you need extra help with the functions on the page, click the "Get Help With This Page" button. It's a work in progress, not all pages have documentation yet - but they main ones do, and every time someone requests a page that's not, we're logging that request to build a list of most requested pages.

- Problems / Known Issues "I have x setup and when I do y, I get z"
This is provided through the knowledgebase in the client area (a logical place since if the knowledgebase doesn't have your answer, you'll submit a support ticket) I think at some point we're going to improve that knoweldgebase some.

- Guides
This is what I think you're after the most. Guides are kind of a walkthrough for some of the more complicated stuff, or at least stuff with multiple steps.
At the moment, this is what we know we're lacking in and what we're focussing on internally - we should have some nice stuff for you soon.



Like I say, all are going to continually improve over time, but it's important to remember to make use of all three - the inline ACP help has a lot of information in, so if your question is of the "How do I..." nature, your answer is probably in there :)

Looking at your most recent tickets:

608369: We waited for you to accept our disclaimer, which you eventually refused to do and closed the ticket yourself.
606915: We responded about 4 hours after the ticket creation.
604629: We responded about 40 minutes after the ticket creation.
603845: We initially responded about 15 minutes after the ticket creation, and then you replied on a Saturday, and even then we got back to you about 8 hours later.

In fact, I can't see any tickets that have been open anywhere near 48 hours. I see one that is open now, but that was also only created yesterday.

Am I missing something? If you can provide the ticket IDs for the cases your referring to where you've had to wait, we can see what's going on.

Looking at your most recent tickets:

608369: We waited for you to accept our disclaimer, which you eventually refused to do and closed the ticket yourself.
606915: We responded about 4 hours after the ticket creation.
604629: We responded about 40 minutes after the ticket creation.
603845: We initially responded about 15 minutes after the ticket creation, and then you replied on a Saturday, and even then we got back to you about 8 hours later.

In fact, I can't see any tickets that have been open anywhere near 48 hours. I see one that is open now, but that was also only created yesterday.

Am I missing something? If you can provide the ticket IDs for the cases your referring to where you've had to wait, we can see what's going on.

Looking at your most recent tickets:

608369: We waited for you to accept our disclaimer, which you eventually refused to do and closed the ticket yourself.
606915: We responded about 4 hours after the ticket creation.
604629: We responded about 40 minutes after the ticket creation.
603845: We initially responded about 15 minutes after the ticket creation, and then you replied on a Saturday, and even then we got back to you about 8 hours later.

In fact, I can't see any tickets that have been open anywhere near 48 hours. I see one that is open now, but that was also only created yesterday.

Am I missing something? If you can provide the ticket IDs for the cases your referring to where you've had to wait, we can see what's going on.