page not found with views
drumnjo - November 5, 2009 - 02:19
| Project: | Facebook-style Statuses (Microblog) |
| Version: | 6.x-2.0-rc2 |
| Component: | Miscellaneous |
| Category: | support request |
| Priority: | normal |
| Assigned: | drumnjo |
| Status: | closed |
Jump to:
Description
Seems like the blocks and and profile page (use profile content) statuses and everything works. But I can't get the pages to work in views. The default views for facebook style statuses seems to be ok (they're there) but when clicking on 'view page' I get "page not found" How do get these pages into my site for users to use? What am I missing?? I searched all around in support in forums.
Please help.
thanks
Joe
#1
I don't know, because you haven't told me any information at all except "it doesn't work."
As the message says on the "Create issue" page,
For example, you're reporting a problem with Views, so the obvious place to start would be explaining exactly which view(s) have this problem. By that I don't mean "The one that lists statuses" -- they all do that -- I mean the facebook_status view or the facebook_status_recent view. I need to know if this is an upgrade or a new install, which version of Views you're using, whether you've edited the default Views at all, what URL you arrive at when you click the link that gives you a 404, what the permissions are of the user(s) who get the 404, etc. Give me as much information as you possibly can, even if you think it's irrelevant.
#2
Ok sorry, I've been trouble shooting. It appears now that a single conversation link works within the 'Statuses'- Latest Updates Status, BUT the 'statuses/conversations' (plural) path in 'facebook_status_cross_post' does NOT contain that conversation?
all fresh installs and latest versions of drupal, views, facebook-style etc...
thanks,
Joe
#3
If you take a look at the "edit" page for the conversation view, you'll see that it requires arguments to work. The "statuses/conversations" page itself doesn't exist -- it couldn't possibly have the information required to know which conversation to show.
Anyway, that view just provides the backend for the
statuses/conversationpage. If you insist, you could get rid of the Page variant of the view, but I don't recommend it since it doesn't affect anything.By the way, see this page for the best way to get help in the future; this was in the documentation.
#4
Automatically closed -- issue fixed for 2 weeks with no activity.