bassangler

Yes, that fixed it. But I see the "website" type also needs the same treatment. Can that be included in the next release?

I cleared all cache several times, reverted to the default theme, etc. The ONLY time the error went away is when I disabled community maps.

I'm getting this error ever since I upgraded to the latest version 4.7.3 . TypeError: flock(): Argument #1 ($stream) must be of type resource, bool given in /system/Theme/Cache/Template.php:90 Stack trace: #0 /system/Theme/Cache/Template.php(90): flock(false, 1) #1 /system/Theme/Theme.php(802): IPS\Theme\Cache\_Template->exists() #2 /applications/core/sources/Achievements/Rank.php(179): IPS\_Theme->getTemplate('global', 'core', 'global') #3 /uploads/template_28_7a734b11232065691bc1176040cb26ad_topics.php(2321): IPS\core\Achievements\_Rank->html('cAuthorPane_bad...') #4 /system/Theme/SandboxedTemplate.php(61): IPS\Theme\Cache\class_forums_front_topics->postContainer(Object(IPS\forums\Topic), Object(IPS\forums\Topic\Post), Array, '') #5 /uploads/template_28_7a734b11232065691bc1176040cb26ad_topics.php(5116): IPS\Theme\_SandboxedTemplate->__call('postContainer', Array) #6 /system/Theme/SandboxedTemplate.php(61): IPS\Theme\Cache\class_forums_front_topics->topic(Object(IPS\forums\Topic), Array, NULL, Array, NULL, NULL, Array) #7 /applications/forums/modules/front/forums/topic.php(576): IPS\Theme\_SandboxedTemplate->__call('topic', Array) #8 /system/Dispatcher/Controller.php(118): IPS\forums\modules\front\forums\_topic->manage() #9 /system/Content/Controller.php(50): IPS\Dispatcher\_Controller->execute() #10 /applications/forums/modules/front/forums/topic.php(39): IPS\Content\_Controller->execute() #11 /system/Dispatcher/Dispatcher.php(153): IPS\forums\modules\front\forums\_topic->execute() #12 /index.php(13): IPS\_Dispatcher->run() #13 {main} BACKTRACE #0 /system/Theme/SandboxedTemplate.php(71): IPS\_Log::log(Object(TypeError), 'template_error') #1 /uploads/template_28_7a734b11232065691bc1176040cb26ad_topics.php(5116): IPS\Theme\_SandboxedTemplate->__call('postContainer', Array) #2 /system/Theme/SandboxedTemplate.php(61): IPS\Theme\Cache\class_forums_front_topics->topic(Object(IPS\forums\Topic), Array, NULL, Array, NULL, NULL, Array) #3 /applications/forums/modules/front/forums/topic.php(576): IPS\Theme\_SandboxedTemplate->__call('topic', Array) #4 /system/Dispatcher/Controller.php(118): IPS\forums\modules\front\forums\_topic->manage() #5 /system/Content/Controller.php(50): IPS\Dispatcher\_Controller->execute() #6 /applications/forums/modules/front/forums/topic.php(39): IPS\Content\_Controller->execute() #7 /system/Dispatcher/Dispatcher.php(153): IPS\forums\modules\front\forums\_topic->execute() #8 /index.php(13): IPS\_Dispatcher->run() #9 {main} I disabled Community maps, and the errors went away. So I updated from 1.4.2 to 1.4.3, and updated IP to 4.7.4 and re-enabled....and the errors returned. I disabled Community maps again, and the errors disappeared. The errors are occurring on a wide range of forum pages and users.

