primordic/IssueDupesLite huggingface dataset:
Repository: osTicket/osTicket

Issue #1985: KB Error on file upload
Created: 2015-04-21T09:19:05Z
Test case:

Create FAQ with attachment
Edit FAQ
Try add file bigger than allowed size, you must get message File Upload Error - File is too large - Press OK
Again try add file but now press Cancel in file dialog, you get message File Upload Error - Your browser is not supported. File added at step 1 disappear from FAQ

1.9.7+chrome

Duplicate issue #2606: v. 1.9.12 - Knowledgebase attach file on create FAQ get lost
Created: 2015-10-01T13:01:27Z
Hey,
like written above attachments get lost, when opening a new FAQ and u save it.
Afterwards u can edit and add it fine again.
Problem was recognized on 1.9.7 (maybe already earlier) and still exists on 1.9.12.
CHEERS!

Closing comment (2015-11-16T18:15:08Z): I have the same issue as Hannibal226.
Upon first creating a new Knowledgebase FAQ, whatever I type is saved. If I have added an attachment as part of creating the new article however, the attachment is not saved to the newly created KB article.  I can then open my just-created article, add my attachment, and the attachment will still be there after I save the article a second time.
This issue is NOT browser specific, as it manifests in Firefox 42, Chrome 46, and IE 11.
It also happens for any size attachment, so not the same as #1985
osTicket v1.9.12, Apache 2.2.22, MySQL v5.5.46, PHP v5.3.10-1ubuntu3.21
Repository: osTicket/osTicket

Issue #3264: 1.10 - Ticket list export outputs only two first lines
Created: 2016-07-11T10:54:45Z
When you click "export" on any ticket list (opened, closed, owned, searched), the CSV generated includes only the first TWO lines.
This also affects to any the result of a search.
The apache logs shows this:
PHP Warning:  mysqli_result::close(): Couldn't fetch mysqli_result in /site_1.10.rc3/include/class.orm.php on line 3076, referer: http://------------------/scp/tickets.php
osTicket 1.10.rc3
Centos 6.8 64b
mysql 5.1
php 5.6
Thank you.

Duplicate issue #3841: Export All Close Ticket | Only 2 tickets are exported to csv.
Created: 2017-06-07T07:38:54Z
Prerequisites

[No ] Do you have any errors in the PHP error log, or javascript console?
[Yes ] Did you check the osTicket forums?

Description
When i try to export all closed ticket to csv. I only got 2 of the results instead of all from table. I try to check them all but same results. No luck.
Expected behavior: it should print all of the ticket number from the table.
Actual behavior: Only 2 tickets from the table was extracted.

Result

Versions
osTicket (v1.10)
Windows 7 64

Closing comment (2017-06-08T01:58:40Z): Duplicate #3264
Repository: oss-review-toolkit/ort

Issue #7436: WebApp reporter should always show effective license
Created: 2023-08-31T14:00:11Z
If there is no declared license and no detected license (e.g. because the scan step is skipped due to a concluded license), the webapp reporter does not show any licenses, even though an effective license should be present and therefore I think it should be shown in the report.
Example:
We have a curation with concluded_license and authors for Protobuf:3.19.8 and even thought the correct license appears in the disclosure document, there is no information regarding the license in the WebApp. Still, the author information from the curation is shown.

Duplicate issue #8038: Show effective licenses in WebApp report's summary tab
Created: 2023-12-14T09:29:10Z
The WebApp report currently show the declared and detected licenses in Summary tab it would be more useful if it showed the effective licenses in the summary e.g. license that actually applies to release artifacts including made license choices. In this way a report report can faster understand which licenses are applicable to the project and thus determine their license obligations.

Closing comment (2023-12-14T09:48:07Z): Sounds like a duplicate of #7436, or?
Repository: oss-review-toolkit/ort

Issue #2424: Read configuration files from default location
Created: 2020-03-26T15:54:48Z
ORT uses many configuration files, for example for curations, license configuration, and custom license texts. Currently these need to be passed to the ORT commands as command line options. To simplify usage, ORT should by default look for those files in the ~/.ort configuration directory, for example ~/.ort/curations.yml.

Duplicate issue #2756: Align on reading all config files from config directory by default
Created: 2020-06-22T11:25:04Z
The code base currently is a bit inconsistent about what files are read from ~/.ort/config by default. For example, the main ORT configuration file (in HCOCN format) ort.conf is read from ~/.ort/config/ort.conf if no other file is specified. The same goes for the Analyzer's curations.yml, but not for the Evaluator's rules.kts. This should be aligned to read all basic configuration files from ~/.ort/config by default to a full ORT pipeline could be configued via ~/.ort/config contents only.

Closing comment (2020-10-05T09:41:18Z): Closing as a duplicate of #2424.
Repository: oss-review-toolkit/ort

Issue #3298: Add a report dedicated to documenting security vulnerabilities
Created: 2020-11-06T10:18:35Z
Once we have the advisor / a first provider implementation, we also need to be able to visualize security vulnerability findings. Ideally, this should be done in a separate (PDF) report to reports that document license findings as the target audience is a different one.
Following the idea in #3244 maybe simply create a separate Asciidoc template and fill it out with only security vulnerability information.

Duplicate issue #3336: Create a separate PDF report for security vulnerabilities
Created: 2020-11-16T08:59:02Z
Now, that we have #3282, and once #3329 is merged, we should generate a separate PDF with any found security vulnerabilities, as the target audiences for the attribution / disclosure document and security vulnerability information are usually different.

Closing comment (2020-11-16T09:20:09Z): Duplicates #3298.
Repository: oss-review-toolkit/ort

