Invision Community 4: SEO, prepare for v5 and dormant account notifications Matt November 11, 2024Nov 11
Posted February 5, 201510 yr In the old interface one could find all the error codes and look them up as to what they mean. Current the new interface don't have the link anymore and I take it that by now all to most of the area codes are final. Could they but listing in the IPS4 Resource link so people can look up what they mean?
February 5, 201510 yr We have an error codes database, and we might make it public once eveything is finished. For now it's used to track error codes and ensure we are using unique error codes.
February 5, 201510 yr Would be appreciated if you could do this, as I used to use the 3.x one quite a bit to help determine issues for questions on the forum. And a 4.x one would be just as good.
February 21, 20187 yr On 05/02/2015 at 3:24 PM, bfarber said: We have an error codes database, and we might make it public once eveything is finished. Cough cough.
April 2, 20187 yr I figured an internal database already existed, so this is good to hear that it in-fact does. Meanwhile, you can do a directory/file search with Notepad++, or whatever utility you use (from the root of the IPS directory), copy the results to a text file, and then regex the results. I started doing this a while ago, but got busy with other stuff and never finished it. A snippet of what I regex'd, just to illustrate what I am talking about: node_error,2B221/1,404 no_module_permission,2B227/1,403 node_error,2B202/1,403 node_error,2B202/2,404 node_error,2B201/1,404 no_module_permission,2B201/2,403 no_module_permission,2B201/3,403 no_module_permission,2B201/4,403 blog_rss_offline,2B201/5,403,blog_rss_offline_admin rss_import_disabled,2B201/7,403 no_module_permission,2B201/6,403 TODO,1B203/1,403 node_error,2L217/1,404 node_error,2L217/3,404 event_rss_feed_off,2L182/1,404,event_rss_feed_off_admin TODO,1L169/4,403 feed_not_found,2L169/2,404 feed_not_found,2L169/3,404 feed_not_found,2L169/1,404 ical_error_.TODO,4L169/5,500 node_error,2L179/1,403 node_error,2L179/2,404 rsvp_error,2L179/3,403 rsvp_limit_nomaybe,3L179/4,403 rsvp_limit_reached,3L179/5,403 node_error,3L369/1,403 node_error,2L354/1,404 node_error,2L182/2,404 error_bad_date,2L182/7,403 error_bad_date,2L182/8,403 error_bad_date,2L182/9,403 error_bad_date,2L182/A,403 cms_delete_linked_topic,1T281/1,403 cms_delete_linked_topic,1T281/1,403 no_module_permission,2T279/1,403 There are of course some rogue lines in there, but hopefully it illustrates my general point.
March 22, 20196 yr Author On 2/5/2015 at 10:24 AM, bfarber said: We have an error codes database, and we might make it public once eveything is finished. For now it's used to track error codes and ensure we are using unique error codes. Is this still being work on or has it been publish yet?
March 26, 20196 yr Author 9 hours ago, bfarber said: It has not been published to date. 9 hours ago, bfarber said: It has not been published to date. we might make it public once eveything is finished. Can you all make it public like it was in the past?
August 8, 20195 yr It would be nice to have general categories for the errors in order to use it on the error page as well. Such as one for all 404 types, one for all failed permissions, etc.
September 16, 20195 yr Author On 8/8/2019 at 10:28 AM, GreenSock said: It would be nice to have general categories for the errors in order to use it on the error page as well. Such as one for all 404 types, one for all failed permissions, etc. True because if where going to be trying to fix the issue how can we look up and understand the problem to fix it if were the ones as the admins.
Archived
This topic is now archived and is closed to further replies.