Ilya Hoilik

(RU4) URLs Transliteration
Some browsers not able to work correctly with Cyrillic links. This simple plugin converts Cyrillic characters into Latin in all new URLs on your IPS Community Suite.
Supported languages: Russian, Ukrainian, Belarusian, Bulgarian, Macedonian and Greek.
Links without plugin: domain/topic/1-вышла-локализация-для-версии-400
Links with plugin: domain/topic/1-vyishla-lokalizatsiya-dlya-versii-400
Not recommended for use on sites with Cyrillic domain.

You can use .test domain as well. Point some .test domain to 192.168.1.16 or 127.0.0.1 in your hosts file. It is completely legal.

You can use .test domain as well. Point some .test domain to 192.168.1.16 or 127.0.0.1 in your hosts file. It is completely legal.

https://www.techandme.se/convert-myisam-to-innodb/

Use advanced search

v1.1.0 of the application is now pending approval on the Marketplace.
A pre-Xmas sale price of $25 ($10 yearly renewal) is in effect, which is 50% off the price of the application. This special price offer will end on 1st January 2022, at which point it will revert to $50 ($20 renewal)
IMPORTANT: this was developed against the default IPS theme. If you purchase this application and have a custom theme which results in the template hooks not working then there will be manual steps required to put things in place - instructions can be provided on how to do this, if it is deemed necessary.

Of course it is. Only a note: the right is dropTable.

Matt, morning! Let me put my two cents. I think you should have to announce renewal price change and allow everyone to renew till January 1 for old price (even if a customer has renewal date after January 1). The pros are customers may choose between renewing right now for $105 or later for $310 if it is no problem for them.
Personally I do not see global problems in $310, but I believe this change had to be realised another way. You should have to give customers a chance to select between several options. Especially because we live in COVID era and some people may have financial problems. I am in luck I renewed my main license past week.
I guess we will see less free products in the Marketplace in the future and less purchases of paid products, because some customers may leave or simple do not renew their license. Bet renew price raising will have long-lasting consequences for us as a third-party developers. I also think we will see how some of developers leave us and switch to another projects.
Regarding support, I see a lot of products where support are provided via public forum. I don't think it is such bad as someone else wrote here. Will see how it will go and hope it will be ok.
Regarding PR, I really hate that 'Don’t worry, it’s not bad news'. It is on top of the worst sentences I have seen for a several months. I work for Yandex and face a PR-sentences from time to time, but that one sentence is very ugly. Price raising is always a bad news for everyone who are paying. I would really re-word it.
I am not leaving nor have a plan to, but I think Invision Community development team must concentrate on customers suggestions and do all the best to release long-awaited update for Pages and Downloads. Especially for Pages, because it has unlimited potential and may turn Invision Community into the next level.

Matt, morning! Let me put my two cents. I think you should have to announce renewal price change and allow everyone to renew till January 1 for old price (even if a customer has renewal date after January 1). The pros are customers may choose between renewing right now for $105 or later for $310 if it is no problem for them.
Personally I do not see global problems in $310, but I believe this change had to be realised another way. You should have to give customers a chance to select between several options. Especially because we live in COVID era and some people may have financial problems. I am in luck I renewed my main license past week.
I guess we will see less free products in the Marketplace in the future and less purchases of paid products, because some customers may leave or simple do not renew their license. Bet renew price raising will have long-lasting consequences for us as a third-party developers. I also think we will see how some of developers leave us and switch to another projects.
Regarding support, I see a lot of products where support are provided via public forum. I don't think it is such bad as someone else wrote here. Will see how it will go and hope it will be ok.
Regarding PR, I really hate that 'Don’t worry, it’s not bad news'. It is on top of the worst sentences I have seen for a several months. I work for Yandex and face a PR-sentences from time to time, but that one sentence is very ugly. Price raising is always a bad news for everyone who are paying. I would really re-word it.
I am not leaving nor have a plan to, but I think Invision Community development team must concentrate on customers suggestions and do all the best to release long-awaited update for Pages and Downloads. Especially for Pages, because it has unlimited potential and may turn Invision Community into the next level.