Issue #3559: Analyzer : Warnings with Clearly Defined Curation Provider
Created: 2021-01-29T13:21:34Z
In our pipeline run, we got these warnings today :
11:46:44.299 [main] WARN  org.ossreviewtoolkit.analyzer.curation.ClearlyDefinedPackageCurationProvider - Getting curations for 'Maven:com.google.code.gson:gson:2.8.6' failed with: MismatchedInputException: Cannot deserialize value of type `org.ossreviewtoolkit.clients.clearlydefined.ClearlyDefinedService$Facet` from Array value (token `JsonToken.START_ARRAY`)
 at [Source: (okhttp3.ResponseBody$BomAwareReader); line: 1, column: 31] (through reference chain: org.ossreviewtoolkit.clients.clearlydefined.ClearlyDefinedService$Curation["described"]->org.ossreviewtoolkit.clients.clearlydefined.ClearlyDefinedService$Described["facets"]->org.ossreviewtoolkit.clients.clearlydefined.ClearlyDefinedService$Facets["dev"])
11:48:54.544 [main] WARN  org.ossreviewtoolkit.analyzer.curation.ClearlyDefinedPackageCurationProvider - Getting curations for 'Maven:com.google.code.gson:gson:2.8.6' failed with: MismatchedInputException: Cannot deserialize value of type `org.ossreviewtoolkit.clients.clearlydefined.ClearlyDefinedService$Facet` from Array value (token `JsonToken.START_ARRAY`)
 at [Source: (okhttp3.ResponseBody$BomAwareReader); line: 1, column: 31] (through reference chain: org.ossreviewtoolkit.clients.clearlydefined.ClearlyDefinedService$Curation["described"]->org.ossreviewtoolkit.clients.clearlydefined.ClearlyDefinedService$Described["facets"]->org.ossreviewtoolkit.clients.clearlydefined.ClearlyDefinedService$Facets["dev"])

It seems something has changed in the responses from the Clearly Defined Curation Provider.

Duplicate issue #3645: clearlydefined parsing exception
Created: 2021-02-18T07:41:21Z
Hello,
I've recently activate clearlydefined in my ort pipeline, and I've got some projects that failed on analyzer error :
[2021-02-17T21:24:22.007Z] 21:24:21.837 [DefaultDispatcher-worker-3] WARN  org.ossreviewtoolkit.analyzer.curation.ClearlyDefinedPackageCurationProvider - Getting curations for 'Maven:com.google.code.findbugs:jsr305:1.3.9' failed with: HttpException: HTTP 404 

[2021-02-17T21:24:22.987Z] Exception in thread "main" com.fasterxml.jackson.databind.exc.MismatchedInputException: Cannot deserialize value of type `org.ossreviewtoolkit.clients.clearlydefined.ClearlyDefinedService$Facet` from Array value (token `JsonToken.START_ARRAY`)

[2021-02-17T21:24:22.987Z]  at [Source: (okhttp3.ResponseBody$BomAwareReader); line: 1, column: 31] (through reference chain: org.ossreviewtoolkit.clients.clearlydefined.ClearlyDefinedService$Curation["described"]->org.ossreviewtoolkit.clients.clearlydefined.ClearlyDefinedService$Described["facets"]->org.ossreviewtoolkit.clients.clearlydefined.ClearlyDefinedService$Facets["dev"])

[2021-02-17T21:24:22.987Z] 	at com.fasterxml.jackson.databind.exc.MismatchedInputException.from(MismatchedInputException.java:59)

Is it a parsing issue from ORT or a wrong content from clearlydefined or a bit of both :-)  ?
regards

Closing comment (2021-02-18T12:14:13Z): This duplicates #3559. Please search existing issues first.
Repository: oss-review-toolkit/ort

Issue #2852: Set processed declared licenses to NONE instead of empty
Created: 2020-07-09T17:49:52Z
We should think about whether it ever makes sense to set a declared license to NONE or NOASSERTION instead of just returning nothing / and empty set, because

NONE seems to be semantically equivalent to "empty",
for NOASSERTION the first case ("no attempt was made to determine the information") is never true because we always tried, and the second case ("intentionally no information is provided") we probably do not really care about, as we're only interested in whether it's empty, but not why.

@fviernau, @tsteenbe, any thoughts on that?

Duplicate issue #3122: Package concluded license: Allow using "NONE"?!
Created: 2020-09-24T12:47:35Z
@sschuberth @tsteenbe @mnonnenmacher : Shall we file a ticket for making "NONE" a valid value for the package concluded license in ORT?
Note that for license finding curations we already do allow that.
Originally posted by @fviernau in #3117 (comment)
I'm a bit undecided. On the one hand it would be consistent to align on SPDX expressions for "everything about licenses". On the other hand, checking for (not) null is much more convenient than checking for isPresent() / isNotPresent(). My hunch is that we should still align on SPDX expression, but I'd like to also hear @mnonnenmacher opinion on that once he's back.
Originally posted by @sschuberth in #3117 (comment)

Closing comment (2020-10-05T09:38:48Z): Very much related to #2852 for declared licenses.
Repository: oss-review-toolkit/ort

Issue #6603: Turn scan storages into plugins
Created: 2023-03-03T09:34:18Z
Scan storages (storage readers / writers) also seem to be a good fit for being implemented as plugins. They should straight use the new org.ossreviewtoolkit.plugins.api.Plugin API.
Some additional notes:

Ideally, this would also address #6460.
And #6765 would probably be a good test case for a new plugin.

Duplicate issue #7075: Plugin support for custom FileStorages
Created: 2023-06-01T08:42:36Z
We would like to use a custom (HTTP) file storage implementation as the existing ones do not fulfil our needs (custom auth in OkHttp client required via request interceptor). In our opinion a valid approach could be to plugin a custom implementation which is then configured via the config.yml file.
@MarcelBochtler / @mnonnenmacher mentioned in todays community call that there might be a bigger refactoring around storages (required) which should also be taken into account.

