Feb 3, 2024 19:22
Exactly. Note how I haven’t accused you of anything, that’s all you. Anyway, this is completely pointless as you’re not up for listening, so I’ll remove myself from the conversation.
Feb 3, 2024 19:12
You see, that’s exactly the sort of response which is going to stop people wanting to help you. People take their free time to try to explain what you need to do, and you throw it back in their face and pretend that they’ve “disrespected” you. It’s a very strange thing to do, the only person it hurts is you. But hey go, this world takes all sorts I suppose.
Feb 3, 2024 18:49
It’s frustrating to try to provide answers to someone who isn’t going to understand them, that’s why I’m suggesting to go down the learning route first. Peoples’ generosity can only extend so far, and there’s at least a 50/50 chance that once you get over this hurdle, they’ll be another one, which right now you’ll also need someone to tutor you through start to finish - you might not find that kind of support available, hence the suggestion
Feb 3, 2024 18:07
I already addressed that. No, it shouldn’t
Feb 3, 2024 17:53
Go to Google, in your language, type in composer tutorials, in your language. Click.
Feb 3, 2024 17:46
Sorry to be the bearer of the news, but this is basic developer stuff, not dev-ops, and nowhere near expert level. You’ve made an assumption that composer will update a package to the next major version automatically. That assumption is wrong, and a very basic bit of composer knowledge. You won’t be able to ask here for every single nuanced composer message you don’t understand, that won’t be useful to everybody else, so doing that learning now is a really good idea, trust me. I’m trying to help
Feb 3, 2024 17:39
But now you do have a problem, so now’s a good time to learn how it works, no?
Feb 3, 2024 17:31
Or just change the major version constraint for drush to 12 and add the -W flag. Or do it the other way round and don’t run drush commands until you’re done. This is really a question of understanding what composer is and how it works, which is basically a prerequisite for Drupal development now. I’d strongly recommend taking a step back and doing some reading up on how to work with composer, or you’re going to end up with several of these questions every time you want to touch your codebase
 
Feb 14, 2023 13:05
That’s not something users here will be able to guess; it should be trivial to grep your codebase for it though. Unless it has some relevance to Drupal, and isn’t just an arbitrary PHP function, this isn’t the right place to ask about it
 
Nov 11, 2021 17:21
General opinion is that it's safe to truncate cachetags, yes, see drupal.stackexchange.com/questions/188382/…
Nov 11, 2021 17:21
If that's definitely the problem and you just want to hack it, add drupal_flush_all_caches() to a hook_update_N function and run through /update.php. Or truncate all the DB tables starting with cache_
Nov 11, 2021 17:21
Yep the metaphor was definitely tortured, but with respect I think you're using that to ignore the obvious point - if you want to develop, refusing to install the development tools really isn't a great idea; posting questions here isn't a sustainable alternative in my humble opinion. I say this for you, not for me or the site. In my experience both as a dev and mentoring devs, it's better to go through the pain of learning how to set up a robust dev environment than it is to try to work around it
Nov 11, 2021 17:21
To your last point - if your broken code is what broke the site, then just don't push that broken code to the remote, and you won't end up in the same position. So you won't need drush on the remote because you won't have this problem. If you do have the problem, then you know your initial assessment was wrong and the problem is elsewhere
Nov 11, 2021 17:21
I prefer not to install Drush in my current localhost Windows 10 environment It might be time to consider whether arbitrary personal preferences outweigh your need to get stuff done. If you want to develop, install the development tools. Would you try to fix a car but refuse to use a wrench? :)
Nov 11, 2021 17:21
But for the specific error, you are indeed either using the wrong username/password for the database you're trying to connect to, or you're connecting to the wrong server. There aren't really any alternatives, unless you have a dodgy version of MySQL installed, which feels unlikely
 
Nov 19, 2018 07:57
And actually according to the OP @Eric it’s not that they want exact matches first, rather they want only exact matches. That’s probably the ambiguity that makes this difficult to address with anything practical
Nov 19, 2018 07:57
Does search api support that kind of union @Eric? Not something I’ve come across before (but then I’ve never looked for it)
Nov 19, 2018 07:57
Yes you could probably use javascript to hide results, but of course that would break paging somewhat
Nov 19, 2018 07:57
Your two requirements are mutually exclusive, there isn’t an answer to give you as far as I can tell. One of the two opposing requirements will simply have to change, unless I’ve missed something
Nov 19, 2018 07:57
At which point it’s redundant @Eric - In x = ‘term’ AND x LIKE ‘%term%’, removing x = ‘term’ will produce identical results. It’s just a partial search
Nov 19, 2018 07:57
I believe what you’re describing is a logical impossibility. You can’t tell the query to be both partial and exact at the same time.
Nov 19, 2018 07:57
Maybe if you remove search api and just use core search? Search api is quite advanced, I’m not sure you can dumb it down to exact word matches only
Nov 19, 2018 07:57
Why would “apples” not be relevant to a search for “apple”?
 
