Dreadknux

@Dreadknux The feature is already implemented in the last version. I am just testing it with 4.7 Beta that's why no release in Marketplace yet.
You can copy-paste a new code from here https://invisionify.com/uploads/page_objects/toc.js.9dfc64d46d40b781a8c0758cccaf01dd.js?v=b574a07d041653147371 And here is an example for an article that uses it https://invisionify.com/blog/how-to-create-curated-youtube-videos-for-community/

Hi @Sonya*
Thanks, looking forward to the next update!
I wanted to try and tweak your toc.js JS code myself to add an "a" anchor before H2 tags, to help with the issue I was having. I used some code from your FX Images JS code to try and wrap an anchor tab around an H2/H3/H4 tag within the page, but it doesn't seem to be working.
setup: function () { // Find the items we need var self = this; var items = this.scope.find("h2, h3, h4"); items.each( function (i) { $( this ).attr('id', 'toc'+i); $( this ).closest('p').wrap("<a id='#" + $( this ).attr('id') + "'></a>"); }); var output = []; var last = ''; if( !items.length ){ return; } Any ideas?

Hi @Sonya*
Just wanted to add to the first suggestion I posted above (side menu closing on every click on mobile), I have taken a recording to show you what I mean. Also, it appears that drop down menus no longer expand when clicked on mobile either, as you can see. I’ve not modified any of the JS or CSS relating to the menu. Any chance this can be fixed? 

Hi all!
I wanted to let you know that we've just released 4.7.0 Beta 1 and I wanted to run though some of the highlights on the release notes page.
 
We recently released a cool little feature to enable you to consolidate a forum and all sub-forums into a single list of topics, much like the global fluid view mode. We took onboard some feedback and made it a little more efficient and also reversed the checkboxes so they are ticked by default as some reached out to let us know it was confusing loading a page with content and unchecked boxes. We also added the new URL parameters into the default robots.txt to avoid Google and friends adding faceted pages into its index.

This week, @Daniel Fadded hCaptcha as a new CAPTCHA method to be used on the contact us form, guest posting and other areas a captcha is used. hCaptcha seems to be a more robust method to keep those pesky bots out. You will need to sign up to hCaptcha, but it's a short registration process and they have a free tier which should be all you need.

One of our enterprise clients mentioned that bots and guests are searching for random things which makes analysing the search trends difficult, so we've added a feature to allow you to omit member groups from adding to the anonymised search logs.
Another popular piece of feedback was to add 'solved' and 'unsolved' filters to the activity stream, and @Andy Millne did just that for 4.7.0.

Elsewhere, @Stuart Silvester improved the speed at which Elastic Search re-indexes the site (useful as 4.7.0 needs a re-index due to the new solved filters).
Our master API person @Daniel F made some improvements to the Zapier integration for this release.
We have raised the minimum PHP version to 7.4, but we do recommend 8.0. We are still working through 8.1 compatibility.
Our cloud platform has new architecture to remove a lot of existing if( \IPS\CIC ) code that you may have seen in our codebase. Moving all cloud functionality into its own area means that those on the self hosted platform won't have to run these checks constantly in the code.

We chose to name this release 4.7.0 because of the PHP minimum version changes and the cloud platform code consolidation.

Let me know if you have any questions on this next release.


 

So… what do we think this will be? The clue is pretty cryptic. New user profile features? Photo recognition stuff? Dynamic floating heads appearing on the front end? 😛
Looking forward to hearing more about it!

I really liked the Pages suggestion honestly. It's just that it's a complex area of code that we have earmarked to refactor at some point, so it's not something we'd consider before then.

Hi guys
Long time InvisionCommunity user, almost-first-time poster. 🙂 I've been using this software to power my community forums for about 15+ years now and I'm looking to take the next step by building an integrated site for my users. I recently purchased the Pages app to experiment with it - the idea is that, one day, I might migrate a long-running Wordpress blog into Pages. With that in mind, I had a few ideas that would greatly help with improving workflow and ensure more consistent connectivity between Forums and Pages. I hope you'll consider them!
To keep things concise, my ideas here are focused on the 'Copy to Database' feature of Pages (I do have other ideas but this is the biggest area of concern for me - I'll post the other suggestions in a separate thread).
 
My Setup
In AdminCP > Pages > Databases > Articles > Forums, 'Post Topic' and 'Use Forum For Comments' are enabled. Post Topic is enabled because not every article we write will be sourced from a forum topic or Copied to Database, and we want to make sure that all news stories we write have an associated topic posted (i.e. if a topic does not exist already, we want to create a topic, but if a topic does exist we want to Copy to Database and use that particular topic as the news story's associated topic) Use Forum for Comments is enabled because we want to always marry the comments in news stories with the replies in the associated topic. We never want this feature to be disabled.  
My Scenario
A regular user in my community discovers some interesting news that they may have read elsewhere, and posts a topic on a particular forum. A member of my community's "News Team" usergroup sees this topic, notices that our Articles database has yet to cover this news topic. The News Team member chooses to 'Copy to Database' the original topic. The original topic is written in a way that works fine for a community environment, but it needs editing in order to read well as a news article. So the News Team member modifies the original topic content to suit the tone of voice we want to present within our news stories.  
The Issues
When the News Team member posts the news story, a duplicate topic is made (in the forum selected in AdminCP). This has the result of confusing the community as there are now two separate topics in which to submit replies/comments to.
  When rebuilding synchronised topic content, the original topic's content is modified to match that of the news story which was created from it. This is not desired behaviour; if copied to database, the expectation is that the original topic remains the same, with any edits made for the news story living solely on the page record/database.
  There's no topic meta to illustrate to users on the forum that a news story was created from it.  
The Solutions:
1. 'Post Topic' Override (per Record basis)

A simple checkbox could be added to a record creation page, if the 'Post Topic' setting is enabled for that database in AdminCP. What this will do is ensure that a topic is not created when the record is created. This will be useful for users who want to use an existing topic as the basis for a record's comments/replies without splintering it into a duplicate topic elsewhere. However, some users might find posting a duplicate topic useful (for instance, they might want to dedicate a specific forum for record entries), which is why having this as an ad-hoc option is the best solution here.
 
2. AdminCP-level Option to Keep Topic/Record Content Separate

Provide a toggle which allows the content in the Original Topic to remain unaffected/does not sync with the copy written in the Page content. I would have thought that this would be standard behaviour, so it's surprising that it's not. I doubt many community members would appreciate their topics being edited without their consent, so this option would fix that issue. This could be a new setting added to AdminCP, which applies to all records made in a database (as illustrated above).
 
3. Add Topic Meta to Copied Topics
Upon using 'Copy to Database', have a setting/toggle (default setting: On) that automatically inserts a new Topic Meta box in the original/source topic, detailing that a user has used the thread as a basis for a new 'record/story/article'. Clicking the Meta box could dynamically expand it, revealing an excerpt of the new story/record/article (Title, Author, Date, Excerpt, Link to Full Article). Some ideas as to how that would look like below.
Idea 1:

Idea 2:

This could also be a setting in the Database options page in AdminCP. A feature like this would be a more elegant solution when copying topics to databases, instead of simply syncing the topic content and record content to be identical. It can also allow users who create interesting topics to see that their posts have been considered worthy of interest from the moderation/news team. You could even tie Achievements/Points/Rewards to this - users who create topics that a moderating team deems interesting for a story, could be awarded points for 'sourcing' the content.
---------------------------------------------------
Hopefully these suggestions are worth considering and implementing in a future update. I know the next update of the Core app is at the forefront of the development team's minds right now, but I think these would be great QOL updates for the Pages app that can make it even more unified with the Forums/Core. Thanks for reading!

Thanks for the feedback - I get what you're saying about no follow-up comments on those topics but they did get a fair number of positive reactions from other Invision Community clients (the Pages one received 7) so I think that counts for something? I don't think these are ideas that would only benefit me, but I understand that you would probably like to see lots of activity in a topic before wanting to comment on it. Fair enough.

We can only skip the news, if it is indicated to whom it applies. 
Scenario A:
“Streaming is coming (to enterprise plans)” I am not not on that plan, so moving on. Otherwise it will be scenario B:
“Streaming is coming!” Getting exiting. Having to research the details. Finding out to whom it applies. Being frustrated.  So, it’s very much about how the news are presented. 

I am asked again and again, why my app FX Pages changes the theme. And if it is safe to confirm new versions on the screen below. And if it will break their theme...
This is due to the message the users see when an upgrade for Pages templates is there. The message says the new version of the theme (there is no new theme!) has changed the templates they have edited (they do not have edited any!).

Can we have a message that states what really happens? E. g. 
Some templates have been changed in the new version of the application. Please confirm the changes.
It would be also nice to have the message formatted as a warning (ipsMessage_warning) instead of an error. Just to not frighten the user 😉 
And ideally have a button where we confirm all new versions with just one click. For non-technical users, those screens with a lot of code are dreadful 😨
Thank you!

We utilize CKEditor 4.18 in our software and both the plugins you listed are not confirmed to work for that version. Please contact the author of those plugins to ensure that they are compatible with the version of CKEditor.

I am going to release a new version this week.
Generally, you can create your own JS and CSS files and add them to your page instead of those delivered with the app. JS and CSS will be replaced silently during the upgrade, so you are going to lose all your custom changes if you have modified the original FXPages JS and CSS. 
I will look into it, however, generally I stick to the IPS framework and UI widgets to be sure it works on every theme out there. So I will not heavily modify the standard IPS functionality to avoid a lot of support.

Hi @Sonya*
Just wanted to add to the first suggestion I posted above (side menu closing on every click on mobile), I have taken a recording to show you what I mean. Also, it appears that drop down menus no longer expand when clicked on mobile either, as you can see. I’ve not modified any of the JS or CSS relating to the menu. Any chance this can be fixed? 

You are looking at the commerce>Support guide there, so you wont see items for pages there. Please see this guide which shows how you add these. This is in relation to a recipe database, but the concept is the same no matter what the database
. 

Hi Sonya
Many thanks for your continued work on this app, it's really helping me out. I have some questions/bugs/suggestions for future updates, please:
Mobile Menu Closing on Every Click
The menu, when viewed in mobile mode, closes every time a user clicks on a menu item. Whether it is a link to a page or a category/dropdown link. It means that a user has to click the menu to open, then click a dropdown link (say, 'Games'), the menu will close so the user has to click the menu again to open, then click a page link within the opened 'Games' menu category to go to the page they like. Any chance of fixing this?
Small Typo
Underneath a page, if there is a previous/next link available, the word 'Previous' is typo'd. It says something like 'Previuos' 😄
Multi-Level Category in Menu?
The menu allows a user to open a category and see the pages inside that category level, but it doesn't show any sub-categories (either as a link to visit or as a nested dropdown to see further sub-pages). It gives the impression that there is nothing in the database beyond that top level. I know you probably don't want to add too many levels (and maybe this is a user-set option in Settings - "how many levels do you want to have in the menu?") but this may be worth thinking about?
Include Link to Category As Well As Dropdown in Menu
Do you think it might be possible to include a link to a category in the docs menu, as well as a way to open/dropdown the menu? At the moment, clicking a category in the docs menu only opens the category and shows pages inside. Perhaps if a user clicks the arrow, the category opens, and if you click the category text, you go straight to the category page instead?
TOC Header Tagging Issue
I have a problem with the way FXPages codes in the #TOC anchors via the JS script. I use a sticky navigation bar on my IPB install, and I use a lot of custom CSS across the site to compensate for anchors sitting behind the navbar (by adjusting the 'a' anchors' top margin and height). I can't seem to fix it for FXPages' anchors though, because rather than include an 'a' anchor before the H2 tag, like this:
<a id="toc1"></a> <h2>TOC Header Text</h2> FXPages adds a "toc1" id within the H2 tag itself, which isn't helpful. Is there a chance you can change this behaviour so it works as above? It's the way IPB use to anchor posts on the forum, so it would keep things consistent.
Record Image Repositioning
This might not be possible, but I was thinking - the way FXPages handles record/hero images for a page is really cool. But is there a way that you can implement a 'reposition image' toggle so that if we upload an image that is bigger than the record image area, we can move the image around so it still looks good on the page?

Sort of like the above (sorry it's a terrible cut and paste job, but you get the idea)?
Thanks again for all your great work on this product! 🙂 

While it is possible to solve it within template using a lot of PHP and heavy customizing, I would not do it.
The best way would be a custom widget, based on Similar Content widget. This widget pulls all the items containing the same tag(s). You would create your own, add some filters, like categories and sorting (e. g. by popular).
The widget I refer to is applications/core/widgets/relatedContent.php

not all wiki markups are supported, but the ones you see on the demo page are
in the future i might consider completely re-do this to support all markups

This has been fixed in FX Pages 2.2.0. Currently waits for approval.............

Hi @Sonya*
I appreciate the feedback, regarding the menu above sidebar ads/announcements I guess it will require editing of stock IPS templates, as you say. I will have to figure out a clever way around this (I always try to design my themes with as little modification of the stock theme as possible - through CSS manipulation etc).
However, I think you may have misunderstood my point about the left sidebar appearing above the content on mobile/tablet view... I could do the trick you suggested at the end of your response to me, but that doesn't seem like a workable solution to me (it would involve having the sidebar void of any other widgets besides the Menu, and I'd like the sidebar to include other content as well - at which point, when the tablet or mobile view is activated, there will always be content appearing above the main content area).
I've had a little play around with CSS and realised that this can be something you can implement easily in FXPages using the following custom CSS code. It adds a flexbox to the entire content + sidebar area, and sets an order to the sidebar and maincontent (which is then flipped when the tablet view is engaged via media screen). I've shared it here in case you want to include it as part of a modification/toggle on settings (i.e. "Do you want left sidebar to appear underneath content when tablet/mobile view is engaged? Y/N"). Anyone else can add this to their custom CSS too; just change the "docs" part of "cCmsDatabase_docs" to whatever database slug they want the sidebar flip to apply to (you can easily check this by looking at the Source of a page in the database in your browser and checking the classes in the 'body' tag).
/* Page Databases That Use Left Sidebar: Fix Ordering in Mobile View */ body.cCmsDatabase_docs #ipsLayout_contentWrapper { display: flex; flex-wrap: wrap; flex-direction: row; } body.cCmsDatabase_docs #ipsLayout_contentWrapper nav.ipsBreadcrumb_top { flex: 0 1 100%; order: 1; } body.cCmsDatabase_docs #ipsLayout_contentWrapper #ipsLayout_sidebar.ipsLayout_sidebarleft { flex: 1 0 50%; order: 2; } body.cCmsDatabase_docs #ipsLayout_contentWrapper #ipsLayout_mainArea { flex: 1 0 50%; order: 3; } body.cCmsDatabase_docs #ipsLayout_contentWrapper nav.ipsBreadcrumb_bottom { flex: 0 1 100%; order: 4; } /* TABLET Fixed Page Order */ @media screen and (max-width: 979px) { body.cCmsDatabase_docs #ipsLayout_contentWrapper #ipsLayout_sidebar.ipsLayout_sidebarleft { flex: unset; order: 3; } body.cCmsDatabase_docs #ipsLayout_contentWrapper #ipsLayout_mainArea { flex: unset; order: 2; } } EDIT:
I just wanted to throw in another little bug I noticed if that's okay... on the menu widget, sub-categories are always expanded even when the arrow is set to closed. Please see below (the 'Mainline Games' subcategory is expanded, the 'Section 2.2' subcategory is not expanded but the child page is still visible). Any chance this can be fixed? Thank you, I appreciate it 🙂 

Thank you for responding and linking that 🙂 

Unfortunately @Sirmadsen, this is a bug (not IPB's fault, but due to constantly changing API parameters by Facebook themselves) and I've logged it in this topic. It doesn't look like IPB will spend the resources to fix it (understandable), instead leaning on Zapier integration.
 

Zapier has a free tier which works really great for most stuff. 

Hi guys
Long time InvisionCommunity user, almost-first-time poster. 🙂 I've been using this software to power my community forums for about 15+ years now and I'm looking to take the next step by building an integrated site for my users. I recently purchased the Pages app to experiment with it - the idea is that, one day, I might migrate a long-running Wordpress blog into Pages. With that in mind, I had a few ideas that would greatly help with improving workflow and ensure more consistent connectivity between Forums and Pages. I hope you'll consider them!
To keep things concise, my ideas here are focused on the 'Copy to Database' feature of Pages (I do have other ideas but this is the biggest area of concern for me - I'll post the other suggestions in a separate thread).
 
My Setup
In AdminCP > Pages > Databases > Articles > Forums, 'Post Topic' and 'Use Forum For Comments' are enabled. Post Topic is enabled because not every article we write will be sourced from a forum topic or Copied to Database, and we want to make sure that all news stories we write have an associated topic posted (i.e. if a topic does not exist already, we want to create a topic, but if a topic does exist we want to Copy to Database and use that particular topic as the news story's associated topic) Use Forum for Comments is enabled because we want to always marry the comments in news stories with the replies in the associated topic. We never want this feature to be disabled.  
My Scenario
A regular user in my community discovers some interesting news that they may have read elsewhere, and posts a topic on a particular forum. A member of my community's "News Team" usergroup sees this topic, notices that our Articles database has yet to cover this news topic. The News Team member chooses to 'Copy to Database' the original topic. The original topic is written in a way that works fine for a community environment, but it needs editing in order to read well as a news article. So the News Team member modifies the original topic content to suit the tone of voice we want to present within our news stories.  
The Issues
When the News Team member posts the news story, a duplicate topic is made (in the forum selected in AdminCP). This has the result of confusing the community as there are now two separate topics in which to submit replies/comments to.
  When rebuilding synchronised topic content, the original topic's content is modified to match that of the news story which was created from it. This is not desired behaviour; if copied to database, the expectation is that the original topic remains the same, with any edits made for the news story living solely on the page record/database.
  There's no topic meta to illustrate to users on the forum that a news story was created from it.  
The Solutions:
1. 'Post Topic' Override (per Record basis)

A simple checkbox could be added to a record creation page, if the 'Post Topic' setting is enabled for that database in AdminCP. What this will do is ensure that a topic is not created when the record is created. This will be useful for users who want to use an existing topic as the basis for a record's comments/replies without splintering it into a duplicate topic elsewhere. However, some users might find posting a duplicate topic useful (for instance, they might want to dedicate a specific forum for record entries), which is why having this as an ad-hoc option is the best solution here.
 
2. AdminCP-level Option to Keep Topic/Record Content Separate

Provide a toggle which allows the content in the Original Topic to remain unaffected/does not sync with the copy written in the Page content. I would have thought that this would be standard behaviour, so it's surprising that it's not. I doubt many community members would appreciate their topics being edited without their consent, so this option would fix that issue. This could be a new setting added to AdminCP, which applies to all records made in a database (as illustrated above).
 
3. Add Topic Meta to Copied Topics
Upon using 'Copy to Database', have a setting/toggle (default setting: On) that automatically inserts a new Topic Meta box in the original/source topic, detailing that a user has used the thread as a basis for a new 'record/story/article'. Clicking the Meta box could dynamically expand it, revealing an excerpt of the new story/record/article (Title, Author, Date, Excerpt, Link to Full Article). Some ideas as to how that would look like below.
Idea 1:

Idea 2:

This could also be a setting in the Database options page in AdminCP. A feature like this would be a more elegant solution when copying topics to databases, instead of simply syncing the topic content and record content to be identical. It can also allow users who create interesting topics to see that their posts have been considered worthy of interest from the moderation/news team. You could even tie Achievements/Points/Rewards to this - users who create topics that a moderating team deems interesting for a story, could be awarded points for 'sourcing' the content.
---------------------------------------------------
Hopefully these suggestions are worth considering and implementing in a future update. I know the next update of the Core app is at the forefront of the development team's minds right now, but I think these would be great QOL updates for the Pages app that can make it even more unified with the Forums/Core. Thanks for reading!

Hi guys, starting to get used to Pages app as a potential alternative to move away from my current Wordpress setup (although there are a few issues that I'd like to see resolved first before I take the plunge, I've made topics about those before here I think), and looking for a solution to easily allow for a "Writers" usergroup to share a common imagebank when developing articles and news stories etc.
After playing around with the Invision Community Demo, I've found that the Gallery app could be a potentially elegant solution for this, by creating a gallery that is only visible to "Admins" and "Writers" (not Members or Guests). I thought a great feature was the ability to search through Gallery Images when looking to add media to a Pages record, as shown below:

However, only the user that uploaded the image can opt to use it in this way - not the rest of the usergroup (or any other group that has access to the gallery). When a different user (who did not originally upload the image) in the "Writer" group tries to add an image the same way, they only see this:

It would be great if we could allow for shared galleries, that multiple people in a usergroup can all access no matter who originally uploaded the images.

As we cannot assist with the designing of pages, I have moved this to community support for you. There are quite a lot of people who have done a lot of different designs with these. So Im sure someone will have something that fits the bill