Closing comment (2023-06-01T15:29:30Z): @vw-anton would you agree that this duplicates #6603?
Repository: oss-review-toolkit/ort

Issue #6698: Configurable URL replacements for the analyzer / downloader
Created: 2023-03-17T03:57:42Z
We need to set some connection configuration of the vcs in general and git in particular, for example whether to use https instead of ssh.
Our current workaround is to place this in the docker entry point:

Duplicate issue #8500: Allow extending URL prefix replacements for Git
Created: 2024-04-09T10:45:54Z
The Git class currently has a hard-coded configuration for replacing URL prefixes, which is limited to replacing the prefix git:// by https://.
In our environment, there was the need to replace a URL like "git@github.com:" (used as a submodule reference and interpreted as SSH) by the URL "https://github.com/". I assume that such replacements cannot be done by ORT in a generic way, since the prefix to be replaced contains a domain; from my research, I found that Git currently does not support wildcards in its prefix mappings. So, it would be nice if there was a straight-forward way to modify the replacement configuration used by Git.
Since version control systems are implemented as plugins, would it make sense to support a similar configuration mechanism as for other types of plugins? Via this mechanism, other hard-coded settings (for instance the history depth) could be made configurable as well.

Closing comment (2024-04-09T11:08:06Z): @oheger-bosch, would you agree that this request can be considered as a duplicate of #6698?
Repository: oss-review-toolkit/ort

Issue #3909: Provide more information about ORT-specific LicenseRefs
Created: 2021-04-19T19:12:01Z
The declared license mapping contains a few mappings to licenses that start with "LicenseRef-ort-". For the user there is no way to find out more information about those licenses, for example the license text, without investigating the text that was mapped to these licenses and searching the Git log for the commits that introduced those mappings.
We should either stop using ORT-specific LicenseRefs or provide an easy way for users to get more information about those licenses.
Also see the discussion in this PR: #3898

Duplicate issue #3910: Provide license texts for ORT LicenseRefs
Created: 2021-04-19T19:35:26Z
ORT already emits its own LicenseRefs in several places. Most notably, we have LicenseRef-ort-* in declared-license-mapping.yml, e.g.

  
    
      ort/spdx-utils/src/main/resources/declared-license-mapping.yml
    
    
         Line 373
      in
      7ca9664
    
  
  
    

        
          
           "SOLACE CORPORATION LICENSE AGREEMENT": LicenseRef-ort-Solace-Software-EULA 
        
    
  


However, for the creation of disclosure documents / notices these mapping are of no value if not also the license text is provided. We need to improve the current logic for importing license texts from SPDX / ScanCode to also allow maintaining our own license texts for our own LicenseRefs.

Closing comment (2021-04-19T21:27:12Z): This is a duplicate of #3909.
Repository: owen-it/laravel-auditing

Issue #1008: Custom audits broken in v13.7.0
Created: 2025-02-18T04:01:41Z
PHP Version
8.3
Laravel Version
11
Package Version
13.7.0
Description
version v13.6.9 works v13.7.0 don't

Steps To Reproduce
dispatch a custom audit Event::dispatch(AuditCustom::class, [$article]);
Possible Solutions
No response

Duplicate issue #1009: Issue in Event::dispatch(AuditCustom::class, [$user]); after update package to 13.7
Created: 2025-02-19T15:10:05Z
PHP Version
8.2
Laravel Version
10.0
Package Version
13.7
Description
After I upgrade to version 13.7 for laravel 10
I have this error
 [2025-02-19 17:35:34] local.ERROR: OwenIt\Auditing\Listeners\RecordCustomAudit::handle(): Argument #1 ($event) must be of type OwenIt\Auditing\Events\AuditCustom, App\Models\User given, called in vendor/laravel/framework/src/Illuminate/Events/Dispatcher.php on line 478 {"exception":"[object] (TypeError(code: 0): OwenIt\\Auditing\\Listeners\\RecordCustomAudit::handle(): Argument #1 ($event) must be of type OwenIt\\Auditing\\Events\\AuditCustom, App\\Models\\User given, called in /home/forge/demo-backend.mjls.tech/vendor/laravel/framework/src/Illuminate/Events/Dispatcher.php on line 478 at vendor/owen-it/laravel-auditing/src/Listeners/RecordCustomAudit.php:10)
Steps To Reproduce
The normal behavior suddenly stopped working after the update.
It is supposed to audit the logged-in user during login, and it was functioning correctly before.
Possible Solutions
I have fixed it by updating the dispatch call from
Event::dispatch(AuditCustom::class, [$user]);
to
Event::dispatch(new AuditCustom($user));

Closing comment (2025-02-19T15:12:00Z): Did you try v13.7.1 or v13.7.0
Duplicate of #1008
#963 was a breaking change
Repository: owen-it/laravel-auditing

Issue #923: AuditingEventServiceProvider disables Laravel's Event Auto-Discovery
Created: 2024-04-22T16:35:27Z
Q
A




Bug?
yes


New Feature?
no


Framework
Laravel


Framework version
11.4.0


Package version
13.6.5


PHP version
8.3.6



Actual Behaviour
I've already filed an extensive bug report in the laravel/framework repository, which has been rejected. I am not yet 100% convinced that this not at least partly a framework problem.
Once the auditing package is installed, Laravel's event auto-discovery no longer works. This means that events and listeners from my application will not be detected. I (want to) rely on auto-discovery.
I am pretty sure this is caused by the AuditingEventServiceProvider inheriting from the framework's base EventServiceProvider.
I have found that the framework's EventServiceProvider is no longer registered once another service provider inheriting from that base class is registered. This is the case for your service provider. I am still trying to figure out how the framework works and registers those service providers.
As the auditing service provider is registered instead the framework's service provider, this check in shouldDiscoverEvents will return false.
Expected Behaviour
Using your package, Laravel's EventServiceProvider is still registered and event auto-discovery works as expected.
Steps to Reproduce

