Here's a 3.x version of the patch using the file_managed table instead.
minoroffense → made their first commit to this issue’s fork.
I'd rather have the code adapt to help being available or not.
I created an MR for review that does that.
Updated patch to fix some lint issues. I'll give this a test to see if it works.
Thanks for the work. I finish it up and set the attribution in the commit for everyone.
minoroffense → created an issue.
I feel as though big coding standards changes like this should follow a core release or major versioning release of coder or something. We have versioning for core APIs why not versions of the coding spec.
We have dozens of individual modules to go and update now and every CI build is broken (including client releases where this spec has nothing to do with what they're trying to ship). Especially for what is arguably a cosmetic change to the spec.
Sure running the beautifier to autofix is great and all but it takes time to do that, time to explain to clients why everything is broken all of a sudden and more time to create follow up releases etc...
Here's a patch that uses the accept headers as decriebed in #25
Could be worked into the main issue of having a default format or on its own to leverage http headers to set the request format instead of that argument.
I tested it with our local sites and it appears to work. I'm using the latest xhprof dev module and the xhgui php profiler module. Running with PHP 8.2
I enabled the module as usual and then configured it.
I've attached the settings we use. Note the URL for the XHGui instance needs to be configured. We use a docker instance and it's docker network name is "xhgui" so we set the url to "http://xhgui"
You can see the nginx config we use for the xhgui instance: https://gitlab.com/dropfort/dropfort_build/-/tree/6.x/assets/development...
And this is the docker-compose file which brings it up. Maybe one of those may help with figuring out why it's not working.
https://gitlab.com/dropfort/dropfort_build/-/blob/6.x/assets/development...
And this is how we install xhprof into the container: https://gitlab.com/dropfort/dropfort_build/-/blob/6.x/assets/development...
I’m working on a 10.3 site today and I’ll figure out what’s up with xhgui.
We setup a view that outputs values into a table for time spent entries. The data element describes the value as seconds and the we use that to generate charts and other things.
Views strips the data element without the patch. We can’t use the raw number since we want to show the value in different formats. The display value is human friendly but the data element lets us bring along machine friendly info.
https://developer.mozilla.org/en-US/docs/Web/HTML/Element/data
minorOffense → created an issue.
This change does break the acquia_search module. Their setEventDispatcher needs to update to match. I'll reference that issue once I create it.
minorOffense → created an issue.
No worries. Glad it got in. And thanks for the attribution.
amateescu → credited minorOffense → .
We have a pair of clients now where it just stops working. You can see the tracking code for a few requests then it’s gone. There’s something wrong. At a certain point there’s just no js added at all. No settings nothing.
Going to test a downgrade and see if that helps. And then compare versions to see what changed.
minorOffense → created an issue.
minorOffense → created an issue.
Here's what the field looks like in Views.
Likely going to need tests but figure get some eyes on it now in case something big needs changing.
I was contemplating adding checks that the langcodes were valid but I'd have to do that on render since it supports tokens and I didn't want to slow stuff down. Figure drupal will just fallback to default if the langcode is bad.
minorOffense → changed the visibility of the branch 11.x to hidden.
minorOffense → created an issue.
minorOffense → created an issue.
Here's an updated patch for the current release.
And I now realize this is fixed in 5.4.x+ :-/
Nm, sorry for the noise.
minorOffense → created an issue.
Here's a first attempt at this. Adds tokenize process, overrides the usesTokens method from the parent plugin and changes views.theme.inc to use the newly created getCaption() method.
minorOffense → created an issue.
minorOffense → made their first commit to this issue’s fork.
minorOffense → created an issue.
Yes I was actually thinking that. I'm also on my way to VueConf in Toronto later this week. I was gonna roll a stable before going. Hoping to learn a few things to add into the module. Or add some related modules for some common UI elements (like a date picker or something).
Well you don’t need the files folder to store runs if you’re using this module. It would ship it into xhgui.
Also do you have the xhprof php plugin installed and enabled? php -m on the command line should show it if so. Or the output of phpinfo()
minorOffense → made their first commit to this issue’s fork.
minorOffense → created an issue.
minorOffense → created an issue.
See 3.x
3.x branch and alpha are avaialble.
Going to mark this as fixed since the 3.x branch has an alpha. Feel free to reopen if you still have issues.
Please use the 3.x branch instead.
I created a 3.x branch for the D10 support and dropping D8. I haven't tested it yet but I'm working on a site that uses Flexslider that's being upgraded. Once I know it works I'll put a release in.
minorOffense → created an issue.
minorOffense → made their first commit to this issue’s fork.
This is required by a client we share for their D10 upgrade. Can you please review.
Before merging any D10 changes I want to drop support for D8 and remove some references to jquery easing (they can't work in D9+).
I created an MR into the branch Rishi created.
I don't have an environment to test it in at the moment.
minorOffense → made their first commit to this issue’s fork.
Thanks but the docs were outdated so I ended up just rewriting them.
Closing an unnecessary since we'll deprecate the D7 version shortly.
Closing an unnecessary since we'll deprecate the D7 version shortly.
Closing an unnecessary since we'll deprecate the D7 version shortly.
Closing an unnecessary since we'll deprecate the D7 version shortly.
No longer required. drush cget or vget can get the data we need.
Closing an unnecessary since we'll deprecate the D7 version shortly.
Closing an unnecessary since we'll deprecate the D7 version shortly.
This is already present in the D9+ version.
Closing an unnecessary since we'll deprecate the D7 version shortly.
Here's a patch in case.
The committed changes here missed the core key in the info file. It needs updating.