I have a block which displays all news belonging to terms of a category. However, sometimes, all news related to a term disappear while other terms' news are still visible. This disappear chunk appears on its own later. Is there a way I can fix it.
Both temporary or Permanent solutions are welcomed. Thanks in advance.
I have tried repairing tables, flushing cache but to no avail.
I checked the queries, they seem to be working fine.. I have used APC cache. Could that be a cause of old cached data. I tried flushing APC cache using apc_clear_cache() w and calling apc_clear_cache('user') but it hangs the server into indefinite loop.
Ok, I figured out the problem. The problem was that one of the news belonging to the set of news of a particular taxonomy was saved partially. Though there was an entry in the node table, other related data was missing.
On deleting this partial node manually from the database, the set of missing news articles reappeared.
Related
I've been working on my WordPress/WooCommerce site all morning. An now, all of a sudden, my Product Attributes have no values.
If I add a new product attribute value (via the product attribute page), the new value also does not show.
If I look in the database, all the values are there and the data looks perfectly fine, references and all.
I've done nothing to the taxonomy terms (except read them in a little theme code I'm writing).
I've even looked at my GIT and nothing has changed that has any impact on product attributes.
I am completely stumped as nothing is making sense. I'm starting to wonder if it's bad mojo, as another site of mine has also decided to magically stop working without reason.
Any ideas anyone? I'm a tick away from going nutts.
Okay, seems to have been a full HDD on the VM machine the wordpress was running on. Once I freed up some space it all started working.
I recently took over a site from someone else at a new company. Having never used Drupal before, updating things has been a bit cumbersome. There were some outstanding security updates that I applied(but I haven't updated the core yet). Anyway, after doing this, the calls to views_embeded_view have not been working. For example:
print views_embed_view('news_block');
Will break the links(by using the title, rather than alias for the link), or it will link correctly, but not follow the paging rules I have set(show 1 page, 6 items per page) instead it shows 10 items and has links for other pages.
I am not sure if the update has anything to do with it, but it seems likely. Would updating the core resolve this issue potentially?
The first argument of views_embed_view is view name, the second one is display id. If display_id is not provided, 'default' is used. Make sure that you are displaying the correct display. (i.e. default can be configured differently than some other display which you actually wish to see)
I'm using Sonata Admin as my admin backend for Symfony2, and I'm trying to load a page where my admin entity (transaction) has a many to one relationship to another entity (rate). The rate table is massive and grows very quickly, and there's not really anything I can do to change that.
When I hit the transaction list page, I get a memory sized exhausted error. Assuming this was a database problem (because the code works on my local environment), I cleared out the transaction table and the problem still happened. Once I cleared out the rates table, the page loaded immediately. I can only imagine this means that related entities are being eager-loaded on the admin pages.
Does anyone know how to force Sonata to lazy-load related entities? I've looked through the documentation and forums, and the only things I've seen either aren't relevant or say that Sonata does lazy-load automatically. Ideas?
I found the problem. Sonata may or may not lazy load, but that's not what the issue was; it was never even getting to the configureListFields() function. Instead, you don't want to add a field that has a lot of rows to your filter, it apparently loads all options at runtime.
I've got a strange senario/question for you.
I'm running drupal 6 with advanced forum (although my problem doesn't go away if I just use the forum module that comes with drupal)! Everything has been fine and so I've left it untouched (not open to the public) for about a month while I've been sorting out legal work...
I came back to it a few days ago only to find 'http://mysite.com/forum' (I'm using clean URL's) does not exist!
I've tried everything I can think of! Even silly things like 'http://mysite.com/forum s'. But it doesn't even appear to be there in Content Management > Content!
I can get to the individual posts and even the individual catergory/containers - I'm just missing the index page!
I've tried disabling and re enabling the advanced forum module, reseting it's settings and even clearing the site cache! Non of which made any difference! I was going to try typing the node in, but I wasn't sure what it was!...
Please help me as soon as possible!
Thanks in advance,
Andy
Latest
Okay, just to clarify exactly what's happening and what I've done so far after 'ax's' wonderful assitants:
Whats Happening is, I get Drupal's 404 Page Not Found message/page when trying to get to www.mysite.com/forum! The strange thing is though, by typing the URL of the individual sections/catergorys I can see them, and all the posts inside etc!
I have, been into sites/all/modules/advanced_forum/advanced_forum.module and look at the variables in the advanced_forum_page($tid=0) function.
First, I just created a post/topic in the forum var_dumping all the variables in the function! They all returned NULL.
But then in the function, I one by one var_dumped all the variables, after the line they were first used (in the function), I deleted the var_dump line for each variable after I refreshed the forum page, so there was only one var_dump in the function at once. The strange thing was nothing appeared on the page, even when I tried `drupal_set_message(print_r($variable));!
So, I don't know and I just need it fixing asap please! ... Thanks in Advance
you can try two solution:
Reinstall the module instead of deactivating and reactivating it (you will lose your current categorization, however it seems like your forum is empty right now).
Build a new installation to make some tests, enable the advanced forum module and take a look at the index page of the forum to see if it's replicable.
Take a look at the issue queue of the module too, maybe someone else had the same problem.
Just figured out what was going on, and therefore was able to sort my problem out myself!
It was the most stupid thing as well. For some reason, I had an empty folder called... you guessed, 'forum' in the root of my website and as soon as I deleted it, I saw my forum index for the first time in ages.
Obviously, Drupal was looking in the folder instead of using the module etc... (You Know...)
Anyway, thanks for your attempts to help me - much appreciated!
-- Andy
I have a fairly new drupal installation with a few hundred nodes. I moved it from the development server to the production server.
However, when I opened my homepage, it says page not found. After checking all my links, it seems that I can't get to any of my content. They exist in the node database, as well as the content type tables. I verified that all my URL aliases are also in place. In most cases, I can still see all the information from views I had created, but when clicking to see the full node view, I get the "Page not found".
I did trim all my cache tables before importing to reduce the size of the DB. Has anyone had these symptoms before? Perhaps there is a particular table, that when truncated, will lead to this problem?
**Update: Imported my revision table again, and presto - Although my content came back, I'm still having a sort of permissions problem. When an anonymous visitor comes to the site, they are told they don't have permission to see items like content type "Page", yet in user permissions, everything looks good (definitely good before migration) perhaps another deleted table?
Yes, node content information is in the revisions table, not the node table. You REALLY need the revisions table. I assume you can just remigrate again, this time without truncating revisions.
if table is broken, it shouldn't show "Page not found". It may show that sql error that table or column doesn't exists.
Try troubleshoot in http://drupal.org/node/201875 (you will see Page Not Found links in middle).
Also may be you use some redirecting in your node theming, check this.
p.s. In any case, node saving touch 2 tables: node and node_revisions