Fresh installation: https://laravel.com/docs/11.x/installation#sail-on-macos
Follow setup
./vendor/bin/sail art make:event TestEvent
./vendor/bin/sail art make:listener TestListener
Type hint the event (3) in the listener (4)
./vendor/bin/sail art event:list
./vendor/bin/sail composer require owen-it/laravel-auditing
./vendor/bin/sail art event:list
./vendor/bin/sail composer remove owen-it/laravel-auditing
./vendor/bin/sail art event:list

Check the output of (8) and (10) and you will see that at (8) the event and listener are discovered while at (10) they no longer are.
Please have a look at the code in the original bug report.
Possible Solutions
If this package would rely on Manual Registering Events, i.e. not inheriting and not using the $listen array anymore, but instead using the facade in any of the boot functions, I think the problem could be solved.
On the other hand, I still think this is a bug in the framework.

Duplicate issue #926: Laravel's auto event discovery not working
Created: 2024-04-30T09:36:10Z
Q
A




Bug?
no


New Feature?
no


Framework
Laravel


Framework version
11.5


Package version: 13.6



PHP version
8.3



Actual Behaviour
By default, Laravel 11 will automatically find and register our event listeners by scanning our application's Listeners directory.  The event was working fine before installing the package. After installation, the package Laravel auto-event discovery is not working.  But manually registering events is working fine.
Expected Behavior
I want to use Laravel's auto-event discovery functionality after installing the package.

Closing comment (2024-04-30T13:44:39Z): Fixed on #916
Duplicate of #923
Repository: owen-it/laravel-auditing

Issue #297: Eloquent MongoDB object changes not auditing
Created: 2017-08-24T15:08:16Z
I am using it with MongoDB Driver and its not working when mongodb object has been changed. So its not working recursive only checking first level of array.

Duplicate issue #315: Bugs with mySql json type and cast attribute to collection
Created: 2017-09-24T20:55:05Z
Q
A




Bug?
yes


New Feature?
no


Framework
Laravel


Framework version
5.5.9


Package version
4.1.3


PHP version
7.0.1



Description:
There is mysql json field type phones.
There is model Bar:
use OwenIt\Auditing\Auditable;
use OwenIt\Auditing\Contracts\Auditable as AuditableContract;

class Bar extends Model implements AuditableContract
{
    use Auditable;

    protected $casts = ['phones' => 'collection'];
}
When i update phone field:
$phones = [111, 222];

Bar::update(compact('phones'));
old_values is {phones: ["111", "222"]} (with space between numbers).
new_values is {phones: ["111","222"]}  (without space between numbers).
And stored phone field value in mysql is ["111", "222"] (with space).
And If i save again and again (without change any numbers), i will store and store new audit...

Closing comment (2017-09-28T18:52:21Z): Somewhat related to #297 .
Repository: owen-it/laravel-auditing

Issue #947: Audited logs deleted on fresh install with threshold set to > 0
Created: 2024-06-10T08:47:38Z
PHP Version
8.3
Laravel Version
11.x
Package Version
13.6.7
Description
Hi there, firstly thanks for the great package!
I'm not sure if this is something I'm doing or what, but I've just installed a fresh copy, followed the instructions to the letter, and it was refusing to keep audit log entries when I'd tried saving in the following manners:

Via "save" buttons in Filament PHP
Via tinker ->save() method on a model instance (with console set to true in the config)

I'd stopped short of making a custom controller just to test this, as I had added the following to my model:
/**
 * The "booted" method of the model.
 */
protected static function booted(): void
{
    static::updated(function (Property $property) {
        dump('updated', $property);
    });
}
And that dump was coming through on the above save methods.
I'd also added an event listener for OwenIt\Auditing\Events\Auditing which was dumping out each time I tried the above save methods as well.
It wasn't until I'd set the threshold option back to 0 (from my preference of 100) that it started actually logging anything.
I've tested this with the threshold at various values and it seems that the prune method might have a bug in it as when the value is anything other than 0, the entire log for that model (and only that model instance, it seems) is removed on each audit event.
Steps To Reproduce

Install auditing tool
Configure as normal
Create at least one auditable model
Set threshold to anything other than 0
Trigger an update/create etc event

Possible Solutions
No response

Duplicate issue #950: Model's all logs are deleted after  v13.6.5 when Threshold is more 0
Created: 2024-06-26T12:16:14Z
PHP Version
8.1
Laravel Version
9.52.16
Package Version
13.6.7
Description
Default installation used.
On version 13.6.5 was working good, but after updating project to 13.6.7 logs stopped. Downgrade helped
Steps To Reproduce
Basic install.
Use 13.6.5 - all is good
Use 13.6.7 - no logs
Possible Solutions
No response

