August 24, 20168 yr 3 hours ago, Ryan H. said: They should work there as well. If not, let me know. I can't test it, it's just a pre-sale question, to be sure before buying your great app
August 24, 20168 yr 9 hours ago, Ryan H. said: Are you actually getting errors on your site? Or just when you run the support tool? If on your site, I need to see your error logs. As far as I can tell, the forum itself is not having issues. It is only in the support tool.
August 25, 20168 yr On 24/8/2016 at 9:31 AM, Xelphos said: So I apparently have database errors, I assume this is because I updated to 4.1.14 which made changes to certain things with addons/plugins. I don't know exactly what the errors are, but this is what the support option in the ACP gives me: I upgraded fron 4.1.13.2 to 4.1.14.2 and I have the same DB errors. Everything seems to work properly.
August 25, 20168 yr Author 23 hours ago, JiigSaaw said: I can't test it, it's just a pre-sale question, to be sure before buying your great app Got it. Yes, that should work as expected. 16 hours ago, Xelphos said: As far as I can tell, the forum itself is not having issues. It is only in the support tool. 6 hours ago, zelgadis said: I upgraded fron 4.1.13.2 to 4.1.14.2 and I have the same DB errors. Everything seems to work properly. Understood, thanks. I'll look into it for the next update, but otherwise, unless you see something break, you can disregard the "DB errors" the support tool reports. The support tool is known (notorious) for misinterpreting the database schema, writing it one way and then reading it as something different, when it's actually the same. Evidently they changed something about it in 4.1.14, and this was a side effect.
September 2, 20168 yr The Support Tool is complaining about the database structure. The support team solved the issue for me, and I am attaching the file to this post. The explanation is as follows: Quote The first issue is that the Advanced Tags and Prefixes application has some incorrectly formatted queries, which causes the database checker to tell you to re-run the queries every time it runs. You will need to contact the modification author about this issue and let them know that a "length" attribute needs to be defined for the columns in their install queries.json: topic_prefix, show_prefix_in_desc, require_prefix. You can also send them the file applications/advancedtagsprefixes/setup/install/queries.json from your server, which I have already patched to resolve this issue and confirm the problem is not with the database checker code. queries.json
September 3, 20168 yr Author 2 hours ago, Gabriel Torres said: The Support Tool is complaining about the database structure. The support team solved the issue for me, and I am attaching the file to this post. The explanation is as follows: queries.json Thank you.
September 4, 20168 yr Hi, Ryan. I'm not sure if I misread what this tool does or I'm doing it wrong, but there's a prefix that I want to remove. Let's say it's called "[beta]". I added that prefix into the text field and ran "Yes. Let's do it." but the prefix wasn't removed. The text field below is where I added the prefix. Did I do it correctly or am I missing something?
September 5, 20168 yr Author 3 hours ago, GrooveOnBeat said: Hi, Ryan. I'm not sure if I misread what this tool does or I'm doing it wrong, but there's a prefix that I want to remove. Let's say it's called "[beta]". I added that prefix into the text field and ran "Yes. Let's do it." but the prefix wasn't removed. The text field below is where I added the prefix. Did I do it correctly or am I missing something? Are you trying to remove an actual prefix, or "[beta] ..." text at the beginning of topic titles? That tool removes text from topic titles. If you want to remove an actual prefix, look at the tag manager.
September 5, 20168 yr 2 hours ago, Ryan H. said: Are you trying to remove an actual prefix, or "[beta] ..." text at the beginning of topic titles? That tool removes text from topic titles. If you want to remove an actual prefix, look at the tag manager. Yes, I wanted to remove some of the actual prefixes in bulk. The Manage Tags will do. Thanks!
September 11, 20168 yr When I upgrade to v4.1.14.3, support tool tells me this: ALTER TABLE `forums_forums` CHANGE COLUMN `require_prefix` `require_prefix` TINYINT NULL DEFAULT 0 COMMENT 'AT&P: Require a prefix' ALTER TABLE `forums_forums` CHANGE COLUMN `show_prefix_in_desc` `show_prefix_in_desc` TINYINT NULL DEFAULT 0 COMMENT 'AT&P: Show prefixes on index' ALTER TABLE `forums_topic_mmod` CHANGE COLUMN `topic_prefix` `topic_prefix` INT NULL DEFAULT -1 COMMENT 'AT&P: Topic prefix'
September 11, 20168 yr 39 minutes ago, Joel R said: When I upgrade to v4.1.14.3, support tool tells me this: ALTER TABLE `forums_forums` CHANGE COLUMN `require_prefix` `require_prefix` TINYINT NULL DEFAULT 0 COMMENT 'AT&P: Require a prefix' ALTER TABLE `forums_forums` CHANGE COLUMN `show_prefix_in_desc` `show_prefix_in_desc` TINYINT NULL DEFAULT 0 COMMENT 'AT&P: Show prefixes on index' ALTER TABLE `forums_topic_mmod` CHANGE COLUMN `topic_prefix` `topic_prefix` INT NULL DEFAULT -1 COMMENT 'AT&P: Topic prefix' Already explained above how to solve this:
September 11, 20168 yr 2 minutes ago, Gabriel Torres said: Already explained above how to solve this: Ah thanks
September 15, 20168 yr On 9/11/2016 at 6:07 PM, Gabriel Torres said: Already explained above how to solve this: Shouldn't the actual install queries be modified as per IPS's request? Will the plugin be updated to match, or will we always have to run this queries.json file? @Ryan H.?
September 15, 20168 yr Author 2 hours ago, djpretzel said: Shouldn't the actual install queries be modified as per IPS's request? Will the plugin be updated to match, or will we always have to run this queries.json file? @Ryan H.? I'll include it in the next update. I don't intend to release a new version for one file for something that isn't broken except for when you try to run the support diagnostic. If it bothers you, the file as Gabriel/IPS so helpfully provided will fix it.
September 19, 20168 yr I have noticed that in the side block of recent posts there is no space after the tag and before the text. This looks dreadful, as literally the text is touching the edge of the tag. Is it possible to make a space after the tag? I believe it used to be like this in an old version, but somehow changed.
September 19, 20168 yr 7 hours ago, ekforum said: I have noticed that in the side block of recent posts there is no space after the tag and before the text. This looks dreadful, as literally the text is touching the edge of the tag. Is it possible to make a space after the tag? I believe it used to be like this in an old version, but somehow changed. This has been already pointed out to the developer: See the posts after this one for the developer's answer and a possible solution.
September 30, 20168 yr On 8/16/2016 at 5:12 AM, Unlucky said: Hi google is reporting the following error message below and every 185 of the urls are connected to the tags such as... /tags/downloads/ /tags/gallery/ /tags/forums/ uk/search/?tags=car+red&sortby=newest&page=1 The google message is: Googlebot identified a significant increase in the number of URLs on http://www.net/ that should return a 404 (not found) error, but currently don't. This can cause a bad experience for your users, who might have been looking for a specific page, but end up elsewhere on your website. This misconfiguration can also prevent Google from showing the correct page in search results. How do we fix this? I have the same issue with Google and tags, how did you fix this?
September 30, 20168 yr I found it, its under the system app and search permissions for guests. I realized this after seeing that the tags pages were search results. google sees these are 404s if you don't enable this. Its good for internal linking. I don't really like guests searching but in this case, I need the SEO. I decided to use flood control for guests and set it for 25 sec. I changed the language settings for the error page they get when they have to wait to: Please wait {# [1:second][?:seconds]} before attempting another search. Avoid waiting the extra time by logging in or registering as a member of our community. I figure maybe that'll prompt registrations. Edited September 30, 20168 yr by ajmboy Changed to 25 Sec
September 30, 20168 yr Author 1 hour ago, ajmboy said: I found it, its under the system app and search permissions for guests. I realized this after seeing that the tags pages were search results. google sees these are 404s if you don't enable this. Its good for internal linking. I don't really like guests searching but in this case, I need the SEO. I decided to use flood control for guests and set it for 25 sec. Good call. Thanks for sharing!
October 6, 20168 yr Hi Ryan H., Is this error causede by the app?; There are some problems with your database. Normally it is safe to try to fix these problems automatically however if your community is large, you may want to run the necessary queries manually. If so, the queries to run are: ALTER TABLE `forums_forums` CHANGE COLUMN `require_prefix` `require_prefix` TINYINT NULL DEFAULT 0 COMMENT 'AT&P: Require a prefix' ALTER TABLE `forums_forums` CHANGE COLUMN `show_prefix_in_desc` `show_prefix_in_desc` TINYINT NULL DEFAULT 0 COMMENT 'AT&P: Show prefixes on index' ALTER TABLE `forums_topic_mmod` CHANGE COLUMN `topic_prefix` `topic_prefix` INT NULL DEFAULT -1 COMMENT 'AT&P: Topic prefix'
October 6, 20168 yr 23 minutes ago, Pedro Ibáñez said: Hi Ryan H., Is this error causede by the app?; There are some problems with your database. Normally it is safe to try to fix these problems automatically however if your community is large, you may want to run the necessary queries manually. If so, the queries to run are: ALTER TABLE `forums_forums` CHANGE COLUMN `require_prefix` `require_prefix` TINYINT NULL DEFAULT 0 COMMENT 'AT&P: Require a prefix' ALTER TABLE `forums_forums` CHANGE COLUMN `show_prefix_in_desc` `show_prefix_in_desc` TINYINT NULL DEFAULT 0 COMMENT 'AT&P: Show prefixes on index' ALTER TABLE `forums_topic_mmod` CHANGE COLUMN `topic_prefix` `topic_prefix` INT NULL DEFAULT -1 COMMENT 'AT&P: Topic prefix'
October 6, 20168 yr Author 1 hour ago, Pedro Ibáñez said: Sorry I don't know hot to do that... If you're not comfortable applying the fix, you can just wait until the next release. It'll be fixed then. In the mean time, ignore those three errors. Nothing is actually wrong with your site, and nothing is broken because of them. The only problem is with the support tool database checker seeing things as incorrect when they aren't.
October 15, 20168 yr Yo my man... I just asked the ips support why my articles where not saving in column forum and i couldnt save the options.. and they said it was with your app.. and they said that your plugin had the same problem before .. and you fixed it.. well in the newest version of ips its messing up again.. can you update your app so it works again.
