Morrigan

Its been a while, I know, but I want to bring us back around to pages databases and organization. Its still a mess and annoying. I've been asking for ages for ways to better order things when it comes to Pages Databases. At the moment things are listed in one of two ways: Alphabetically or by Database ID this is both in the ACP and on the front end. I don't think this is good for anyone and I really am hoping to get an ordering system for Pages Databases this will reorder things similar to how I suggest it here: The ordering is just atrocious if you look at them each. Here is how they are listed when you are clicked on databases: This is the ACP sidebar: (Edit: I just remembered that the sidebar you can manually reorder in the ACP sidebar, the annoying part here is new databases pop to the top instead of the bottom and so you have to re-order these all the time) Hopefully you can see the discrepancy here already. This is the create menu: . This is my profile which is only consistent with the Mod CP (Not screenshotting as they are identical) As you can see there is no consistency (save for profile to ModCP which list them in Database ID order where no where else does). It also doesn't leave anything for you to put the most important and what you want to be prevalent content closer to the top where less important information is further down on any of these lists. I would like for my order to be Directory, Guides, Reviews, Resources toward the top as these are user submitted content items where News I don't want my Newsletter posts in my profile, the comments make sense since all of my users can comment but I'm one of the only ones that can create Newsletters. I want better control of my menus and my databases. For now I will continue to use the magic of CSS but I still think that a better solution needs to be provided for at least some of this.

So I have been revamping my main site for ages today and it reminded me how much I loathe the "Create" link. It shows you EVERYTHING you have access to submit if your database name and the record name are the same they are redundant as hell (Submit Record to Records) and this is even more prevalent when you use a single category setup instead of having multiple categories. On top of that (and I'm submitting this in a separate topic) Pages databases are a mess in it. I recently revamped my Create link, though I can't fix all of my issues I was able to take it from this: To this: While some of that (I'd say about five from the first section) are admin/staff only it doesn't make that list any less daunting or confusing for an end user. So my issues: No option in order. It currently follows an App order to put it into the list and for Pages they are all listed in whatever order they want looking at it now. No option in what shows in here. If I want a database to be submitted from only one page I can't tell the create menu (without editing the template) what not to show. Create is too vague of a term. I changed my verbiage to "Quick Create Content" to see if it gets used any more than it had been before as it stands even though it moves with the site I still don't think my members know what it is or how to use it. What I want is something where you can mange what shows up and in what order. People are already inundated with how much stuff can be on any one site, it would be good not to overload them with looking through a long list of what they can submit and focus them on your primary content sources.

So if I have a select field with multiple selections (or even just one) we'll say: Book Movie TV Other Eventually I decide "Movie" isn't the right category I want to change the option to "Movie Blockbuster" and "Movie Indie" well my key currently is movie and if I change the key to "movie_blockbuster" everyone that had the key "Movie" still have that key instead of the newly updated key of "movie_blockbuster". Yes I know I could just change the name and add the second one but a change to any key is never reflected in the listings themselves and so it could mean that you have to go through and edit tons of listings to get the correct key on them. It also means that if you remove a key that listings that had those keys still have them even though its no longer an option for that field. What I'm asking for is that if you change keys that it should update said key in the array whether that is to change it to a new key or to delete it as it no longer exists. Is that better @Matt

I've known about the deprecation for a long time and I think I'm one of the very few people that actually utilizes it. I'm preparing to move to a new solution to manage accounts, you should do the same.

Super simple, when using the standard ips Grid CSS on a paginated page the subsequent pages do not recalculate the height of the items so if there are items that are slightly taller on other pages they are out of alignment and throw the rest of the grid off. If you refresh the page (fully instead of the pagination) it recalculates for the page and everything shows as it should. Having to define heights on things that could have a variable height because its paginated is annoying. Please re-trigger the height calculation when a page paginates. Thank you! Note that one has the line fandom while the other doesn't. But a refresh: It legit only happens during pagination page turns.

So in Pages you can change a selection field from something like one to first but the options that had originally chosen one do not get changed to first and they are lost to the oblivion of time and space. It would be nice to have the option that if you change the key that it updates the correlating database entries with the new key. Trivial? Maybe. But it would make it easier for those of use that have rather expanding and contracting databases to be able to manage it more smoothly This would go for deleting keys etc.

I would recommend looking at subscriptions.

Make sure only the people that you want access to submit/edit have the "Add/edit" permissions. Anyone that doesn't will never be able to see the form to submit. They should all be the same page but different parts/permissions of it that come from the database permissions.

No worries dear. Bugs are just best reported direct to the source. It gives the team the ability to investigate directly and quickly. Unfortunately they can’t always scour the forums to verify bugs reported here.

Rebuild your search index.

Bugs should always be reported via ticket in the Client Area: https://www.invisioncommunity.com/clientarea/

Add this to your custom.css: body { background-image: url(IMGURL); }

My brain was putting it together incorrectly. It's behaving the same way as on my community. Its keeping the filter type highlighted but not actually filtering it. The one you linked has all providers but not JUST the Community Managers.

The odd thing is that I can't duplicate it here (when I tried it with the providers page) but when I remove the CSRF key from my URL all of the filters are cleared. For me it highlights the correct items in the filter section but the filter isn't applied to the page (aka there are no results and its not filtering) indicating that in some way on my site that its mandatory. This, I guess, could be a template level issue.

CSRF requirement in the URL was removed in the ACP it would be nice if some front end elements could get the same level of treatment. Currently when using filters in Pages it adds the CSRF to the URL still and if you remove it the applied filters do not work. That's all.

I don't think so. But you may be able to use the "Quote" functionality so that it auto-hides the data but it will still be expandable.

Submit a ticket.

I think the reason this isn't there is because its technically bad for SEO. By the 30 day mark they have been indexed by search engines. When you delete this content or its inaccessible it actually works against you, thus the reason why people are recommending other options. Overall, its your choice obviously. Perhaps you can poke Fosters to see about making it 4.5 compatible.

I don't know what panel you have but most of them will break that down into specifics: So my databases (I have a few) are taking up 3 gigs of that 138 gigs of dick usage on my server. What Daniel is asking you @Moonbeam is which one is it in you case? With my hosting I can actually click on those and get more details: For me I know a chunk of it is my systems daily backup that is run by my server (probably about half of it honestly).

Still in the ACP. Blogs > Blogs >

Group blogs must be edited in the ACP. They aren't the same as a single user blog.

Pretty sure its the "Skin" column in the core_members. 0 and blank I believe is default.

They are looking to UNHIDE content. Unfortunately this isn't feasible as there is no way for the system to know legitimate content from unlegetimate content. The user may have legitimately hidden content (be that moderation queue, hidden content due to reports, hidden content that was hidden due to code of conduct violations). By adding this feature you'd open a can of worms in this sense and is unnecessary. You really don't want something like this. While it seems like a great idea it can cause more issues than it provides solutions for.

Not your content either technically.

If your moderators are the ones closing it, you can already do this with a saved action. This only works with forums but look for "Saved Actions" in the ACP.