Closing comment (2024-06-26T13:52:45Z): If audit.threshold = 0, that delete should never be executed

  
    
      laravel-auditing/src/Drivers/Database.php
    
    
         Line 25
      in
      22682dd
    
  
  
    

        
          
           if (($threshold = $model->getAuditThreshold()) > 0) { 
        
    
  


unless you have the auditThreshold property on that model, on that case, this would be a duplicate of #947

  
    
      laravel-auditing/src/Auditable.php
    
    
        Lines 616 to 619
      in
      22682dd
    
  
  
    

        
          
           public function getAuditThreshold(): int 
        

        
          
           { 
        

        
          
               return $this->auditThreshold ?? Config::get('audit.threshold', 0); 
        

        
          
           }
Repository: owen-it/laravel-auditing

Issue #708: https://laravel-auditing.com/ is not accessible
Created: 2022-03-30T07:19:37Z
https://laravel-auditing.com/ is not accessible

Duplicate issue #737: https://laravel-auditing.com/ is down
Created: 2022-08-29T13:55:39Z
Q
A




Bug?
yes



Actual Behaviour
Laravel Auditing is down
Expected Behaviour
Laravel Auditing is running
Steps to Reproduce
Go to Laravel Auditing
Possible Solutions
Checkout heroku logs --tail

Closing comment (2022-09-19T22:14:22Z): Duplicate of #708
Repository: owen-it/laravel-auditing

Issue #885: Enabling queue causes Unable to JSON encode payload. Error (5)
Created: 2023-12-21T17:41:32Z
After updating to the latest version it seems that the queue is automatically enabled.
This caused all my auditable models to stop saving and return this error:
Unable to JSON encode payload. Error (5): Malformed UTF-8 characters, possibly incorrectly encoded {"userId":1,"exception":"[object] (Illuminate\\Queue\\InvalidPayloadException(code: 0): Unable to JSON encode payload. Error (5): Malformed UTF-8 characters, possibly incorrectly encoded at /app/vendor/laravel/framework/src/Illuminate/Queue/Queue.php:109)
Publishing the config and setting the queue to false solves the issue but it's not clear why this is happening.
laravel/framework v10.38.1
owen-it/laravel-auditing v13.6.3
Thanks Dan

Duplicate issue #895: Binary attribute casting no longer works in new versions (works flawlessly with v13.5.1)
Created: 2023-12-30T01:22:16Z
Q
A




Bug?
yes


New Feature?
no


Framework
Laravel


Framework version
10.28.0


Package version
13.6.3


PHP version
8.1.0



Actual Behaviour
Binary uuid started creating error "Json malformed (Errno: 5)" even with use of a custom attribute modifier to cast from bytes to string and string to bytes. It worked fine for months till I updated from v13.5.1 to v13.6.3. I downgraded to  v13.5.1 and it started working back fine as expected.
Expected Behaviour
After investigation, it looks like my custom BinaryUuid::class is no longer called and the object to be casted into json still contains binary information. With v13.5.1 I can confirm that it my attribute modifiers is called to cast binary data into string
Steps to Reproduce
Here is the class I used in my models that have binary uuid (Dyryndra/Laravel-efficient-uuid):
`class BinaryUuid implements AttributeEncoder
{
public static function encode($value)
{
    if (blank($value)) {
        return null;
    }
    return Uuid::fromBytes($value)->toString();
}

public static function decode($value)
{
    if (blank($value)) {
        return null;
    }
    return Uuid::fromString(strtolower($value))->getBytes();
}

}`
And then I do this in Models:
protected $attributeModifiers = [ "id" => BinaryUuid::class, "withhold_of" => BinaryUuid::class, "slavery" => BinaryUuid::class, "pin" => RightRedactor::class ]; 
Possible Solutions
If you have any ideas on how to solve the issue, add them here, otherwise you can omit this part.

Closing comment (2023-12-30T13:33:29Z): #884 (comment)
Seems like Duplicate of #885
Repository: owen-it/laravel-auditing

Issue #907: Implement support for Laravel 11.x.
Created: 2024-03-05T13:40:44Z
Q
A




Bug?
no


New Feature?
no


Framework
Laravel


Framework version
11.x


Package version
-


PHP version
8.2 / 8.3



Actual Behaviour
Currently, the project does not support Laravel version 11.x.
Expected Behaviour
We expect the project to support Laravel version 11.x.
Steps to Reproduce
None
Possible Solutions
Implement support for Laravel 11.x.

Duplicate issue #910: Laravel 11
Created: 2024-03-12T20:55:37Z
Q
A




Bug?
no


New Feature?
no


Framework
Laravel


Framework version
11


Package version
13.x.y


PHP version
8.3.3



Actual Behaviour
Problem installing package with Laravel 11
Steps to Reproduce
composer require owen-it/laravel-auditing 
Make sure to include code (affected models, configuration, ...).

In a nutshell, help us, help you.

Closing comment (2024-03-12T21:41:59Z): Duplicate of #907
Fixed on #905
Repository: owen-it/laravel-auditing

Issue #211: Configurable Audit Model
Created: 2017-03-16T20:00:26Z
There should be a way to declare a custom Audit model. Since it extends from the default Eloquent model, it is currently incompatible with MongoDB. Simply changing which Model it "use"s worked with no problems, but editing vendor files is generally not a good idea.

Duplicate issue #258: Mongodb
Created: 2017-06-29T08:53:25Z
Q
A




Bug?
yes


New Feature?
no


Framework
Laravel


Framework version
5.4.27


Package version
4.0.7


PHP version
7.1.6



Hello I have problem about usage with MongoDB and i fixed it with changing model of audit but it will be fix on new release.
I fixed mongodb usage error like that;
/src/Models/Audit.php
Find:
use Illuminate\Database\Eloquent\Model;
Replace:
use Jenssegers\Mongodb\Eloquent\Model;
Now its working well but if we change this in package file it will go after package update please add this feature in new release.

Closing comment (2017-06-29T09:24:15Z): Hi @bsormagec,
Yeah, I'm aware of this, since it was already reported in #211. While the fix seems trivial, it will increase the package setup complexity a little bit.
I don't want to do this change in the current version, so I'm planning this for version 5. I'm gonna mark this as closed, in favour of the older report.
Stay tuned!
Thanks.
Repository: owen-it/laravel-auditing

Issue #360: Audited Data appears to be encoded encoded in utf-16
Created: 2017-12-12T09:06:30Z
Q
A




Bug?
?


New Feature?
no


Framework
Laravel


Framework version
5.3.y


Package version
5.0


PHP version
7.1.4



Actual Behaviour
Audited data appears to be stored encoded in utf-16.
sample audit
{"criteria_id":2,"is_checked":true,"application_id":111,"value":"\u07a6\u0790\u078b\u07a6\u0790\u078b","id":127}
Expected Behaviour
{"criteria_id":2,"is_checked":true,"application_id":111,"value":"ަސދަސދ","id":127}

Duplicate issue #460: Models Casts and Json strings - stop the escaping!
Created: 2018-11-08T17:44:12Z
Q
A




Bug?
no


New Feature?
yes


Framework
Laravel


Framework version
5.7


PHP version
7.2



Actual Behaviour
Cast arrays in the model that store as Json strings are escaped when audit is stored.
Expected Behaviour
No escapes, it makes it hard to visibly see what changed.

Closing comment (2018-11-09T09:51:03Z): This seems to be a duplicate of #360. Please read the response I gave, since it explains the reason why this happens and why it's something we have no control over.
You could always try to override the asJson() method from your models and pass the appropriate flags, so that the data doesn't get escaped.
Something like the following could work:
protected function asJson($value)
{
    return json_encode($value, JSON_UNESCAPED_UNICODE);
}
Repository: pagekit/pagekit

Issue #505: Option to force friendly url's
Created: 2015-11-25T12:48:51Z
I have a hosting account with custom nginx with htaccess rewrite rules support. Pagekit doesn't detect this rare configuration. So what I proposing is simple switch in admin panel or maybe in config that forces Pagekit to use friendly url format.

Duplicate issue #765: index.php on NGINX
Created: 2016-10-25T09:33:16Z
Problem
Hello, I am using Pagekit 1.0.8 with NGINX. I followed the instructions to enable pretty urls on NGINX.
Now I can access a page using www.example.com/index.php/blog and www.example.com/blog . Both URLs are showing the blog page.
If I click "blog" in the menu this item is linked to www.example.com/index.php/blog .
Technical Details

Pagekit version: 1.0.8
Webserver: NGINX
Database: SQLite
PHP Version: 5.6.24

Closing comment (2017-01-30T13:09:13Z): Duplicate of #505.
Repository: pagekit/pagekit

Issue #889: I have moved my website from one server to another, everything went smooth except the Blog module.
Created: 2018-01-30T09:44:01Z

Duplicate issue #890: SQLSTATE[42000]: Syntax error or access violation: 1055 
Created: 2018-01-30T09:45:48Z
I have moved my website from one server to another.
Everything went smooth, except for the Blog module. When i enter the Blog module and try to edit my articles, the Blog is not accessible, it throws the following exception:
DriverException in AbstractMySQLDriver.php line 115:
An exception occurred while executing 'SELECT user_id, name, username FROM pk_blog_post INNER JOIN pk_system_user ON user_id = pk_system_user.id GROUP BY user_id, name':

SQLSTATE[42000]: Syntax error or access violation: 1055 Expression #3 of SELECT list is not in GROUP BY clause and contains nonaggregated column 'pmgpagekit.pk_system_user.username' which is not functionally dependent on columns in GROUP BY clause; this is incompatible with sql_mode=only_full_group_by

Closing comment (2018-01-30T09:46:43Z): Duplicate of #889
Repository: pagekit/pagekit

Issue #229: premium themes/extension
Created: 2014-08-31T14:19:27Z
Hi
can we sold premium themes and extension via your marketplace? setup a purchase link or similar? are you planinng add this?
thanks!!

Duplicate issue #244: [Question] Can we sell items in Pagekit Marketplace?
Created: 2014-09-13T10:14:40Z
Hi. Just one question with Marketplace.
Can we sell themes or extension in upcoming Marketplace? or just free ?

Closing comment (2014-09-13T11:51:43Z): duplicate of #229
Repository: pagekit/pagekit

Issue #682: Add option for JS aggregation/minifying
Created: 2016-06-19T21:16:58Z
More than 30 js files are being loaded (using Theme One that is). There should be an option to aggregate and/or minify those assets for performance reasons.

Duplicate issue #738: Async or Defer options do not work for dependencies 
Created: 2016-08-19T09:45:43Z
This:
<?php $view->script('theme', 'theme:js/theme.js', ['uikit-sticky',  'uikit-lightbox',  'uikit-parallax', 'uikit-slideshow', 'verticalDropdown'], ['defer', 'async']) ?>
Will load theme.js asynchronously. It would be nice to have an option to load the dependencies asynchronously.

Closing comment (2016-08-22T10:12:19Z): Duplicate #682 @MalteScharenberg
Repository: pagekit/pagekit

Issue #814: Store XSS in post title and context 
Created: 2017-04-05T06:46:13Z
Pagekit version: 1.0.11
Webserver: Apache
Database: MySQL
PHP Version: 7

Login user who has "Manage own posts" privilege can inject arbitrary web script or HTML via post editor, XSS vulnerability will be triggered by visiting /blog or /blog/{post_id}.
PoC

Duplicate issue #894: Stored XSS issue in Blog title 
Created: 2018-03-09T01:23:00Z
Problem
Hello, I found stored XSS security issue in the blog title.
I have no good idea where is the best to post this issue, so I will post it here.
When Authenticated attacker post crafted the blog post. Any kind of Javascript is executed on browsers of users who access to crafted blog post page.
Let me show how to reproduce it.

Acces to 「/admin/blog/post/edit」
set blog  title as following

stub-title<script>alert(0);</script>


Save the blog and publish it.
Back to Blog list page 「/Pagekit/admin/blog/post?page=0」
Access to the blog url 「/blog/1」　as following image



dialog appears and says as 「XSS」


Then you reproduce Stored XSS issue is in the blog title.
Consideration
When an attacker uses this security issue for an attack, he is required to be authorized. So this issue is not so serious. But if another security issue is discovered and this security issue might be getting serious.
Technical Details

Pagekit version: 1.0.13
Web server: Apache
Database: not related this issue
PHP Version: 5.6.31

Closing comment (2018-03-09T20:47:37Z): Dupe of #814
Repository: pagekit/pagekit

Issue #550:  [Feature Request] Enqueue scripts in footer.
Created: 2016-02-28T04:57:51Z
Re-creating old issue from pre-beta as it seems to still be applicable.

Right now it appears that all scripts in theme and extensions are enqueued in the head. Generally, it's better to include scripts in the footer when possible for performance reasons.
It would be helpful if @script had an option to print the script in the footer, rather than in the header, perhaps by having these print in a @section('footer') section in themes.

Duplicate issue #609: Asset pipeline
Created: 2016-04-20T19:34:33Z
Hey Guys,
first of all I want to say that your doing a great job with Pagekit! Keep up your good work.
I would like to know if there are any thoughts about enhancing the current state with handling assets like css or js. Currently everything will be written into the head section of the document. As the theme grows there will be plenty of scripts. Which result in many requests the user has to do in order to load the page.
What I would love to see is that everything will be automatically concatenated and minified. But at least some option to load scripts at the end of the document or further asynchronous loading of third party scripts like so: <script async src="/js/libs.js"></script>
Maybe just enhance the $view->script() function with a boolean parameter.

Closing comment (2016-04-21T08:11:38Z): Already implemented: 655bb84 :)
Duplicate of #550.
Repository: pagekit/pagekit

Issue #505: Option to force friendly url's
Created: 2015-11-25T12:48:51Z
I have a hosting account with custom nginx with htaccess rewrite rules support. Pagekit doesn't detect this rare configuration. So what I proposing is simple switch in admin panel or maybe in config that forces Pagekit to use friendly url format.

Duplicate issue #693: mod rewrite enabled, but navigation still links to /index.php/...
Created: 2016-07-06T08:56:39Z
Hey,
i purchased a webserver (and this one is only a webserver with no access to the cli) and installed pagekit on that server.
First links like http://myDomain.de/home didn't work, because i had to define this line in my .htaccess file: RewriteBase / After i did this, links like http://myDomain.de/home finally worked.
Problem
Now the problem is, that the navigation links are still pointing to http://myDomain.de/index.php/myPage
Technical Details

Pagekit version: 1.0.3
Webserver: Apache
Database: MySQL 5.5.49-0+deb7u1-log
PHP Version: 5.5.36

Closing comment (2016-07-06T13:45:43Z): You're right, there should be a better option than the dirty fix that is listed in the issue I linked. However, I think this is a duplicate of #505 which is still open. :)
Repository: pagekit/pagekit

Issue #787: Square brackets in code excerpt previews as a link in markdown
Created: 2017-01-03T00:49:55Z
Problem
Consider the following code excerpt within markdown when editing a blog post:

When previewing this post we see the following:

Expected Output
My expectation is that instead of seeing <link-preview ..., I should see:

Note: Screenshot taken from this gist
Technical Details

Pagekit version: 1.0.10

Duplicate issue #863: Post preview shows <post-preview> when I add brackets to my text
Created: 2017-08-25T09:05:24Z
Problem
Post preview shows <post-preview> when I add brackets in a <pre> tag.
So if I write
` ` `
'config' => [],
` ` `

in my text, the preview shows 'config' => <link-preview index="7"></link-preview>,
Escaping with backslash does not work.
In the frontend the text is shown correctly.
Technical Details

Pagekit version: 1.0.12
Webserver: Apache 2.4
Database: SQLite
PHP Version: 7.1.2

Closing comment (2017-09-07T13:26:17Z): Isn't this exactly the same as #787?
Repository: pagekit/pagekit

Issue #50: Invalid argument
Created: 2014-07-19T07:36:39Z
After installation the pagekit show me some errors, reading this post on google+ community : https://plus.google.com/105077122590712223916/posts/UzeuKjG7NVa
I reduced all the error whit debug = 0 in config.php.
But, there are other  error that I report below:
pagekit/extensions/system/src/Extension/Extension.php on line 144
pagekit/extensions/system/src/Theme/Theme.php on line 149
I can't see fronted pagekit and I can't enter in admin area.
How can solve it?

Duplicate issue #61: RuntimeException in NativeSessionStorage.php line 143
Created: 2014-07-21T21:20:01Z
Directly after installation of Pagekit, following error will be displayed:
RuntimeException in NativeSessionStorage.php line 143:
Failed to start the session because headers have already been sent by "/var/www/html/test/pagekit/extensions/system/src/Extension/Extension.php" at line 144.
Anybody the same?

Closing comment (2014-07-23T09:21:29Z): This is a duplicate of #50
Repository: pahen/madge

Issue #335: [Feat] Specify config path via CLI
Created: 2022-11-18T17:43:24Z
There is currently no way to provide config path or detectiveOptions via CLI. Its blocked by commander even though it would work out of the box with rc

Duplicate issue #273: How to provide config file like package.json to CLI?
Created: 2021-03-10T21:30:05Z
I'm sorry if it's a stupid question. I want to use madge as CLI tool and provide all the configuration inside package.json "madge" field. I see that CLI supports providing webpack-config and ts-config but there is no option to point it to rc config. How should I do that?

Closing comment (2023-01-30T06:00:44Z): @Dostoievsky It's actually a nice idea after I understand what you mean.
But then it's like a dup of

#335

right? I think we can keep this one closed since #335 is still open.
Repository: pahen/madge

Issue #181: See dependencies on a directory not just a module
Created: 2018-11-06T21:30:28Z
I would find it useful to be able to see the dependencies between modules in one directory and modules in another directory. The most obvious use case would be seeing how tightly coupled a directory is to a projects common directory. The --depends functionality seems to almost provide this, but I think it would be useful if it could accept a directory, or possibly a regex, to see dependencies to a set of modules. I'm happy to work on this but thought I would put it out there incase I'm missing some other way to do it.

Duplicate issue #202: Group by folder
Created: 2019-02-03T11:20:28Z
Can it group files by parent folder in generated image?

Closing comment (2019-02-03T17:33:07Z): Similar to #181 ?
I wrote a filter that does that:
#181 (comment)
Repository: pahen/madge

Issue #254: [Feat] generate subgraph of dependencies
Created: 2020-07-21T21:31:27Z
How can I generate a subgraph from a give file
Use case:
I'd like to know all "internal" files that depends on a give File

Package B subgraph would be, package A and babel (just change package for files in the example to make sense)

Duplicate issue #254: [Feat] generate subgraph of dependencies
Created: 2020-07-21T21:31:27Z
How can I generate a subgraph from a give file
Use case:
I'd like to know all "internal" files that depends on a give File

Package B subgraph would be, package A and babel (just change package for files in the example to make sense)

Closing comment (2024-11-15T16:53:45Z): @PabloLION

@sibelius Can you check if this is a dup of #254 ? Also I think the solution to #181 may help you as well.

You linked the current issue as a potential duplicate. I did a quick search and couldn't identify the issue you may have meant.
#181 seems orthogonal to this issue.
@sibelius
You can use the JS/TS interface to crawl the graph for your needs. Just call .obj() and assemble the subgraph as required.
Repository: pahen/madge

Issue #57: Unable to retrieve requirejs child recursive dependencies
Created: 2015-04-26T08:33:04Z
The analyse always stops at the first layer and consider my dependencies to have no deps, which is of course not the case.
using madge -f amd -R myconf.js -N -i out.png src

Duplicate issue #59: no transitive dependencies
Created: 2015-05-06T13:07:55Z
When I have a simple file with the dependency e.g. to react
require("react");

the madge only finds
{ index: [ '../node_modules/react/react' ] }

and does not recurse any further.
I must be missing something. I want to get all transitive dependencies, too.

Closing comment (2015-07-27T10:09:35Z): +1
This looks like a duplicate of #57, btw.
Repository: pahen/madge

Issue #328: how to deal if the require path have variable
Created: 2022-10-28T05:16:17Z
like this:  const producer = require(`${config.path.mq}producer`);

Duplicate issue #344: Is it possible to exclude dynamically imported modules?
Created: 2023-01-27T00:03:33Z
I need to exclude dynamically imported modules from inspection, e.g. import("../xxx")

Closing comment (2023-01-28T13:09:39Z): @1226085293 is this a dup of #328?
Repository: pahen/madge

Issue #253: Yarn workspace or TSC path not picked up
Created: 2020-07-10T23:40:31Z
First off, very cool library. Codebase only 7 files!
I've tried the includeNpm: true option but isn't picking up yarn workspace packages. I've used both the yarn workspace, & the tsconfig compilerOptions.paths & references options.
Are these currently supported? I searched through the issues/docs and found no mention of yarn workspaces.
UPDATE:
Before I was running madge from a workspace package, not root. After running from root, the link to dist folder's .d.ts file was found.
This is the actual symlink, but would be good to pick up the src file instead.

I'm guessing it could use the sourcemap to do some conversion?

Duplicate issue #290: Yarn workspaces
Created: 2021-07-28T12:02:58Z
I have a yarn workspaces, with 100 packages dependent on each other (using @my-company/package-name syntax).
Can this tool help me find circular dependencies? It doesn't seem to pick up my internal packages...

Closing comment (2021-07-29T09:28:52Z): Duplicate of #253. Sorry, no support for Yarn workspaces.
Repository: pahen/madge

Issue #344: Is it possible to exclude dynamically imported modules?
Created: 2023-01-27T00:03:33Z
I need to exclude dynamically imported modules from inspection, e.g. import("../xxx")

Duplicate issue #328: how to deal if the require path have variable
Created: 2022-10-28T05:16:17Z
like this:  const producer = require(`${config.path.mq}producer`);

Closing comment (2023-01-28T13:10:55Z): Similar to #344 but more dynamic. Closing #344.
Repository: pahen/madge

Issue #158: support for module-alias
Created: 2018-04-16T08:50:00Z
Hello! is it possible add support for module module-alias ??
if I use this module, the svg image shows everything on the same level

Duplicate issue #182: package.json name paths not included
Created: 2018-11-14T08:58:02Z
Paths using the name of my root directory package.json aren't included in dependency calculations
package.json:
{
  "name": "myproject",
  "version": "0.0.1",
...
}

Upon calling
madge --orphans --basedir ./ ./ or
madge --orphans ./
it lists a file as an orphan: src/services/Logger.js
This file isn't an orphan, however its dependant is using the package name in the import:
import Logger from 'myproject/src/services/Logger'
.madgerc:
{
  "detectiveOptions": {
    "es6.mixedImports": "true"
  },
  "includeNpm": "true",
}

Closing comment (2023-01-29T06:21:27Z): If this bug do exist, it's similar to #158 . I reckon we should solve them in a same PR.
Repository: pahen/madge

Issue #135: Add an option to color the starting node differently
Created: 2017-10-18T00:15:43Z
It would be helpful in SFDP layout mode, since the starting node might get moved around...

Duplicate issue #313: [Proposal] new color for files where nobody depends on (e.g. index.js)
Created: 2022-02-04T10:48:35Z
Currently there is 3 colors:
Blue has dependencies, green has no dependencies, and red has circular dependencies.
It would be great to add a 4th one for "start" file like index.ts for example. Usually it should have only one such file, but there is case where there is more than one and it currently difficult to see such files

Closing comment (2024-11-15T17:00:47Z): Duplicate of #135