Jump to content
Invision Community


  • Content count

  • Joined

  • Last visited

  • Days Won


-FP last won the day on November 15 2017

-FP had the most liked content!

About -FP

  • Rank
    Community Regular
  • Birthday 07/22/1988

IPS Marketplace

  • Resources Contributor
    Total file submissions: 14

Profile Information

  • Gender

Recent Profile Visitors

8,800 profile views
  1. This has been brought up quite a few times in other topics. /still waiting
  2. Please test search

    Great! Did 3 searches that I did the past weeks looking for some very specific things. Previously Google did a better job at getting me that, but now searching here I get right away what I needed.
  3. ¿Tienen sección en español?

    Hola. No, solo Inglés. (The question is if there's a Spanish section on the website)
  4. Not really @kmk, well I haven't looked into it, I haven't looked into clubs at all. The thing is it's easy and simple in Pages because of its nature, using custom fields in the templates. I think clubs also has custom fields, but I suspect everything else to make use of them would not be as straight forward.
  5. QOTW: Let's talk about music

    Time flies and I'm getting old...
  6. Improving fluid view ?

    I made a plugin that might be useful to you.
  7. Show us your IPB 4 sites!

    Had an idea and set this up quickly... now the difficult part, getting people into it https://www.thegalaxyoutpost.com/
  8. So I wanted to share this simple example of how you could go about using the pages app to deliver content in various languages. It's probably not the best implementation and there are some things to consider like meta tags... but it works, hopefully some of you will find it useful as a starting point. What is nice is that IPS automatically sets the site language for guests -I believe- based on the browser's locale, so everything works nicely. I created a free demo install on IPS to write this guide, that means that I'm implementing it over the default pages app setup. ------------------------------------------------------------------------------------ 1 - Initial Setup 1.1: Obviously we need to have at least 2 languages. In this example I'm using English and Spanish. English is the default language. At this point you should take a note of the IDs of your languages. In this case it is easy because it's a fresh install and there are only 2 languages, so the IDs are 1 for English and 2 for Spanish. It will probably be different in other cases. You can find the ID of the language by hovering over the button to edit the language and taking a look at the URL. The ID would be the last number in the URL. 1.2: In this example we will be working with the 2 basic fields, the article title and the article content. We need to add additional fields to the articles database, to store the Spanish version of the article. Note that you also need to make a note with the IDs of the Spanish fields so we can use them later in the templates. You can find their IDs in the same way you did for the languages. Create a new Text field for the Spanish article title. Then create an Editor field for the Spanish article content. 1.3: At this point if you try to add a new article, you should see the Spanish title and content fields. 2 - Database Template Edits Now it's time to modify the database templates to display the English or Spanish fields depending on the user's language. I'm modifying the default templates because as I said this is a fresh install and it's what the database uses by default. You may have to check what templates your database is using if you already have custom/different ones in use. I will be modifying a couple of templates, the entry and record ones. Depending on how you show the articles on your site, you may have to expand this to other templates. This setup is meant to work with the database setting "Database index" set to "Show records like articles". Remember when I talked about making a note of the additional Spanish fields IDs and language IDs? In this case, the Spanish title field ID is 3, and the Spanish content field ID is 4. As for the languages, as said in the beginning of the guide, English is ID 1, and Spanish is ID 2. This is important to keep in mind because we will use these to perform some checks and show one field or the other. So IF there's something in the Spanish title field AND the user's language is Spanish, then we will show the Spanish title. Otherwise we will show the English title. Same logic for the content field. 2.1: In the database templates under Category Articles, open the entry template. Find the <span> element for the record title. Modify the code to match the screenshot above. You can copy this and modify the IDs to your needs. {{if $record->field_3 != "" && member.language == 2}} <a href="{$record->url()}" title="{lang="read_more_about" sprintf="$record->field_3"}">{wordbreak="$record->field_3"}</a> {{else}} <a href="{$record->url()}" title="{lang="read_more_about" sprintf="$record->_title"}">{wordbreak="$record->_title"}</a> {{endif}} 2.2: In the same entry template, scroll down a bit to find the <section> element where the preview content is displayed. Once again, replace and modify the code to your needs. {{if $record->field_4 != "" && member.language == 2}} {$record->field_4|raw} {{else}} {$record->truncated()|raw} {{endif}} 2.3: Now we are going to modify the record template under Display. This template displays the full article content when you view it. Locate the code where the article title is displayed, it's below {{if $record->canEditTitle()}} Modify the code once again. {{if $record->canEditTitle()}} <span class='ipsType_break ipsContained' data-controller="core.front.core.moderation"> <span data-role="editableTitle" title='{lang="click_hold_edit"}'> {{if $record->field_3 != "" && member.language == 2}} {$record->field_3} {{else}} {$record->_title} {{endif}} </span> </span> {{else}} <span class='ipsType_break ipsContained'> {{if $record->field_3 != "" && member.language == 2}} {$record->field_3} {{else}} {$record->_title} {{endif}} </span> {{endif}} 2.4: Still in the record template, scroll down a bit to find the <section> element with the article's content. For the last time, modify the code. Again, don't forget to change the IDs if you need to. {{if $record->field_4 != "" && member.language == 2}} {$record->field_4|raw} {{else}} {$record->_content|raw} {{endif}} 3 - Result Article entry in English. Article entry in Spanish. Article content in English. Article content in Spanish. ------------------------------ Aaaaaand that's it for now, cheers! As I said, this is a basic example but what is shown here can be easily expanded to more languages, fields, and to other elements like custom blocks.
  9. Version 1.0.2


    This plugin removes the default desktop view forum filter when in fluid forum view. It adds a button on the sidebar and/or on the forum index. Clicking this button brings up a window to filter the forums, like in mobile view. Compatible with Community Suite 4.2.4 (If the plugin seems not to be working on a 3rd party theme, try reinstalling it)


  10. I had a few members wanting me to delete their accounts. I did the first few times. The problem with this is that in many cases these members have content that if deleted, would alter the flow of a topic/conversation. So then I decided to add a few policies to our Sign Up terms. A specific one informed that accounts are not deleted on demand. Aftet that, some people threatened me with their lawyers for "vulnerig their right to privacy". I talked to a lawyer friend of mine and he concluded that their claims are basically bullcrap. At least in my country you are not vulnering a person's privacy if you can't physically identify the person or their identity. So solely their email or some random internet picture as an avatar doesn't count. It would be different if they posted a real picture of them or if they were dumb enough to post their ID or something like that. In which case you'd just get rid of that information. In the end nothing happened with the threats. Fun times though, people get so paranoid and upset over silly things.
  11. Tablet view

    Also in Desktop view. They upgraded the site not long ago, so that was probably it.
  12. I don't know man.. my dad had all kind of devices and boxy machinery, I can only remember this.
  13. I had it a couple of times before... but I can't say if I was drunk or something and miss-typed my details Hard to tell why it's happening unless IPS takes a look.
  14. Requesting a password reset should clear that lock wait time.
  15. Finding Zero Replies....

    I used this code in a manual html page to list topics without replies... it was mainly a "mod/staff tool" to have quick access to topics without replies, to possibly reply to these topics and boost the forum activity. As I said it was something solely used by mods and I made it to my needs. The topic listing doesn't respect any kind of per forum topic view permissions, the only permission is to set who can view the page to see the listing. {{$topics = \IPS\Db::i()->select( 'tid', 'forums_topics', 'posts = 1' );}} {{$num_topics = 0;}} <h4 class="ipsType_pageTitle">Topics without replies</h4> <div class="ipsMessage ipsMessage_warning ipsSpacer_top"> This page list topics without replies, ignoring any kind of forum read permissions. Double check this page permissions for access. </div> <ol class="ipsDataList ipsDataList_zebra ipsClear cForumTopicTable cTopicList data-role="tableRows"> {{foreach $topics as $topic_id}} {{$topic_title = \IPS\Db::i()->select( 'title', 'forums_topics', 'tid = "' . $topic_id . '"' )->first();}} {{$topic_furl = \IPS\Db::i()->select( 'title_seo', 'forums_topics', 'tid = "' . $topic_id . '"' )->first();}} {{$topic_by = \IPS\Db::i()->select( 'starter_name', 'forums_topics', 'tid = "' . $topic_id . '"' )->first();}} {{$topic_url = \IPS\Http\Url::internal( "app=forums&module=forums&controller=topic&id={$topic_id}", 'front', 'forums_topic', array( "{$topic_furl}" ) );}} <li class="ipsDataItem ipsDataItem_responsivePhoto"> <div class="ipsDataItem_main"> <h4 class="ipsDataItem_title ipsContained_container"> <span class="ipsType_break ipsContained"> <a href="{$topic_url}"><span>{$topic_title}</span></a> </span> </h4> <div class="ipsDataItem_meta ipsType_reset ipsType_light ipsType_blendLinks"> <span>By {$topic_by}</span> </div> </div> </li> {{$num_topics ++;}} {{endforeach}} </ol> {{if $num_topics == 0}} <div class="ipsMessage ipsMessage_success"> There are no topics without replies! </div> {{endif}}