I'm getting this error ever since I upgraded to the latest version 4.7.3 (theme was updated too). TypeError: flock(): Argument #1 ($stream) must be of type resource, bool given in /system/Theme/Cache/Template.php:90 Stack trace: #0 /system/Theme/Cache/Template.php(90): flock(false, 1) #1 /system/Theme/Theme.php(802): IPS\Theme\Cache\_Template->exists() #2 /applications/core/sources/Achievements/Rank.php(179): IPS\_Theme->getTemplate('global', 'core', 'global') #3 /uploads/template_28_7a734b11232065691bc1176040cb26ad_topics.php(2321): IPS\core\Achievements\_Rank->html('cAuthorPane_bad...') #4 /system/Theme/SandboxedTemplate.php(61): IPS\Theme\Cache\class_forums_front_topics->postContainer(Object(IPS\forums\Topic), Object(IPS\forums\Topic\Post), Array, '') #5 /uploads/template_28_7a734b11232065691bc1176040cb26ad_topics.php(5116): IPS\Theme\_SandboxedTemplate->__call('postContainer', Array) #6 /system/Theme/SandboxedTemplate.php(61): IPS\Theme\Cache\class_forums_front_topics->topic(Object(IPS\forums\Topic), Array, NULL, Array, NULL, NULL, Array) #7 /applications/forums/modules/front/forums/topic.php(576): IPS\Theme\_SandboxedTemplate->__call('topic', Array) #8 /system/Dispatcher/Controller.php(118): IPS\forums\modules\front\forums\_topic->manage() #9 /system/Content/Controller.php(50): IPS\Dispatcher\_Controller->execute() #10 /applications/forums/modules/front/forums/topic.php(39): IPS\Content\_Controller->execute() #11 /system/Dispatcher/Dispatcher.php(153): IPS\forums\modules\front\forums\_topic->execute() #12 /index.php(13): IPS\_Dispatcher->run() #13 {main} BACKTRACE #0 /system/Theme/SandboxedTemplate.php(71): IPS\_Log::log(Object(TypeError), 'template_error') #1 /uploads/template_28_7a734b11232065691bc1176040cb26ad_topics.php(5116): IPS\Theme\_SandboxedTemplate->__call('postContainer', Array) #2 /system/Theme/SandboxedTemplate.php(61): IPS\Theme\Cache\class_forums_front_topics->topic(Object(IPS\forums\Topic), Array, NULL, Array, NULL, NULL, Array) #3 /applications/forums/modules/front/forums/topic.php(576): IPS\Theme\_SandboxedTemplate->__call('topic', Array) #4 /system/Dispatcher/Controller.php(118): IPS\forums\modules\front\forums\_topic->manage() #5 /system/Content/Controller.php(50): IPS\Dispatcher\_Controller->execute() #6 /applications/forums/modules/front/forums/topic.php(39): IPS\Content\_Controller->execute() #7 /system/Dispatcher/Dispatcher.php(153): IPS\forums\modules\front\forums\_topic->execute() #8 /index.php(13): IPS\_Dispatcher->run() #9 {main}

Looks like changing it to mysql did the trick. Thank you!

Done!

It did not correct the problem.

Invision Community Version 4.7.2.1 Version 8.1.11 I just updated to php 8.1 from 7.4, and now I have these errors for various pages, all generated by "guest" Error: Failed opening required '.../datastore/widget_activeUsers_rhsfib2aw_d7c41f2f94c103e97be4ddedfdab8efc.a1d28ee3cc.php' (include_path='.:/opt/cpanel/ea-php81/root/usr/share/pear') (0) #0 /(server path to IP)/system/Data/Store/FileSystem.php(178): IPS\Data\Store\_FileSystem->get('widget_activeUs...') #1 /(server path to IP)/system/Data/AbstractData.php(126): IPS\Data\Store\_FileSystem->exists('widget_activeUs...') #2 /(server path to IP)/system/Data/Store.php(303): IPS\Data\_AbstractData->__isset('widget_activeUs...') #3 /(server path to IP)/system/Widget/Widget.php(904): IPS\Data\_Store->__isset('widget_activeUs...') #4 /(server path to IP)/uploads/template_28_94a9d7649fb9cdbfc784d3516e61a717_global.php(18493): IPS\_Widget->__toString() #5 /(server path to IP)/system/Theme/SandboxedTemplate.php(61): IPS\Theme\Cache\class_core_front_global->widgetContainer('footer', 'horizontal') #6/(server path to IP)/uploads/template_28_94a9d7649fb9cdbfc784d3516e61a717_global.php(6877): IPS\Theme\_SandboxedTemplate->__call('widgetContainer', Array) #7/(server path to IP)/system/Theme/SandboxedTemplate.php(61): IPS\Theme\Cache\class_core_front_global->globalTemplate('Making a normal...', '\n\n\n\n<div class=...', Array) #8 /(server path to IP)/system/Dispatcher/Dispatcher.php(173): IPS\Theme\_SandboxedTemplate->__call('globalTemplate', Array) #9 /(server path to IP)/system/Dispatcher/Standard.php(113): IPS\_Dispatcher->finish() #10 /(server path to IP)/system/Dispatcher/Front.php(625): IPS\Dispatcher\_Standard->finish() #11 /(server path to IP)/system/Dispatcher/Dispatcher.php(155): IPS\Dispatcher\_Front->finish() #12 /(server path to IP)/index.php(13): IPS\_Dispatcher->run() #13 {main} BACKTRACE #0 /(server path to IP)/init.php(1029): IPS\_Log::log('Error: Failed o...', 'uncaught_except...') #1 /(server path to IP)/system/Widget/Widget.php(939): IPS\IPS::exceptionHandler(Object(Error)) #2 /(server path to IP)/uploads/template_28_94a9d7649fb9cdbfc784d3516e61a717_global.php(18493): IPS\_Widget->__toString() #3 /(server path to IP)/system/Theme/SandboxedTemplate.php(61): IPS\Theme\Cache\class_core_front_global->widgetContainer('footer', 'horizontal') #4 /(server path to IP)/uploads/template_28_94a9d7649fb9cdbfc784d3516e61a717_global.php(6877): IPS\Theme\_SandboxedTemplate->__call('widgetContainer', Array) #5 /(server path to IP)/system/Theme/SandboxedTemplate.php(61): IPS\Theme\Cache\class_core_front_global->globalTemplate('Making a normal...', '\n\n\n\n<div class=...', Array) #6 /(server path to IP)/system/Dispatcher/Dispatcher.php(173): IPS\Theme\_SandboxedTemplate->__call('globalTemplate', Array) #7 /(server path to IP)/system/Dispatcher/Standard.php(113): IPS\_Dispatcher->finish() #8 /(server path to IP)/system/Dispatcher/Front.php(625): IPS\Dispatcher\_Standard->finish() #9 /(server path to IP)/system/Dispatcher/Dispatcher.php(155): IPS\Dispatcher\_Front->finish() #10 /(server path to IP)/index.php(13): IPS\_Dispatcher->run() #11 {main}

