Jump to content

Community

Marcher Technologies

+Clients
  • Posts

    17,657
  • Joined

  • Days Won

    98

 Content Type 

Profiles

Downloads

IPS4 Providers

Release Notes

IPS4 Guides

IPS4 Developer Documentation

Invision Community Blog

Forums

Store

Posts posted by Marcher Technologies

  1. Yes, I am fully aware I can do this by extending the KeyValue form helper class. Every, single, time I want to use something not a text input for the key or value. Can we pass this as an option like 'keyFieldType' and 'valueFieldType', defaulting to Text instead, and pass the field type specific options through to them with something like 'keyFieldOptions' and 'valueFieldOptions' please?

    For reference, I often use this field with the Stack field type, so such a change would need supported with this field type as well to be of value.

    For example:

    $form->add( new \IPS\Helpers\Form\Stack( 'my_setting', $values, true,
        [ 'stackFieldType' => 'KeyValue', 'keyFieldType' => 'Url', 'valueFieldType' => 'YesNo' ] ) );

     

  2. 1 hour ago, Joey_M said:

    I've got two hidden posts which I cannot locate or delete, I've only found them in a third-party app.

    If I click on them it says they cannot be found.

    Unrelated to the original post, should probably submit a ticket so staff can take a look at your database and see if it's something that needs fixed in the codebase.

    4 hours ago, TSP said:

    When hiding a single post (from the Options menu on the post) you are taken back to the page you where on. This is good and works as expected. 

    However, when using the multi-select tool and choosing to hide from the moderator toolbox overlay, then you are taken back to the first page. You should be left on the page you were on. 

    Please note, I am NOT arguing against this. That tool allows one to select posts across pages of a topic. Please define what it should do if you select a post on page 1, 5, 10, and 15 to delete while viewing page 20, which no longer exists as of deleting those posts.

    This is the kind of thing that the code has to account for in honoring this request.

  3. I'm not sure why, but when developing, ergo IN_DEV = true, the 'log in as' feature lasts not even 2 minutes.

    This results in a ridiculous amount of time waste when one needs to develop against and test a multitude of access levels and configurations.

    Is there a constant I can set to a member id to make 'log in as' stay put long term while IN_DEV?

  4. Not precisely what you are after, but close. Fluid view enabled: https://invisioncommunity.com/forums/?forumId=492%2C497%2C406%2C503%2C504%2C238%2C500%2C442%2C431%2C506%2C477%2C320%2C493%2C15

    On 2/9/2019 at 12:53 AM, opentype said:

    Can’t be done. None of the main app views can just be called (customized or not) somewhere else. There is alsways just one “index page”. 

    Not remotely true. Every view can be abused and called up within any other view. Just a matter of actually knowing the code well enough to do so. CMS app does this natively, in fact, with custom database views completely outside of the norms called up via the 'pages' view.

  5. Wrong dispatcher would be my guess. You'd want to use the Front dispatcher, not the External, and initiate the member session with \IPS\Session\Front::i(); before calling the dispatcher run.

    Please note, this is only a guess, and is untested, but it makes logical sense that using the external dispatcher like this would cause widgets to go awry.

  6. It is possible with code in a manual HTML page actually. Much less so with a page builder page. Check against \IPS\Member::loggedIn()->language()->id or if preferring to check against locale strings instead of numbers, \IPS\Member::loggedIn()->language()->short

    Despite the apparent use of a logged in member object, this works for guests as well due to the way \IPS\Member works.

    Alternatively, see this post. In 3.x any admin could just add a language string, but that was removed from the core in 4.x, or I would have just said to dump them into the language system to begin with.

  7. If the method is commented to have @apiclientonly in the docblock, instead of denying only  OAuth Access Token use, it denies any use other than API key. 

    This is directly counter the documentation: https://invisioncommunity.com/developers/rest-api?endpoint=core/members/POSTindex

    On the surface, the problem seems to be that such methods are not actually available to be granted permissions in the scopes selection form in the ACP for Oauth Client Credentials.

    I can't imagine this is intended given the documentation and code. I would appreciate it if this could be looked into, thank you. It is vastly preferred to use the security superior oauth for such work.

  8. In the vein of this: 

    And in the  train of thought of avoiding doing this:

    Can the hunk of code that actually 'follows' and 'unfollows' things in IPS\core\modules\front\system\notifications be abstracted out to actually be on the item/node object, or anywhere it could actually be reused?

    The above reason is not the first time I have needed to control follow status dynamically, and currently such strays extremely close to a direct copy-past of a large chunk of code that is not desired to be maintained by me, and falls foul of the license agreement.  

     

  9. {expression="var_export($variable, true)"}

    I use the above. var_dump does not return a result. it literally just prints to screen.

    On 1/23/2018 at 2:22 PM, opentype said:
    
    {{$varoutput=var_dump($variable);}}
    {$varoutput}

    I always do it like this. 

    To clarify, the second line there, and indeed, setting the $varoutput variable itself, is a meaningless no-op because var_dump was used.

    {{var_dump($variable);}}

    is the exact same thing as the code you posted.

    I prefer var_export both for control of placement of result and because I have seen var_dump do nothing on some servers due to the output buffering used in the suite, thus var_export consistently gives me the debug i'm looking for without fighting install-specific semantics.

  10. opentype, I fully understand your position, and it indeed seems nonsensical to think google would drop already indexed pages for lack of a sitemap. Thing is.... the Google 'Fred' algorithm update actually arbitrarily culled thousands if not millions of pages from google's index. not as any penalty for black hat, but as a measure to curb their own storage needs, and the only thing getting them back in google's index is the sitemap. It's not the lack of a sitemap entry itself causing them to be dropped, it's Fred that dropped them, and the sitemap as the main route of recovery.

  11. Failed to load resource: the server responded with a status of 403 ()
    https://dne4i5cb88590.cloudfront.net/invisionpower-com/page_objects/homepage2.css.23f95b3edd9258e7c37d05e34e9f8444.css?v=bf33ac44f2

    getting some severely unstyled content on the homepage, dropped caches and checked other browsers to be sure it wasn't a temporary fluke, just thought you should know

  12. Hello Brandon,

    I feel obliged to remind you sorting in php itself here(or really anywhere where one is dealing with a query result set with a limit) is completely unreliable, thus this needs reworked to begin with. Let's say I have a result set needing ordered by submission, or ordered from z-a(it happens). To try to sort it in php *after* already limiting the result set means the results are wrong. The last 10 submissions, are not the last 10 if one pulls the result set limited from db not sorted by date, but then sorts it in php by date. That is merely 10 random records reordered. As it stands, the helper currently sorts by length in database, then resorts in php. This, as detailed above, is in no way reliable.

  13. @jair101, please stop being deceptive. No app or plugin to date has done this due to 4.2. Themes have. The large template differences may warrant it, but don't lump app and plugin authors in with themers. Our woes are not equivalent to theirs, and often we can ignore template updates where themers can not. Your wording was designed to lead this topic towards the thought of apps, when in fact this is about themes. Taken in the context of themes, a complex theme may be justified in re-release, there were indeed a LOT of template changes.

  14. .... um.... it's a brand new domain, so of course it wouldn't be in a security database. It will keep doing that until the domain is 'classified' as per the bottom set of instructions.

    Thanks for the screenshot, that makes more sense.

  15. 18 minutes ago, Lindy said:

    Could you send me some details on that? Any idea why your firewall might be flagging it?

    Maybe for the same reason I did a whois on the domain before trusting it? I actually was convinced i had somehow been directed to a phishing site upon waking.

  16. 10 hours ago, Matt said:

    I think you've found the solution, use the activity streams to do this. It would effectively duplicate the functionality.

    Please add a 'list' view to streams then? I find the fluid(or even topic listings in a forum) view much easier on the eyes than the 'stream' format in whole. I have primarily avoided AS because the format is not very useful in providing information at a glance. I find the expanded view jumbled and confusing, and the condensed view gives far too little information. Not saying it actually is these things for all users, just that it would really help in AS usage for many, while identifying a potential reason people are asking for this feature in fluid view to begin with.

×
×
  • Create New...

Important Information

We use technologies, such as cookies, to customise content and advertising, to provide social media features and to analyse traffic to the site. We also share information about your use of our site with our trusted social media, advertising and analytics partners. See more about cookies and our Privacy Policy