Jump to content

Numbered

Members
  • Posts

    310
  • Joined

  • Last visited

  • Days Won

    1

Reputation Activity

  1. Like
    Numbered got a reaction from OptimusBain in My list of wanted cms/pages app improvements   
    Features that I missed in current IPS:
    we can't export/import blocks from one site to another one (we doing all changes on the staging server before deploying them to the production one) block contains media with their id's. So when we upload the same media files they have different id's. It will fix if the media supports folder and filenames instead of id. We can upload a lot of media files to different websites and copy-paste pages/blocks code contains the media. It might look like {media="some/folder/file_name.jpg"} if we have a lot of pages and switches from one 'main' page to another one we couldn't find on the next time which page is actual default right now. we should click on the arrow of every page to see if the star icon filled or empty. templates (page templates, css, js) - you couldn't understand where the current css file used now. You can only jump into the edition of each page and remember that. It's not useful. cms don't support languages at all. So in every block, we used code  {{$lang = \IPS\Member::loggedIn()->language()->short;}} {{if mb_strpos($lang, 'de_DE') === 0}} some html {{elseif mb_strpos($lang, 'fr_FR') === 0}} some FR html ... additional 10+ languages {{else}} EN content {{endif}} Or you can define variable inside conditions and call them. This is very dumb way to support multilanguage in 'cms'. And, no cache available for all language based blocks at all.
    block editing in ACP is unuseful. we have very little space for the editor (HTML). No 'revert' option (if save will support ajax we'll have a browser default Ctrl+Z option, but.. we haven't it with reload) same as for templates - when we editing block we couldn't understand on which page it used now You couldn't link the block content with template CSS and JS. Mostly it might be the default way to linking (blocks should be self-dependent). Right now it doesn't (in case of css and js). I hope this list helps the devs to understand the daily pains of our content managers.
    Thank you
  2. Like
    Numbered got a reaction from PurplePixel in Command Line Upgrades   
    Not certainly in that way. In the case of millions of users/topics/answers, the update time may take a long (for business) time. Of course, this also depends on the power of the application server and the database. But overall, the ability to have command-line tools would add a lot of administration, support and deployment abilities. As an example, it would be possible to describe in some manifest file a list with versions of applications/plug-ins and with some continuous integration tool builds an IPS test instance with needed additional stuff, proceed autotests for updated app branch, make deployment to production, etc.
  3. Like
    Numbered got a reaction from PurplePixel in CLI support for apps/plugins   
    This ability will be very useful for OPS team (and for dev's too). I think it is not very hard to develop. We can do this themselves. But our implementation must be supported by us at every IPS update and it will be very painful. What this improvement must do:
    install app/plugin update app/plugin (just with incoming argv with path to gz / xml file) execute well all inside setup/update parts enable/disable app/plugin or apps module That's it. I think it will be not good only for us. It can open a lot of 3rd_party IPS hosters, which can add personal 'approved' list of apps/plugins, which can their clients install simply. There are a lot of good thing, which will open with that ability. I can write much of them, but i think it is not necessary. Anybody can think their usable situations with that. As one more example - we can do CI for IPS. On some app/plugin commit trigger it can autobuild via Teamcity (or any other) and do a lot of autotests. This will improve quality and waste time for doing that with hands. Or we can simply build simular IPS instance as they exist on a lot of production configuration (with app1, app3, plugin16 and plugin17) - and check any needed problems.
    Thanks!
  4. Like
    Numbered got a reaction from sobrenome in My list of wanted cms/pages app improvements   
    @bfarber, thank you so much! I don't know about that before and this will be extremely helpful for us. We doing very complex works with cms application and this is the best option for us. There are fresh examples of what we have done with the cms app (all made inside CMS including languages, registrations, and back-end features). https://wowslegends.com/ https://wowslegends.com/promo1/ 
    Is there any change in the future to improve other parts that I mentioned above?
  5. Like
    Numbered got a reaction from sobrenome in My list of wanted cms/pages app improvements   
    Features that I missed in current IPS:
    we can't export/import blocks from one site to another one (we doing all changes on the staging server before deploying them to the production one) block contains media with their id's. So when we upload the same media files they have different id's. It will fix if the media supports folder and filenames instead of id. We can upload a lot of media files to different websites and copy-paste pages/blocks code contains the media. It might look like {media="some/folder/file_name.jpg"} if we have a lot of pages and switches from one 'main' page to another one we couldn't find on the next time which page is actual default right now. we should click on the arrow of every page to see if the star icon filled or empty. templates (page templates, css, js) - you couldn't understand where the current css file used now. You can only jump into the edition of each page and remember that. It's not useful. cms don't support languages at all. So in every block, we used code  {{$lang = \IPS\Member::loggedIn()->language()->short;}} {{if mb_strpos($lang, 'de_DE') === 0}} some html {{elseif mb_strpos($lang, 'fr_FR') === 0}} some FR html ... additional 10+ languages {{else}} EN content {{endif}} Or you can define variable inside conditions and call them. This is very dumb way to support multilanguage in 'cms'. And, no cache available for all language based blocks at all.
    block editing in ACP is unuseful. we have very little space for the editor (HTML). No 'revert' option (if save will support ajax we'll have a browser default Ctrl+Z option, but.. we haven't it with reload) same as for templates - when we editing block we couldn't understand on which page it used now You couldn't link the block content with template CSS and JS. Mostly it might be the default way to linking (blocks should be self-dependent). Right now it doesn't (in case of css and js). I hope this list helps the devs to understand the daily pains of our content managers.
    Thank you
  6. Sad
    Numbered got a reaction from Sonya* in ¿Tienen sección en español?   
    Can be good choise for create clubs for specific languages here) But i think it never implement because it's a very huge part for some moderation works
  7. Like
    Numbered got a reaction from Sonya* in My list of wanted cms/pages app improvements   
    Features that I missed in current IPS:
    we can't export/import blocks from one site to another one (we doing all changes on the staging server before deploying them to the production one) block contains media with their id's. So when we upload the same media files they have different id's. It will fix if the media supports folder and filenames instead of id. We can upload a lot of media files to different websites and copy-paste pages/blocks code contains the media. It might look like {media="some/folder/file_name.jpg"} if we have a lot of pages and switches from one 'main' page to another one we couldn't find on the next time which page is actual default right now. we should click on the arrow of every page to see if the star icon filled or empty. templates (page templates, css, js) - you couldn't understand where the current css file used now. You can only jump into the edition of each page and remember that. It's not useful. cms don't support languages at all. So in every block, we used code  {{$lang = \IPS\Member::loggedIn()->language()->short;}} {{if mb_strpos($lang, 'de_DE') === 0}} some html {{elseif mb_strpos($lang, 'fr_FR') === 0}} some FR html ... additional 10+ languages {{else}} EN content {{endif}} Or you can define variable inside conditions and call them. This is very dumb way to support multilanguage in 'cms'. And, no cache available for all language based blocks at all.
    block editing in ACP is unuseful. we have very little space for the editor (HTML). No 'revert' option (if save will support ajax we'll have a browser default Ctrl+Z option, but.. we haven't it with reload) same as for templates - when we editing block we couldn't understand on which page it used now You couldn't link the block content with template CSS and JS. Mostly it might be the default way to linking (blocks should be self-dependent). Right now it doesn't (in case of css and js). I hope this list helps the devs to understand the daily pains of our content managers.
    Thank you
  8. Like
    Numbered got a reaction from sobrenome in Font awesome 5.0   
    You right. Globally IPS doesn't need to include big monstrous FA5 (or any else). But with last Rikki answer, I hope they'll create some build tool for an ability to include custom font build with icons which are actually needed. In my humble opinion, this way will be an amazing solution, which may be named as a really good new improvement. Let's wait and see 
  9. Like
    Numbered got a reaction from sobrenome in Font awesome 5.0   
    UP topic. FA5 has a lot of icons, which are very like to have from the box.
  10. Like
    Numbered got a reaction from Cyboman in My list of wanted cms/pages app improvements   
    Features that I missed in current IPS:
    we can't export/import blocks from one site to another one (we doing all changes on the staging server before deploying them to the production one) block contains media with their id's. So when we upload the same media files they have different id's. It will fix if the media supports folder and filenames instead of id. We can upload a lot of media files to different websites and copy-paste pages/blocks code contains the media. It might look like {media="some/folder/file_name.jpg"} if we have a lot of pages and switches from one 'main' page to another one we couldn't find on the next time which page is actual default right now. we should click on the arrow of every page to see if the star icon filled or empty. templates (page templates, css, js) - you couldn't understand where the current css file used now. You can only jump into the edition of each page and remember that. It's not useful. cms don't support languages at all. So in every block, we used code  {{$lang = \IPS\Member::loggedIn()->language()->short;}} {{if mb_strpos($lang, 'de_DE') === 0}} some html {{elseif mb_strpos($lang, 'fr_FR') === 0}} some FR html ... additional 10+ languages {{else}} EN content {{endif}} Or you can define variable inside conditions and call them. This is very dumb way to support multilanguage in 'cms'. And, no cache available for all language based blocks at all.
    block editing in ACP is unuseful. we have very little space for the editor (HTML). No 'revert' option (if save will support ajax we'll have a browser default Ctrl+Z option, but.. we haven't it with reload) same as for templates - when we editing block we couldn't understand on which page it used now You couldn't link the block content with template CSS and JS. Mostly it might be the default way to linking (blocks should be self-dependent). Right now it doesn't (in case of css and js). I hope this list helps the devs to understand the daily pains of our content managers.
    Thank you
  11. Like
    Numbered got a reaction from Rikki in My list of wanted cms/pages app improvements   
    Features that I missed in current IPS:
    we can't export/import blocks from one site to another one (we doing all changes on the staging server before deploying them to the production one) block contains media with their id's. So when we upload the same media files they have different id's. It will fix if the media supports folder and filenames instead of id. We can upload a lot of media files to different websites and copy-paste pages/blocks code contains the media. It might look like {media="some/folder/file_name.jpg"} if we have a lot of pages and switches from one 'main' page to another one we couldn't find on the next time which page is actual default right now. we should click on the arrow of every page to see if the star icon filled or empty. templates (page templates, css, js) - you couldn't understand where the current css file used now. You can only jump into the edition of each page and remember that. It's not useful. cms don't support languages at all. So in every block, we used code  {{$lang = \IPS\Member::loggedIn()->language()->short;}} {{if mb_strpos($lang, 'de_DE') === 0}} some html {{elseif mb_strpos($lang, 'fr_FR') === 0}} some FR html ... additional 10+ languages {{else}} EN content {{endif}} Or you can define variable inside conditions and call them. This is very dumb way to support multilanguage in 'cms'. And, no cache available for all language based blocks at all.
    block editing in ACP is unuseful. we have very little space for the editor (HTML). No 'revert' option (if save will support ajax we'll have a browser default Ctrl+Z option, but.. we haven't it with reload) same as for templates - when we editing block we couldn't understand on which page it used now You couldn't link the block content with template CSS and JS. Mostly it might be the default way to linking (blocks should be self-dependent). Right now it doesn't (in case of css and js). I hope this list helps the devs to understand the daily pains of our content managers.
    Thank you
  12. Like
    Numbered reacted to bfarber in My list of wanted cms/pages app improvements   
    I can't comment on potential changes in Pages that haven't been announced in our news area yet.
  13. Thanks
    Numbered reacted to bfarber in My list of wanted cms/pages app improvements   
    This is already supported just FYI. The tag presented may use the id, but the folder/filename.ext syntax also works.
  14. Like
    Numbered got a reaction from Meddysong in My list of wanted cms/pages app improvements   
    Features that I missed in current IPS:
    we can't export/import blocks from one site to another one (we doing all changes on the staging server before deploying them to the production one) block contains media with their id's. So when we upload the same media files they have different id's. It will fix if the media supports folder and filenames instead of id. We can upload a lot of media files to different websites and copy-paste pages/blocks code contains the media. It might look like {media="some/folder/file_name.jpg"} if we have a lot of pages and switches from one 'main' page to another one we couldn't find on the next time which page is actual default right now. we should click on the arrow of every page to see if the star icon filled or empty. templates (page templates, css, js) - you couldn't understand where the current css file used now. You can only jump into the edition of each page and remember that. It's not useful. cms don't support languages at all. So in every block, we used code  {{$lang = \IPS\Member::loggedIn()->language()->short;}} {{if mb_strpos($lang, 'de_DE') === 0}} some html {{elseif mb_strpos($lang, 'fr_FR') === 0}} some FR html ... additional 10+ languages {{else}} EN content {{endif}} Or you can define variable inside conditions and call them. This is very dumb way to support multilanguage in 'cms'. And, no cache available for all language based blocks at all.
    block editing in ACP is unuseful. we have very little space for the editor (HTML). No 'revert' option (if save will support ajax we'll have a browser default Ctrl+Z option, but.. we haven't it with reload) same as for templates - when we editing block we couldn't understand on which page it used now You couldn't link the block content with template CSS and JS. Mostly it might be the default way to linking (blocks should be self-dependent). Right now it doesn't (in case of css and js). I hope this list helps the devs to understand the daily pains of our content managers.
    Thank you
  15. Like
    Numbered reacted to Morrigan in Better representation of a banned user   
    I disagree. If you need it to be more noticeable then take the extra steps to move banned members into a banned group, make their restrictions heavy or remove all access to everything. That shouldn't be on IPS on how heavy handed or flashy you want to be to your banned users. They provide the means to remove the banned users access to your community. How you display that should be on you.
  16. Like
    Numbered got a reaction from Sonya* in Grammatical case: not all languages behave like English   
    And one more request. Don't make keys like 'Search In'. 'class'...? really?

  17. Haha
    Numbered got a reaction from Sonya* in Large community? You have a problems with sitemap!   
    Wow! I see that too @Sonya*! I think IPS fixed that right now!

  18. Like
    Numbered reacted to Sonya* in Large community? You have a problems with sitemap!   
    I leave it.  We are running extended sitemap for the pages (2,3,4 and so on) as well. It make indeed sense. Your posts sitemap does not make sense. And your screen is a prove -> sitemap for posts does contain zero valid pages. 
  19. Haha
    Numbered reacted to All Astronauts in Which one of you IPS developers is the psychopath?   
    public static function moveCheck( $configuration, $oldConfiguration ) { foreach( array( 'bucket', 'bucket_path' ) as $field ) if ( $configuration[ $field ] !== $oldConfiguration[ $field ] ) { return TRUE; } return FALSE; } @Martin A. dragged me into this brief insanity, he accepted it before I did.
    It's still just so wrong.
  20. Thanks
    Numbered reacted to CodingJungle in Which one of you IPS developers is the psychopath?   
    you don't but its bad form imho, it can make the intention unclear :) 
  21. Confused
    Numbered reacted to Adriano Faria in Which one of you IPS developers is the psychopath?   
    You don’t need the curly braces.
    https://stackoverflow.com/questions/8726339/php-if-else-for-foreach-while-without-curly-braces/8726411
     
  22. Thanks
    Numbered reacted to newbie LAC in Media upload limit   
    \applications\cms\modules\admin\pages\media.php
    'maxFileSize' => 5  
  23. Like
    Numbered got a reaction from Joel R in rebuild posts - one post stays blocked   
    I get the same problems (with the slow conversion of big sites) and have some helper tools for them. One tool is for background queues. I have a sh script, which runs php file in the cycle.
    #!/bin/bash while [ true ] do /usr/bin/php -d memory_limit=-1 -d max_execution_time=0 $HOME/path/to/task.php echo 'Task executed' sleep 1 done And the task.php file
    <?php require 'path/to/init.php'; $queueTask = \IPS\Task::load('queue', 'key')->run(); var_dump($queueTask); Of course, this script might be in one php file. But in my original helpers, it does not have only one function. I just strip unnecessary other parts which are out of this topic. var_dump additionally can write an exception to the console if something goes wrong. You may run them in the background with piping stdout into the log file. Anyway, if you wanna use them - it's a good starting point for solving your problem with slow background queues.
    My experience that this task finishes background conversion to one day from over the week. Another potential helpful part is increasing REBUILD_SLOW constant (it used to define the batch of each background queue). Typically I prefer to set it to 150. If you understand what value might be good for your environment (depends on performance) - you can tune it for yourself.
    It set up in the constants.php file in that way:
    <?php // your constants variables here \define( 'REBUILD_SLOW', 150 );
     
  24. Confused
    Numbered got a reaction from Daniel F in rebuild posts - one post stays blocked   
    I get the same problems (with the slow conversion of big sites) and have some helper tools for them. One tool is for background queues. I have a sh script, which runs php file in the cycle.
    #!/bin/bash while [ true ] do /usr/bin/php -d memory_limit=-1 -d max_execution_time=0 $HOME/path/to/task.php echo 'Task executed' sleep 1 done And the task.php file
    <?php require 'path/to/init.php'; $queueTask = \IPS\Task::load('queue', 'key')->run(); var_dump($queueTask); Of course, this script might be in one php file. But in my original helpers, it does not have only one function. I just strip unnecessary other parts which are out of this topic. var_dump additionally can write an exception to the console if something goes wrong. You may run them in the background with piping stdout into the log file. Anyway, if you wanna use them - it's a good starting point for solving your problem with slow background queues.
    My experience that this task finishes background conversion to one day from over the week. Another potential helpful part is increasing REBUILD_SLOW constant (it used to define the batch of each background queue). Typically I prefer to set it to 150. If you understand what value might be good for your environment (depends on performance) - you can tune it for yourself.
    It set up in the constants.php file in that way:
    <?php // your constants variables here \define( 'REBUILD_SLOW', 150 );
     
  25. Like
    Numbered got a reaction from Ilya Hoilik in Command Line Upgrades   
    Not certainly in that way. In the case of millions of users/topics/answers, the update time may take a long (for business) time. Of course, this also depends on the power of the application server and the database. But overall, the ability to have command-line tools would add a lot of administration, support and deployment abilities. As an example, it would be possible to describe in some manifest file a list with versions of applications/plug-ins and with some continuous integration tool builds an IPS test instance with needed additional stuff, proceed autotests for updated app branch, make deployment to production, etc.
×
×
  • Create New...