Jump to content

Community

IPBSupport.de

Members
  • Content Count

    2,282
  • Joined

  • Days Won

    2

 Content Type 

Profiles

Downloads

IPS4 Documentation

IPS4 Providers

Release Notes

IPS4 Guides

IPS4 Developer Documentation

Invision Community Blog

Forums

Everything posted by IPBSupport.de

  1. Yes, the support always reply this in tickets, but i'm not at the same opinion. There are a lot of (support) topics on the board where @bfarber (e.g. here) and other IPS Team members told the customers/presales questions that this is a option (subdomain support). At this stage, a lot of customers use this feature and now this does not work anymore. The support told me that this posts are x years old. Yes, but i don't think this is a good way to answer a ticket and justify the missing feature which works years ago.
  2. No, this fix you linked is not a fix for the subdomain "bug" (or support). This "fix" give us only the index.php back, but only with subfolder and not subdomain support.
  3. Since years, we could use the special "index.php" with IP.Content (Now Pages) to use the "Pages" e.g. on www.domain.tld and the forum/community on community.domain.tld - as the IPS team provides this opportunity since years on the support forums (e.g. here and here and a lot of places more) i think this is not a "hidden" feature and was not planned to be supported in the past (i started a ticket and this is the answer i read out of the replys). At this moment, we can not use the current index.php on a subdomain. IPS4 detects if the installation is done in the main/root folder or not. If you installed the community e.g. on community.domain.tld you can not activate the gateway setting in the acp (Pages -> Advanced Settings) because of the automatic detection ("Your IPS 4 suite is already installed at the root of your domain."). There are still support topics about this problem: So i hope there is a quick fix so we can still use the new index.php on a different Subdomain as the community. This still works fine (we could specify a path to the IPS4 install) but we can not activate the setting in the ACP (because the trouble i declared above). I think a "advanced setting" should give us the "power setting" to deactivate the autodetection so we still can use the index.php in a different subdomain as the IPS4 suite.
  4. I know you guys are very busy on fixing bugs on the IPS Suite 4 to become a Final stage. But just a quick question: Is there a problem with the "Legacy Upgrades" Department on your Support System in the Client Area? I'm waiting since Feb. 16 for the change of my licenses without any reply (after @Mark H forwarded my ticket to the department). Not a big deal (don't missunderstand), but for now i have time i would spend testing the IPS 4 Suite (upgrades for bug boards from customers etc).
  5. ​Okay. We do not miss this feature, so forget it... <ironyOFF>
  6. Still waiting and missed this a lot of times here. Cant find topics i looked for... Still don't know who comes to this stupid (sorry, not a personal thing) idea to remove this feature - and also not WHY...
  7. Still get more then one mail for one notification. Get today 3x "Mark has posted a file, reCAPTCHA 2" mails (13:18, 13:20, 13:22 PM).
  8. ​Just a few examples (grrrrr, no uploadbox here / too little storage). Edit:
  9. I also get multiple mails for one notification. Also i get a lot of confusing "NAME has posted a post in a topic requiring approval" mails.
  10. Wonder why there is still no "Only search in titles" option (back) in the search system (or have I missed this now?). I would not explain again why this is a must have feature for a search system, we have declared this here a few weeks ago and after some tests with the feedback board, my testinstallations and now this live board i can say that this option is still necessary for a search system on a community (board). Still hope for this feature - or for the first modder which give us a hook/mod for this.
  11. Does this make sense? If you change the forms.css file during a fix, all other CSS-Files will automatically be upgraded? :o
  12. Great work, IPS! Here are a few (partly little) feature suggestions from me for the language system. Maybe you can think about some of my ideas if you would add more improvements.
  13. The new "Quote" headline is splittet in 2 language bits, but (e.g. for german) we can not translate it so it make sense. For now, you use "quote_said" (said) and "quote_on" (on) to generate a headline like But we need a headline-language string like... %s, on %s, said ...or something else, so we can translate it to a text which make sense.
  14. I tink we don't say "I'm not a fan", we (and i) say'd we have a bad "feeling" if we use your IP.Content tracker. That can have various causes, Adriano listed a few things which makes the IP.Content tracker "ugly". If you using a software (like your IP.Content tracker), you have a "feeling" if you use it. And this feeling is just not good. I can not describe it better.
  15. Ok, thank you. I tink it would be good to change the dropdown to a (in other areas default) selectbox so we can select multiple categorys (not only ONE or ALL).
  16. Just a quick question: How we can leave a dropdown "blank"? :o And: Should re report bugs here or on your "demo"?
  17. Sign! I am also not happy with the new tracker here on the IPS Forums... Working (posting, answering, searching (!!!)) with it feels not good... But the "old one" (IP.Tracker - now "Tracker") seems to be not an alternative at this moment (delayed/slow development). ATM i'm using the old IP.Tracker and i've waited a few month ago/since last year for a (stable) update. For now i think i will change to TracDown (click me) which looks like a cool Bug Tracker System.
  18. Just a quick question to IPS: Do you plan to show statistics to the Nexus referrals on our client area?
  19. I informed Matt and Brandon about the problem and matt said... So: Yes, they read this thread and i hope we will see a captcha in 3.4
  20. What i want to achieve? The badword filter works very well to replace a text with a new one (badword -> goodword :D). The badword filter also works very well to replace a text with a new one INCLUDING bbcode or html code (badword -> goodword including a link, e.g. to the boardrules). But at the moment there are a problem: The filter also works on topic titles (which is correct and good), but if you replace a "badword" with a new word including bbcode or html code, the code show in the topic title: Now there are a few options: For me, i use the system to replace "IPS" with a link to your IP.Board page, IP.Content to the IP.Content page etc... There are a lot of options to use those system, maybe also to show only "crosslinks" (wiki style links). [*]Rename the "badword filter" system to a "Replacement system" or something else and filter the bbcode and html code in topic titles [*]Only filter the bbcode and html code in topic titles [*]Create a similar system to the badword system (maybe only copy the system) and call it "Replacements" to replace texts (not badwords -> goodwords).
  21. Similar to this topic and brandons answer here, i now post this as a feedback / feature request. We can still use the badword filter system to replace a "badword" with a (html or bbcode) link, but this also acts on the topic titles and we see the html/bbcode codes in the topic title. I reported this here as a bug, but matt classified it as "not a bug". So the badword system should become a little rework so that the replacements with html and bbcodes only replace the text, not the html/bbcode or it would be great to have a similar system to the badword system for replacements including the thing with the topic titles.
  22. And even if it is OK on facebook (i do not think so) we don't have any informations about the terms and privacy police on twitter registration. And also i don't think it is a big problem to show a text (maybe including checkboxes) BEFORE a member can register with facebook/twitter - i see this on other pages as well (e.g. "By clicking and registering with the XXX button you accept our terms and privacy police").
×
×
  • Create New...