I you can learn Wordress' code, then you can do anything. 🤪
Yes, anything complex or needs logs / screenshots can be moved into a ticket, that's no problem.

Matt, morning! Let me put my two cents. I think you should have to announce renewal price change and allow everyone to renew till January 1 for old price (even if a customer has renewal date after January 1). The pros are customers may choose between renewing right now for $105 or later for $310 if it is no problem for them.
Personally I do not see global problems in $310, but I believe this change had to be realised another way. You should have to give customers a chance to select between several options. Especially because we live in COVID era and some people may have financial problems. I am in luck I renewed my main license past week.
I guess we will see less free products in the Marketplace in the future and less purchases of paid products, because some customers may leave or simple do not renew their license. Bet renew price raising will have long-lasting consequences for us as a third-party developers. I also think we will see how some of developers leave us and switch to another projects.
Regarding support, I see a lot of products where support are provided via public forum. I don't think it is such bad as someone else wrote here. Will see how it will go and hope it will be ok.
Regarding PR, I really hate that 'Don’t worry, it’s not bad news'. It is on top of the worst sentences I have seen for a several months. I work for Yandex and face a PR-sentences from time to time, but that one sentence is very ugly. Price raising is always a bad news for everyone who are paying. I would really re-word it.
I am not leaving nor have a plan to, but I think Invision Community development team must concentrate on customers suggestions and do all the best to release long-awaited update for Pages and Downloads. Especially for Pages, because it has unlimited potential and may turn Invision Community into the next level.

Matt, morning! Let me put my two cents. I think you should have to announce renewal price change and allow everyone to renew till January 1 for old price (even if a customer has renewal date after January 1). The pros are customers may choose between renewing right now for $105 or later for $310 if it is no problem for them.
Personally I do not see global problems in $310, but I believe this change had to be realised another way. You should have to give customers a chance to select between several options. Especially because we live in COVID era and some people may have financial problems. I am in luck I renewed my main license past week.
I guess we will see less free products in the Marketplace in the future and less purchases of paid products, because some customers may leave or simple do not renew their license. Bet renew price raising will have long-lasting consequences for us as a third-party developers. I also think we will see how some of developers leave us and switch to another projects.
Regarding support, I see a lot of products where support are provided via public forum. I don't think it is such bad as someone else wrote here. Will see how it will go and hope it will be ok.
Regarding PR, I really hate that 'Don’t worry, it’s not bad news'. It is on top of the worst sentences I have seen for a several months. I work for Yandex and face a PR-sentences from time to time, but that one sentence is very ugly. Price raising is always a bad news for everyone who are paying. I would really re-word it.
I am not leaving nor have a plan to, but I think Invision Community development team must concentrate on customers suggestions and do all the best to release long-awaited update for Pages and Downloads. Especially for Pages, because it has unlimited potential and may turn Invision Community into the next level.

Hello! I saw your PM and will release a fix soon. Thank you for your report!

All of this is on our radar - it's obviously not trivial though. Trust me, I probably use Pages more than anyone else, so I'm certainly aware of the pain points and potential future for it 🙂 

...and the patch is out.

After each major IPS release all of the developers are busy updating all of their existing marketplace and custom apps.  This particular release is all the more challenging as IPS and the developers need to ensure their code works with PHP 7.x and 8.x which adds to the complexity of coding and testing.
Most developers only have a few hours each week in which they can devote towards the marketplace as they have full-time jobs and many things that take up their time.  Also a handful of developers have left the marketplace in the past year or have had to deal with various personal issues that have prevented them from being available.
Most developers seem to be releasing updates with minimal additional functionality so I wouldn't be surprised if they will be busy again reviewing customer suggestions and releasing follow-up versions.  Things will settle down some in a few months after which time "some" of the developers might entertain doing custom projects.
The marketplace could benefit from a handful more developers but that's not such an easy thing as it requires a significant amount of time and effort to become sufficiently knowledgeable with the IPS codebase and programming environment as well as the cost of purchasing the suite and paying ongoing renewals. Selling 10 apps here and 20 apps there at 10 to 20 dollars isn't likely to be exceptionally enticing to join the marketplace.  
I would welcome the community and IPS to come together to make it more enticing for new marketplace developers and appreciating the efforts that the old-timers make on an ongoing basis.  
 
 