Got it. Thanks!

I'm trying to access /api/forums/posts?key=xxxx. However, I cannot access any URL of the API, because I get the following error. { · errorCode: "2S290/8", · errorMessage: "IP_ADDRESS_NOT_ALLOWED” } I don’t think the GET requests of the API do need to be blocked by IP address, because those are read only. Although, the POST requests should be blocked, because those allow the user to create entries. I assume this is why the .htaccess file is blocking POST requests and filtering by IP address. How do I open GET request access to /api/forums/posts?key=xxxx ?

I did, and that's where I got the information above. Didn't help because it doesn't work. That's why I posted here for help.

I'm trying to use an API method using an API key. Do I need to include the key as a query parameter? If all is working correctly, I expect that we should see the results using https://www.domain.com/developers/rest-api?endpoint=forums/posts/GETindex&key=xxxx Although, it seems strange that you would serve the “endpoint” as a query parameter. Also, “GETindex" seems strange. As I read the documentation at https://invisioncommunity.com/developers/rest-api?endpoint=forums/posts/GETindex, I would expect the endpoint “/forums/endpoint” to be directly in the URL. Something like https://www.domain.com/developers/rest-api/forums/posts?key=xxxx. You seem to be trying to mimic the URL of the documentation, but I have no idea what you are doing on your end to serve the endpoint. To be more clear, I expect https://www.domain.com/developers/rest-api to be root of the API. Then the following GET endpoints would serve posts and topics respectively. /forums/posts /forums/topics Since we are using an API key, put that in a query parameter ?key=xxxxx. https://www.domain.com/developers/rest-api/forums/posts?key=xxxx Thoughts?

The first link I sent you was an example of somebody who was able to post on a 15 year old topic that should've been archived. Just had somebody moments ago post on a 9-year old topic. Clearly archiving isn't working.

Huh? The thread was from 2006. Nobody had posted on it since, until 2 days ago - 15 years later. If it had been archived, nobody should have been able to post on it, right? As mentioned above, the archive process started 6 weeks ago. That topic should have been archived, ergo that recent post should not have been possible on a 15 year old topic. But at any rate, I just PM'd you a topic from 2004. Go ahead and post on that then. It should be archived, but it's not.

Just sent a PM. I cannot find any that are archived.

6 weeks after setting it to "7 years", people are still posting on 15yr-old topics. My forums aren't that big. So....is the process really that slow? Should I wait several months?

I looked at the main dashboard and it didn't show any processes running. If an archive process is running, it should be showing that it's running. Doesn't make sense that it wouldn't.

IDK what's going on, but it appears the archive function is actually deleting posts. I have a lot of "We could not find that topic." errors in my logfiles now. So I turned it off.

A few weeks ago, I set the archive to 7 years. The process completed within days. However users are still finding and posting on decades-old threads such as this one today: Why aren't the pages archived?

Yes, plus mainEntityOfPage, Name, and URL values (see my OP for example). Thank you!

I get the software assumes it's installed at the root directory, hence the way the Schema is coded. But it's not installed in the root directory, so the Schema information is incorrect. The software has no provision for that use case (installed in something OTHER than the root). That is the problem.

Well, no, it's not correct. The schema is wrong. You're saying it cannot be fixed? Seems like a bug then, because you should be able to edit it for instances like this.

I noticed the Organization schema works IF the TLD is the forums. However, that's not the case for us. Instead, IC a directory off the the TLD (i.e. https://TLD/forums). In this instance, the schema ends up like this: @type Organization @id https://www.TLD/forums/#organization mainEntityOfPage https://www.TLD/forums/ name Name of Forums url https://www.TLD/forums/ Where it should be: @type Organization @id https://www.TLD/#organization mainEntityOfPage https://www.TLD/ name Name of Website url https://www.TLD/ Is there a method to fix this?

Cool. Both sides pointing fingers at each other, confident the other side is at fault. Neat.