BN_IT_Support
Clients
-
Joined
-
Last visited
-
-
Hello, This is a change from V4 (and not a welcome change 😉)... If I create a blog entry I immediately get a banner across the top of the page that says: "Your content will need to be approved by a moderator". This is different from V4 where we just let the members create whatever blogs they wanted (same as we did for the forum topics and posts). If any content was posted that breached community guidelines then the moderators would hide/remove the content and take appropriate action. (If moderators missed the content then someone else would report it in due course - this worked well...) We do not want to have to have our moderators approve all blogs - this would disrupt the free flow of the site. It is entirely possible (although unlikely) that I have overlooked some setting - please provide "appropriate feedback" (!!) is this is the case. Group setting "Can moderate own blog entries?" set to 'off' - it seemed to make no difference and we want it set to off. Group setting "Content: Bypass content moderation?" set to 'off'. Group setting "Content: Require approval before content shows?" set to 'off' Thanks. John
-
-
-
Esther, Thanks - sorry for the duplicate. I could not find my earlier cron bug and as the problem had "gone away" for a time and then "reappeared" I erroneously presumed it was a different bug. Thanks. John
-
Hello, Most days I get an email showing a cron failure. When I look in the system logs for the time of the email I find an entry: Error: Call to undefined method IPS\core\extensions\core\IpAddresses\Content::pruneIpAddresses() (0) #0 /home/bn2468/public_html/applications/core/tasks/pruneipaddresses.php(51): IPS\Member::pruneAllLoggedIpAddresses() #1 /home/bn2468/public_html/system/Task/Task.php(343): IPS\core\tasks\pruneipaddresses->execute() #2 /home/bn2468/public_html/system/Task/Task.php(306): IPS\Task->run() #3 /home/bn2468/public_html/applications/core/interface/task/task.php(78): IPS\Task->runAndLog() #4 {main} Thanks... John
-
Hello, [5.0.0] Add Similar Event" fails to set lat/long in event_location and fails to set event_latitude or event_longitude That pretty much defines the problem ;-) Thanks. John
-
Hello, "Add Similar Event" fails to fire UIItem::formElements (and presumably it does not fire any of the other methods in that extension) Not sure what else to say - it just does not fire it! Thanks. John
-
Hello, When my application calls Event::retrieveEvents with $skipPermissions=true I get the following Exception: TypeError: IPS\Content\Item::getItemsWithPermission(): Argument #4 ($permissionKey) must be of type string, null given, called in /home/bn2468/public_html/applications/calendar/sources/Event/Event.php on line 2228 (0) #0 /home/bn2468/public_html/applications/calendar/sources/Event/Event.php(2228): IPS\Content\Item::getItemsWithPermission(Array, 'event_start_dat...', NULL, NULL, true, 0, NULL, false, false, false, false, NULL, false, true, true, true, false, NULL) #1 /home/bn2468/public_html/applications/bncal/modules/front/calendars/view.php(575): IPS\calendar\Event::retrieveEvents(Object(IPS\calendar\Date), Object(IPS\calendar\Date), NULL, NULL, true, NULL, NULL, true, NULL, 0, Array) #2 /home/bn2468/public_html/system/Dispatcher/Controller.php(128): IPS\bncal\modules\front\calendars\view->events() #3 /home/bn2468/public_html/applications/bncal/modules/front/calendars/view.php(27): IPS\Dispatcher\Controller->execute() #4 /home/bn2468/public_html/system/Dispatcher/Dispatcher.php(169): IPS\bncal\modules\front\calendars\view->execute() #5 /home/bn2468/public_html/index.php(16): IPS\Dispatcher->run() #6 {main} Note the comment: * @param bool $skipPermissions Skip permission checks (used by REST API to fetch all events which are filtered on later) So I presume the API is also broken (as well as my application). Thanks. John
-
-
-
-
Hello, I upgraded to 4.7.20 but cannot find the matching SDK. (I know, I know, I should have checked for the SDK before doing the upgrade but it did not cross my mind that it would not be there!) Thanks. John
-
Hello, I think it probably makes sense to allow more than one SSO handler - for example some users of your platform might have logged into “service-1” and others might have logged into “service-2” and if both services have the potential for SSO login to IPS then you would want two SSO handlers - if the first one succeeds then don’t try the second one (or any other subsequent ones) but if the first one fails then you would want to try the second (and subsequent) in case a later one returns success. It appears to me that the way that Session/Front works it does not get any signal back from the SSO handler to say either “keep on trying” or “we now have success so stop trying any more SSO handlers”. The problems… SSO::onSessionRead() is only called for the first SSO handler in the chain. foreach( Application::allExtensions( 'core', 'SSO', FALSE ) as $ext ) { /* @var SSOAbstract $ext */ if( $ext->isEnabled() ) { return $ext->onSessionRead( $this, $result ); } } SSO::onInit() is called for ALL SSO handlers - so if (for example) the first one is successful Session/Front still continues on down the chain looking for further SSO handlers: foreach( Application::allExtensions( 'core', 'SSO', FALSE ) as $ext ) { /* @var SSOAbstract $ext */ if( $ext->isEnabled() ) { $ext->onSessionInit( $this ); } } Of course, the order of discovery (in the ‘foreach’) is pretty random so the ‘first’ in the description above is pretty random. Even if you were going to make this controllable (sort order) in the future it would be nice to implement the ‘keep on trying’/’all done’ signal now so that my SSO code does not have to be modified in the future ;-) Adding to the above — another problem that I ‘discovered’ just before submitting this… The session data is ‘saved’ BEFORE SSO::onSessionRead() is called and the session data includes details of the logged in member - so, if the SSO module changes the logged in member the session data would be out of date (incorrect). There is no way for the SSO module to update the session data itself as the session data is ‘protected’ and thus only available to variants of Session. /* Set data */ $this->data = array( … Thanks! John
-
-
Marc, Would you move the bug report over for me? (Or do I need to re-post in the correct place?) Thanks. John
-
-
Hello, As a preamble to this bug report, I’m somewhat confused about where I am supposed to report bugs. The “Beta Discussion” in the IC5 Beta Testing club says “Got a bug? Please post it in our tracker.“ but that takes me to a no-access page. The “New public bug tracker” topic takes me to the “feedback” forum where there appear to be a lot of V4 issues? I’ll try here and see whether it gets moved ;-) I previously reported a bug where Loader::onFinish() does not get called for “database pages”. That is still the case. This report is for additional (possibly related) issues. When using the Page Editor on a simple single column page there are three widget areas - top, middle and bottom. It appears that Loader::onFinish() ONLY gets the content of the “middle” area so that the content of any widgets in the top or bottom areas does NOT get passed to Loader::onFinish(). If that is intended behaviour then it needs to be clearly documented The workaround is relatively simple (for non-database pages) → just drag and drop the widgets into the middle area and test again The next problem is for “database pages”. When a database is created under IC5 a new page is automatically created and the database widget is placed in the middle area. The issue is that the middle area is greyed out in the editor so it is NOT possible to drag and drop any other widgets into the middle area. Thus, the only option for additional widgets is to put them in the top or bottom areas but in those cases they will not appear in Loader::onFinish(). Thanks. John
-
Hello, This seems more complicated under V5 than under V4 and it feels like there is a bug (or at least a deficiency) here - but I'm not sure so I'm starting this as a discussion rather than a bug report... Under V4 this all seemed to work simply. I could run my test system with IN_DEV enabled and if I created a custom Database Template (e.g. type = Category List - first page when viewing a database) then it would work whether IN_DEV was enabled or not. Under V5 it appears that custom templates created this way only work when IN_DEV is disabled. As soon as IN_DEV is enabled then accessing the database gives a "NO_TEMPLATE" exception because when IN_DEV is enabled under V5 the system expects to find the template files in applications/cms/dev/html/front/databases/etc... and the files are not there. Just the fact that it used to work simply under V4 leads me to feel this is a retrograde step that should be logged as a bug. It is possible to work around the above problem by creating files in the appropriate directory. Of course, most of the file content is a straight copy-and-paste from the template file as viewed in the ACP. But, in addition to that content it is also necessary to insert the line at the top ... something like "<ips:template parameters="$category"/>". What is the expected workflow? The easy way to create templates as the starting point for customisation is in the ACP. But as described above, there is no obvious way to output the templates to files so the workaround is copy and paste with the insertion of he additional header line. The alternative would seem to be to hand-craft the files in the relevant folders and then use the "Import Developer Templates" button to upload all files as templates. That's a nice idea except there is no really easy way to create the starting point! When using the Developer Center to modify one of our applications it is possible to use the Front-End Pages Templates option to select templates to be included with the application. How does that play with the previous comments? Does this option save from the template/dev files or from the information held within Invision tables? Thanks very much. John
-
-
-
-
BN_IT_Support replied to Matt's post in a topic in Invision Community 5: Beta Testing's Beta DiscussionWhile I agree that it would be really great to have the V5 developer documentation "sooner rather than later", you really don't have to wait for the V5 documentation before you start some development. Use the V4 developer documentation PLUS the V5 developer blogs (https://invisioncommunity.com/developers/devblog/). The really big thing is that in V5 it is NOT POSSIBLE to use V4 style 'HOOKS'. If you read the documentation and conclude that you need a V4 HOOK then you are going down the wrong path - read the Dev Blogs and work out how to do it under V5. There are a few useful things that have been added since the V5 Dev Blogs were written and they're not documented yet. But, if you're only just starting to do your development then you're 99% OK if you (1) Use the V4 docs, plus (2) AVOID V4 HOOKS and (3) use the V5 Dev Blogs. Finally, there are people in the forum who will give you pointers if you get stuck on V5 development. John
-
-
BN_IT_Support replied to Matt's post in a topic in Invision Community 5: Beta Testing's Beta DiscussionWell, if you did not delete ALL old DEV files first -- i.e. before copying the latest dev files to your system then I strongly recommend that you check the file dates on all your dev files. (It's a lot easier and quicker to clear out the dev folders first as checking file dates of thousands of files takes time...) You're partly correct that the upgrade of a dev system will go OK. That is, it should be fine as long as you stay OUT of dev mode. If you switch to dev mode and if you did not clear out all the old dev files then there is a strong possibility that some old dev files (CSS and/or JS) will get loaded -- it's just the way that loading CSS and JS works -- it does not load individual CSS or JS files but bundles them so if the old/stale file has a name that matches one of the bundles then it will get picked up and loaded even though you don't want it. When I had stale CSS and JS files in dev mode then pretty much everything worked -- except a few things like some things did not look quite right and I ended up submitting bug reports for things that were just stale files. So, in particular, if you intend to log bug reports I suggest you make sure you don't have stale files hanging around. John
-
BN_IT_Support replied to Matt's post in a topic in Invision Community 5: Beta Testing's Beta DiscussionJust a warning for those thinking of upgrading from V4... I suspect that if your system was relatively recently installed (as V4) for the first time then all may well be OK. But, if your system was initially installed as V4 some time around 4th October 2019 or earlier then expect problems... If you can log in then the pages will display as blank. The issue is the following files: applications\core\extensions\core\FrontNavigation\Promoted applications\nexus\extensions\core\FrontNavigation\NetworkStatus applications\nexus\extensions\core\FrontNavigation\Referrals The above files do not exist in V5 but were present in some very old version of V4 (possibly 4.4.7 or older, but I'm not sure). The way the system loads menus is it searches for files in those folders and attempts to load them but as the files have not been converted to V5 then PHP crashes and you end up with blank pages. The 'fix' is to delete the files and your pages will automagically reappear when you refresh your browser. This has previously been reported as a bug - but the answer at that time was that the upgrade would not delete any files. Fair enough - I don't care because I know what to do. If you don't know what to do then expect to trip up 😉 I have a feeling that when I enable IN_DEV mode then I'll run into lots of problems with CSS and JS files being out of date and maybe some others. I think the best advice at this point is to delete ALL dev folders before you install the dev kit John Yes - I can confirm it works (with the warning described above). Download the V5 ZIP Unpack the ZIP Copy the folders over the top of the existing folders Browser /admin/upgrade and log in with your normal adminCP credentials (NOT you invision community credentials) Basically, follow the Installation manual "Manual Install" section. John
-
Hi Matt, I need an installable kit so I can start converting our many applications and plugins. I guess that probably means that I'll have to wait for beta? But the sooner that I can have an installable kit and start converting plugins and applications the better... Thanks. John