Oct 31, 2018 15:30
@MikeL5799 It would be wise to take Kevin's advice - no offence intended, but you're kind of all over the place here and most of your problem seems to be lack of knowledge about or confusion over basic PHP. We can't support a collaborative debug session here, that's not what Q+A is about, and unfortunately that's what this has become in the comments
 
Apr 16, 2018 13:51
It's a core one, there's Internal Page Cache and Internal Dynamic Page Cache, the latter is for authenticated users
Apr 16, 2018 13:51
Have you enabled the dynamic page cache module? Can make a large difference. Other than that profile/optimise the server config, there must be something not quite right. I have plenty of servers with lower specs than yours all happily serving admin pages in 1-2secs at most
 
Feb 16, 2017 20:08
It's pretty simple actually - can you get to /admin/people/permissions when logged in as the user in question? If yes, your code is correct, and the user you're requesting the page as in not the same one. If not, permissions are incorrect. Any other possibility requires non-core code to achieve, which we can't see. Not sure what else can be advised other than check that your method for confirming which user is making the request is accurate
Feb 16, 2017 20:08
Dunno, but of the probably thousands of hook_menu entries I've written in my life, not one of them has failed to work, using basically identical code. So you need to work out what's different from your site to a "normal" Drupal site
Feb 16, 2017 20:08
I suspect there's something about your setup/configuration that you're not sharing. It's impossible for $GLOBALS['user'] to be null inside a hook in Drupal unless there's rogue code breaking things
Feb 16, 2017 20:08
Then logically the user isn't one who has a role with "administer permissions" assigned. Take out the access arguments, clear the cache, and var_dump($_GLOBALS['user']); in the delivery callback function. Is it what you expect?
Feb 16, 2017 20:08
@Quantico EDIT THESE CHANGES INTO THE QUESTION, DON'T LEAVE THEM TO DIE IN THE COMMENTS. Please :)
Feb 16, 2017 20:08
But for some reason the 'administrator permission' is not working. Why would it? Your code is: 'access arguments' => array('administer permissions'),.
 
Jan 4, 2016 12:57
There are many modules that provide payment functionality. Try some, and if/when you have a specific question, that's when to ask here.
 

 Drupal Answers

Have the drop on
Jan 23, 2014 11:07
@Mołot That guy is creating a new anon account for every question/answer, so auto-ban won't work. He'll get bored eventually, just some pre-teen with too much time on their hands :)
Jan 10, 2014 18:43
@Letharion yep that was me...was just remarking how one can tell you've been in the UK for a bit ;) Are you in London? I'm just down in Brighton, we should meet up for a beer at the next Drupal event
Oct 30, 2013 00:02
@MPD Yeah either that or patch morkbench_moderation.module at line 927 to return the default state you're interested in. Funnily enough after all this time the comments for that function still says "@TODO: make this configurable."
Oct 29, 2013 21:54
@MPD I haven't used it for ages but yes, last time I did the string "draft" was hardcoded into one or two of the functions and removing that state broke everything
Oct 25, 2013 15:47
@Letharion It depends - can Facebook read this chat message? If so, then definitely, definitely not :P
Oct 25, 2013 15:04
Couldn't agree more. You're in England now, right? You should know we're all a bunch of cynical gits!
Oct 25, 2013 15:01
@Letharion I'd be very active too if I had that budget ;)
Oct 25, 2013 14:58
@Letharion @Bart There's some HHVM testing metrics (including for Symfony and Drupal specifically). Last week's release looks to have fixed up a lot, including providing redis support and fixing up ArrayObject/ArrayIterator (for D8), so it might not be too long before it's 'proper' usable
 
Jul 16, 2013 18:11
hi! yeah the comments were getting a bit crowded so we can move them over here
Jul 16, 2013 17:27
I think you might have to take a creative route around this, like making another view that's filtered explicitly by those tids, using the No Results Behavior area to embed that view, then change the contextual filter behavior to show the No Results area if the filter value isn't in the url. something like that anyway
Jul 16, 2013 17:25
Yeah I'm just playing with a basic view locally, same thing for me. The problem is the validator doesn't run when there's no argument in the URL, so it doesn't expand the comma/plus separated string. Might have to think of a different way around this one
Jul 16, 2013 17:25
Not a bug, no. Views isn't supposed to run the validator if it hasn't got an argument to validate, so it's behaving as designed. The validator is the only thing that allows you to use multiple term ids in the URL, so the conversion functionality simply isn't applied
Jul 16, 2013 17:25
Ah I see it...not a bug then :) Taxonomy filtered views normally allow you to use a comma separated list of values in the URL, so I would think you should return '63,64'; instead of the array. Haven't tried it, and there might be a setting in the contextual filter that needs to be enabled, but I think that should work eventually
Jul 16, 2013 17:25
It might be a + not a , thinking about it...
Jul 16, 2013 17:25
Awesome thanks. Is there any other processing done on that view (in custom code?) I can see a bit of PHP logic for the header but nothing related to the tid...
Jul 16, 2013 17:25
I'd go for hook_views_query_alter() personally. Depending on how you have this view set up you might actually have found a bug
Jul 16, 2013 17:25
Would you be so kind as to dump an export of your view somewhere online and let me have a link? If it is a bug I'll get it reported