Allright, thanx for your response ;-) We will look wat suits our project best.
Looking at the code i think using multiple threads is possible, but connecting a job to a specific thread is not.
Well, my idea to use threads to restrict a specific job to one server, and run all others on the other server will not work. It also looks like the "Run in thread" does not really work. The "--options=thread=2" can not be added to the default cron. And the cron-run command that can use the parameter, only runs if you specify a specific job. Then I thought to run the one specific job with the setting on one server, and the regular cron on the other server... but than the job for server 2 is still also executed on server 1 in the regular cron. So for the load balancing purpose this is not very useful. To me it looks like the setting "Run in thread" does not really work at all.
But it's also very possible that I am misinterpreting the working of this function. There is not really a lot of documentation to go on.
Added patch for both config forms. In the plugin I did not add the dependency injection, as the file is full of dependency injection ;-).
@smustgrave: they are added for the issues documented in #17 📌 Typo: There was a problem creating field :@message Needs review
I normally just use the 2.x branch as development branch, and release a tag...
The test runs, but fails. ;-) I will have a look at it.
Hi @idebr,
I added a 2.x-dev branch. Is that what you mean?
Rerolled the patch for the latest 11.x branch, but the test have been significantly changes. So the tests are removed in this patch. They need to be rewritten, but unfortunately I do not have the time to do this right now.
Added simple change record. Also added setting to ignore things that you don't want in the change log.
joshahubbers → created an issue.
Nice! Better. ;-)
We had this error in our ddev environment. Ik can be solved by putting the solr configuration you download from drupal into the folder .ddev/solr/configsets/NAME_OF_THE_COLLECTION/conf/
Then restart ddev. Now de collection is automatically created and in Drupal we have no errors.
Allright, new try in a clean branch. MR against 11.x. Hopefully this is ok. Sorry for the waste for such a small fix ;-)
joshahubbers → changed the visibility of the branch 3534107-typo-there-was to hidden.
Hi PTMkenny, Sorry for my late response. I was on vacation. Thanx for committing it and making it a setting. Nice!
I did however add a commit to credit your contribution. Thank you for your time.
Sorry for the delay. I have been messing around a bit. Your suggestion works well for the single field. But while testing I noticed that the validation of the multiple field never has worked. Auch!
So I altered the code, to check for 0, and also make all validations work. I also adjusted the tests to get them to work.
joshahubbers → made their first commit to this issue’s fork.
Sorry, have been messing with the merge request. I think it is allright now?
Small fix in PR.
joshahubbers → created an issue.
Changed strategy to precacheAndRoute.
Forgot the interdiff.
New version. I removed the collection of assets to cache. Restored that part.
Also fixed some pipeline-things. Only composer next minor fails. Don't know why exactly.
I added the patch to enable sound by default. It follows the device setting of course, so when sounds are muted a buzz is played, or nothing at all, depending on the user phone preference.
joshahubbers → created an issue.
I think there is no real way to remove the tooltip. Just select the text around it and replace it with normal text... ;-)
Created a mr.
Is it possible to change the default branch to the latest branch? So 3.0.x? That would be nice ;-)
joshahubbers → created an issue.
Offline caching was not working properly. New try.
joshahubbers → created an issue.
joshahubbers → created an issue.
Merged.
* make entity fieldable
* link to edit entity is under structure > content types
joshahubbers → created an issue.
Good to know. Thank you very much!
Well, I was struggling with caching too, and stumbled upon this issue. Only this issue is far behind the current version of the module. I did some fiddling around, but did not get a proper way to merge this code into the current version. So I created a very basic implementation of the current workbox script. It is lacking nuance, and is rather crude. But I think it is working for now. Maybe a starting point to work on going forward.
Great! Thanx for sharing it. I will link it on my project page, and give it a try!
Here is the above patch for version 2.2.6. Since the change log shows de js files are not modified, I just repatched the js files.
I also tried to add a hook_ENTITY_TYPE_build_defaults_alter (hook_product_variation_build_defaults_alter) to add the user.role context. The strange thing is that the cache context is added, but I think that later in the process somewhare a call to getCacheContexts is done, and then the original cache context is restored. But I did not have the time to confirm my feeling.
Thanx @kaszarobert. Ik think you have a fair point here. Thinking about it, a hook like yours could be added to the module, only we don't use the module but it is integrated via google tag manager. So than we should incorporate it in a custom submodule for ourselves I think.
This is the patch. I know it is not to be comitted to the module this way, but for reference if someone needs it.
joshahubbers → created an issue.
This is the patch. I know it is not to be comitted to the module this way, but for reference if someone needs it.
joshahubbers → created an issue.
Another fix is to add the 'user.roles' cache context to the productVariation entity:
File: commerce/modules/product/src/Entity/ProductVariation.php
/**
* {@inheritdoc}
*/
public function getCacheContexts() {
return Cache::mergeContexts(parent::getCacheContexts(), ['store', 'user.roles']);
}I will have a look at the commerce issue queue to check if there is an issue for this.
We added 'user.roles' in our services.yml, like this:
required_cache_contexts: ['languages:language_interface', 'theme', 'user.permissions', 'user.roles']
But I think this should be added as a cache context explicitly to the display as a better fix.
We experience the same problem, but prices are cached across users. So if a user with a discount opens the page first, a user without the discount will also see the discounted price also.
Thanx Johan! Fixed and committed.
Great. Thank you for the fix and your effort.
Hi Timo,
I approved your suggestion. Let's wait untill the new po has been generated and check if it is complete then.
Thanks for your help!
This is a duplicate of 🐛 rh-node.js error: $action.next(...).textContent is not a function Fixed . That one has been committed.
joshahubbers → created an issue.
I am having schema issues also with the plugins...
joshahubbers → made their first commit to this issue’s fork.
I removed the module from this commit, as I think you mostly want to customize what exactly happens there, and not everything is generic enough.
I add the module as zip for reference.
Example module →
So what this patch does:
- Add hook to expand the service worker
What it does not do (see how to do it in the example module):
- Add new submodule for the notifications (see zip file for an example)
- The firebase service worker has to come from a specific url: /firebase-messaging-sw.js. The url is altered with a route to serve the service worker from this location.
- When a user accepts the push messages, the token is saved to the database.
Yes, great. Now only test-coverage is missing. ;-)
Back to working on this... please mind this is work in progress. F.e. in the current patch we show the token of the browser in the frontend to allow us to easily send test messages. ;-) Just so you know the current status.
Sorry, I know I am a knit-wit... but "enabled" suggests the variable enables the entire functionality. But it enables/disables the protection of 404, 403 and front pages. Maybe rename that to "protect_404_403_front"? Than it is obvious what the setting does...
joshahubbers → created an issue.
joshahubbers → created an issue.
🐛 Upload app icon results in error Active is included in this patch
Hi @divyansh.gupta,
you said in #7:
So as per your suggestions i will work and create a option to enable/disable this feature in settings form.
I am missing that in this branch?
You can always open the "Diff"-link in the mr above and save that as a .patch or .diff. This file you can use in composer. But for your convenience I attach it here.
I think this should be closed in favour of the other ticket. The idea was that you could use your own local scripts if you would like that (I think ;-) ).