IPS 4.6.0
trying to download a plugin in my dev localhost on ips 4.6.0 and im getting this error 

it happens if i try to download any plugin and i have refreshed all the ips files including developer tools 
any idea? all my plugins work fine it just cant be downloaded anymore in acp

The language string notification__new_content misses 'in'. Actually, it is %s posted %s %s: %s making Someone posted an article Articles: Breaking News.
It should be Someone posted an article IN Articles: Breaking News

Please make it 8PM on a Friday (EST) and be sure to run the upgrader on mobile with 2% battery life left. Thanks and tell the boys in support Lindy sent you!

my request:
can we get documentation for adding API to our apps, I'm having to add it to 3 different apps atm for a project for a client, and i'm really sorta winging it. looking at what you guys have done, but even then its not all that clear what is being done or why. please document the graphql api you've added, i'm assuming you are using this in your mobile app, since i can't find any reference to it in any of your php/js code. '/^\s*\*\s*@([a-z]*)(\t+([^\t]*))?(\t+([^\t]*))?(\t+([^\t]*))?$/', found in /system/Api/Controller.php line 319. hopefully I can express how much misery this regex has caused me. you guys are literally the only software or framework i know of, in php or not, that uses tabs in their code. I use spaces, the rest of the world uses spaces, I have git hooks that will actually reject code for using tabs instead of spaces, my IDE is configured to use spaces. so for like .00001% of the over all app, on stuff that isn't even code, i have to undo ALL of that, just so the api reference docs are processed and shown in the ACP for the other devs on this project to have easy access to that info. I spent a good long while trying to figure out why it was not showing or throwing an exception in the api references, as there was no clear indication as to what was causing it or why. so for sanity sake, please make this regex more robust to look for tabs or space (or better yet, not rely on phpdoc block for api reference, make it a json/xml/txt in <app>/data that can be read and parsed out).  $this->_respond( json_encode( $output, JSON_PRETTY_PRINT ), $response->httpCode, NULL, $shouldLog, TRUE ); /system/Dispatcher/Api.php line 338/342/348., this code does not always produce valid json. it looks like json, but its not, its corrupted. I've had to add 'JSON_HEX_QUOT | JSON_HEX_TAG ' to the flags section of json_encode to get it to produce valid json (i did this thru a hook, but had to overload the entire method, cause there was no point in the code execution, i would be able to add those 2 flags). So please either add those flags or move the json_encode to a method inside the dispatcher, where all it does is json_encode, that way i can hook it and add those flags or any other flags i might need in the near future.  editor content from the api doesn't not get the file or url place holders replaced, i was pulling articles and blogs records, and none of the internal links or attachments were showing up, cause they still had the and <filestore> stuff still in them, so i had to go hook blogs and articles api to parse them (haven't gotten to the other apps yet).  embed/iframe content also is not loaded, cause the src attribute is empty, as the source is still on data-embed-src (i'm assuming this is apart of the IPS lazy loading that didn't get scrubbed properly). on db records, you include a title property but in 'fields' property, it also includes the title field content as well, so if that can be removed or at least give us the ID of which field_# is the title, same for description.  can you also include for any dates, a rfc2822 format along with the rfc3339, as javascript does not like the rfc3339 one (example: DateTime::ts($sometimestamp)->format(RFC::882), this will return a rfc2822 formatted date). heck even a raw unix timestamp would be better than a rfc3339 :).  to be completely honest, the api has not been a pleasure to write code for or to work with. it is one of the most difficult API's i've used. I have spent about 20 times longer debugging and finding solutions, than i have actually writing code to use the api. any way, i hope you guys can address these issues, if not, I might be forced to abandon the api and find another solution.

You can exclude duplicates by using following rules:
Disallow: /*do=* Disallow: /*sort=* Disallow: /*sortby=* Disallow: /*csrf=* Disallow: /*csrfKey=* Disallow: */?tab=* Disallow: */?_fromLogin=* Disallow: */?_fromLogout=* My entire robots.txt https://hoilik.com/robots-txt-for-invision-community-473d8aa32984