-
Posts
6,568 -
Joined
-
Days Won
37
Content Type
Downloads
Release Notes
IPS4 Guides
IPS4 Developer Documentation
Invision Community Blog
Development Blog
Deprecation Tracker
Providers Directory
Forums
Events
Store
Gallery
Posts posted by Daniel F
-
-
On 9/2/2021 at 7:45 PM, opentype said:
I've noticed some weird stuff while working on the ticket from @Ocean West but before I fix it , I've also created a ticket for you which I've assigned to myself to take also a look at your installation to see if both have literally the same issue.
-
8 minutes ago, Lucas James said:
This app is causing an issue with a theme that was recently updated. This is the only app/plugin that conflicts and causes the theme to break and not work until I disable the Forms App. Any ideas? Thanks
What exactly is crashing? What's the error?
-
-
Yes, they have a limit of 500 emails per day
QuoteYou may see this message if you send an email to a total of more than 500 recipients in a single email and or more than 500 emails sent in a day.
-
What browser were you using for the testing?
-
This sounds like a bug.
App/Theme/Plugin installations and upgrades will already trigger all necessary cache rebuilds.4 minutes ago, CheersnGears said:Bumping this to maybe get some sort of response from IPS..... just upgraded a few applications and my site slowed to a crawl until I cleared the cache.
What exactly was so slow? And how exactly did you clear the caches? Via the new Support Tools page?
-
-
-
$theme->css_updated will contain the timestamp of the last rebuild.
-
The /core/clubs endpoint will return only visible clubs if you're using oAuth 🙂
/** * GET /core/clubs * Get list of clubs * * @apiparam int page Page number * @apiparam int perPage Number of results per page - defaults to 25 * @note For requests using an OAuth Access Token for a particular member, only clubs the authorized user can view will be included * @return \IPS\Api\PaginatedResponse<IPS\Member\Club> */
That said, I have raised an internal suggestion to add an additional parameter to pass a specific member
-
Were you able to resolve this in the meanwhile?
If not, what was the logged error?
On 8/9/2021 at 10:46 PM, Askancy said:resulted in a `500 Internal Server Error` response:
-
Were you able to resolve this in the meanwhile? If not, what's your current code?
-
Were you able to address this issue? If not, what's the full error which is returned?
-
Take a look at Node::roots() 😉
Unfortunatly there are few cases where nodes are handled different and this is one...
Node::roots() won't call the constructLoadQuery method, but you'll be able to add your own data to the AR object inside the constructFromData() method. -
On 8/25/2021 at 5:33 PM, IPCommerceFan said:
Ahh, I thought it conspicuous that 1 wasn't a 0 (my assumption being it represented the first item in an array)
I've modified it to indicate the language key for the logged in member:
$form->add ( new \IPS\Helpers\Form\Translatable( 'dripcampaigns_step_vin_regex', NULL, NULL, array( 'placeholder' => '/[A-Z0-9]+/i', 'app' => 'dripcampaigns', 'key' => $this->id ? "dripcampaigns_step_vin_regex_{$this->id}" : NULL ), function( $val ) { $langID = \IPS\Member::loggedIn()->language()->id; if ( $val[$langID] AND @preg_match( $val[$langID], NULL ) === false ) { throw new \DomainException( $val[$langID] . ' is not a valid regex string.'); } } ) ); return parent::form( $form );
Thanks again!
Why would you even use a translatable field with a validation?:D
What's going to happen if you're logged in with the "English" language in your ACP, and you set English and French and there's a typo in the French field? It won't return any error, right?;)So you'll literally have to save the form, change the ACP language to French and resave the form again to run the validation for the French field
Sorry, I'm just nitpicking, and I guess you know what you're doing, but had to mention it for anybody else searching for something similar and finding the topic and your (bad code:P ) 😄
-
Adriano's code will disable the app completely, which I guess is also not what you want:D
1. You'll have to tell us how you're changing the navigation:D
2. You *could* use \IPS\Member::loggedIn()->skin to get the members theme id and do something like:
{{if \IPS\Member::loggedIn()->skin === 3}} this will be displayed only in theme 3 {{else}} everybody else will see this {{endif}}
Something similar could be done in Theme::hookData(). It's really a powerful system, so I would suggest to spend some time to see how exactly it's working:)
You could also create a hook on Template::compileTemplate to do whatever you want there, for example to remove the hook before the template is compiled;) BUT I'm afraid, that's just asking for trouble and it's something what you could do for your own board, but I don't think that we would allow such changes in the marketplace!
- Gregory Gleinig, ReyDev and Adriano Faria
- 2
- 1
-
Looking at your first and second code there's also something else..;)
if ( $val AND @preg_match( $val, NULL ) === false )
In your first attempt you were assuming that $val is a string, but it's literally an array with the language ID as key and the string as value .This means that even your current code with $val[1] could result in an error!
-
Thanks, I have added this step to https://invisioncommunity.com/developers/docs/development/extensions/coremodcp-r151/
-
9 hours ago, IPCommerceFan said:
Does Translatable support $customValidationCode as of 4.6.5.1?
This was supported since 4.0.x !
Take a look at applications/core/extensions/core/FrontNavigation/CustomItem.php for an example 🙂 -
You can use the ban filters for this. ( ACP => Members => Ban Settings )
-
49 minutes ago, mark2012 said:
have an option regarding groups Posting Limits and Max items of content (posts, comments, etc.) per day, which i actually set it up as 10 per day. But for some reason new topics are not included here.
This sounds like a bug to me, which I have raised internally.
-
-
Hi,
could you please reupload the file to the marketplace.
-
This will require a plug-in
WYSIWYG Editor Block only in pages?
in Technical Problems
Posted
It seems that this was a bug in our upgrader.
The WYSIWYG widget was indeed limited to be used in the pages app in the past, but we changed this 2018 for IPS 4.3.4 (geez, time flies:D ) , but due to a bug in our upgrader, the restriction was never changed, so all instances which were installed before we made the change were unfortunatly not able to use the widget outside of the pages app, while new installations were, hence the problem with reproducing it.
I have fixed this now for an upcoming release 🙂