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 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?
  4. 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
  5. 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
  6. 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
  7. 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 
  8. 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.
  9. 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
  10. 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
  11. 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.
  12. 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.
  13. 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
  14. 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.
  15. 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!

  16. 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. 
  17. 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.
  18. Like
    Numbered got a reaction from supernal in Large community? You have a problems with sitemap!   
    IPS Sitemap generator using special database table source for refreshing - core_sitemap.
    Primary search engine source of sitemap is url https://example.com/sitemap.php which is list of sub-sitemap files. You can see list of that files proceed for this link.
    Each of that file contain no more than 1000 urls to specail pages (profile status, topic (without number of pages or comment) and other elements, with supported sitemap as core extension).
    One of our case is forum with more than 100k topics, more than 4.2kk posts and more than 6kk users. So with simply math we have 5214 sitemap files (you can simply count number of that files with command 
    select count(*) from core_sitemap; // 5214 Sitemap generator task run by default once per 15 minuts and update only one oldest element from that big list. With simple math we can try to answer question 'how many time we need for update everything?' (because users can post not only in newest and may post in some old topics... but.. new created topic will add to sitemap file only when ALL older files will newer than current file with new topic inside). So, how much time we need for update?
    5214*15 = 78210 minuts = 1303 hours = 54 days! 54! days! Search engine will add your newest content after 54 days after them posted. Incredible thing. Not believe? Or want to know this lag for your community? You can simple know your lag time with that sql:
    select FROM_UNIXTIME(updated,'%a %b %d %H:%i:%s UTC %Y') from core_sitemap order by updated asc limit 1; // Wed Nov 01 14:13:49 UTC 2017 Yep.. In our case oldest file last updated in 1 November...
    What we should do for fix it? Very fast solution - create a temp file, like a 'mycustomsitemapupdater.php' with this content:
    <?php require 'init.php'; $generator = new \IPS\Sitemap; $generator->buildNextSitemap(); $last = \IPS\Db::i()->select('FROM_UNIXTIME(updated, "%a %b %d %H:%i:%s UTC %Y")', 'core_sitemap', null, 'updated asc', 1)->first(); print_r('Oldest time now: ' . $last . PHP_EOL); And run it via web or cli so times, what you want (before oldest time not be so old).
    Solution for a longer time - add this script to the cron and run it every minute or, which better - change task 'sitemap generator' run time from 15 mins to one minute (but it may be not solve you special problem, if you need to update it faster - do it with smart).
    Better solution - wait for IPS updating of that system.
    Thanks for attension!
    P.S. If you read my text with negative speach - it's wrong. I love IPS and just want to make attension for that problem and help others with their large communities. 
  19. Like
    Numbered got a reaction from SeNioR- in Large community? You have a problems with sitemap!   
    I think this becomes a negative result for Google. Google scans the whole page and index content on a specific page. In your sitemap_posts file, you have tons of links to the same pages (they have not differences by the code or view). So with that, you bring Google just problems. Moreover, for preventing duplications Google gives us a links management service, where we can 'say' to Google which params identify something important with content changing (like a 'page' attribute) or something not necessarily (like an 'unread' param).
    Additional, you made just problems for Google. If you wish to highlight or markup the content on the page - you should use schema.org meta, html5 tags. All of that already done by IPS. You don't need to do anything more in general purpose.
    Anyway, if your really want to scan every post like an individual content - make a special request to the topic, which will show only one post without other (but with the link to the default view). In this way, you'll increase your number of scanned 'pages'. But it mustn't be good for your SEO.

  20. Sad
    Numbered reacted to sadams101 in Large community? You have a problems with sitemap!   
    @DawPi has completed the custom sitemap application that I mentioned which handles all posts. You can see an example of it here:
    https://www.celiac.com/sitemap_posts.php
    but it is modeled after the existing sitemap--but this one handles just forum posts. We were not able to add a minimum word count to this application, as one person suggested, because it slowed things down and put a load on the CPU. We were, however, able to add the ability to exclude certain forums, for example my site has around 25 different forums, so I was able to exclude a general chit chat and a technical support forum that are more or less off the main topic of my site.
    Whether or not this will be a benefit or liability in Google search is an open question, but I'll follow up here with any noticeable changes, positive or negative.
    I believe this will have positive results, simply because we are making it easier for Google to index specific content and allow them to provide more relevant search results for any given query. Currently Google's results may send people to a topic page like this one /page/10/, and the person who searched will still have to fish on it for the specific results of their query. With all posts indexed, Google should be able to send the person directly to the content that answers their query...at least that is my hope here.
    Anyone interested in this app can contact @DawPi
    Here is a screenshot of the admin page:

  21. Like
    Numbered reacted to bfarber in 5.0 - A Discussion   
    Our community in the cloud environment is load-balanced and set up this way. The "nodes" are transparent to the end user and administrator, however, and we do not attempt to provide statistics on a per-node basis (it is irrelevant to the functionality). In other words, cluster support is already there
    We have style guidelines which we try to follow. We are also human, however.
    The software also already supports this. We used to use it on our community in the cloud environment until recently, but all you have to do is define the right additional settings in conf_global.php to enable this, and ensure the constant \IPS\READ_WRITE_SEPARATION is set to TRUE (the default). Look in the Db.php database driver class for the settings to define in conf_global.php.
  22. Like
    Numbered reacted to Xenboy in Secure File System Storage   
    In a number of popular web scripts like Drupal, the software has the ability to specify a non-public location for the software to store and serve files from. IPS doesn't allow this, you can only specify file system locations that are within the web root of the account (meaning that there is direct access to the files via a URL). For security, best practice is to store data outside of your web root location. This stops people from uploading files and then accessing them via direct URL and potentially compromising the account or even the server (particularly on servers where the web server does not run PHP scripts as the local user). 
    It would be nice if IPS supported local file system access outside of web root. Right now, IPS also allows you to specify a local file system storage location outside of the web root, but if you use that file storage location, those items will no longer be accessible by IPS once the system moves them. If nothing else, IPS should warn people in the ACP that if you specify a file system location outside of the web root, the items won't be accessible.
  23. Thanks
    Numbered got a reaction from Cyboman 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 
  24. Like
    Numbered reacted to Patreon Lukazuki in Font awesome 5.0   
    There are many cool free new icons in FA5 and they updated a lot of icons from v4
    yup I know is difficult to do in a short time, but it must have in a future update
  25. Like
    Numbered reacted to jair101 in Font awesome 5.0   
    Do you have any plans to integrate Font Awesome 5.0 with the suite?
×
×
  • Create New...