- Edit
- Flag
Bug / Feature Request
| Also known as |
- Software Ticket
If you've run into an issue that you think is a bug, please have a look at our known issues list below. If you have a new item (feature or bug) to post, add a new one with the action link to the left. You can also review the roadmap of future...
more
If you've run into an issue that you think is a bug, please have a look at our known issues list below. If you have a new item (feature or bug) to post, add a new one with the action link to the left. You can also review the roadmap of future features or list of closed items.
Note: we recommend Mozilla Firefox 2.0+ or IE 6.0+ for your best Alpha experience (For performance reasons, we also recommend you disable Firebug if it is installed)less
-
Results: 1 – 30 of 103
| close name | close image | close type | close priority | close status | close article |
|---|---|---|---|---|---|
| Duplicate links for Album Contribution | Bug / Feature Request | Low | open - new |
I just discovered a couple of cases where the Album Contributions property on Musical Artist has duplicate links to the same album.
Bob Dylan
www.metaweb.com/metaweb/combinedView.html?id=/wikipedia/en_id/3345
David Rawlings
www.metaweb.com/metaweb/combinedView.html?id=/wikipedia/en_id/1202695&typeId;=/music/artist
|
|
| Topic | |||||
| WYSIWYG editor has issues with newlines | Bug / Feature Request | Medium |
For the first paragraph in a text box (like this one) hitting return at the end of the line inserts a return but keeps the cursor on the same line.Hitting return a second time will put the cursor on the next line, rather than two lines down. It's only when typing additional text that the cursor will move to the next line.
|
||
| Topic | |||||
| Main interfaces need consistent "working" indicator | Bug / Feature Request |
At least on my box (a laptop a couple of years old running Windows XP and Firefox 1.5.0.10), the various interfaces like view and filter often take a number of seconds to come up. It's very hard to tell when the app is actually done working, so I alternate between waiting for it when it's already done and going to click on something and having it move.I'd like to see a consistent "working" indicator. The two I'm used to from normal browsing are the browser "waiting" animation and the pointer...
|
|||
| Topic | |||||
| Query editor too tall | Bug / Feature Request | Low | open - new |
The query editor is too tall to fit without scrolling even when maximized on my 1400x1050 screen using normal browser settings. It should at least fit on a 1280x1024 screen, and it would be great if the layout were flexible enough to accommodate a variety of window sizes.
|
|
| Topic | |||||
| Query editor should not resort query by key | Bug / Feature Request | Low | open - new |
Although key order doesn't make any difference to the API, you can see in the docs that changing key order can make the query clearer. Unfortunately, the query editor automatically sorts the keys in alphabetical order on submission. In addition to making the query more confusing to a novice, it also is disconcerting to have things jump around.
|
|
| Topic | |||||
| Want to monitor my discussions | Bug / Feature Request | Medium | open - assigned |
So that I can particpate actively in discussions, I'd like to be able to monitor three sorts of discussions:Ones I have commented in,Ones I on topics I have created or contributed to (like this one), andOnes that are interesting to me.I think the first two should be automatic and available off the home page or my profile. The third should be something I can select manually. On-Freebase monitoring is plenty to start.
|
|
| Topic | |||||
| Type editor should not offer forbidden options | Bug / Feature Request |
For types where I have no rights, the type editor still offers me the option to change things. Only when I try to change them will it tell me that I'm not allowed. This includes just trying to look at the options for enumerated types.Rather than offering me an option and then refusing to follow through, it should disable controls I'm not allowed to fiddle with. That way the interface will better reflect the underlying reality.
|
|||
| Topic | |||||
| Starting a document should be double-clickable | Bug / Feature Request |
To enter this text, I have to click, "You can add it." For other data
entry, I double-click on the grey italic text. This is inconsistent,
and I often end up double-clicking on "There is no user-contributed description for [topicname]". It'd be better if double-clicking worked for filling in the document field just like it does for other fields.
|
|||
| Topic | |||||
| Filter titlebar should mention location | Bug / Feature Request |
When filtering on a type (as when viewing the ticket list), the page titlebar should mention the locaiton in the same way the page header does. That makes it easier to tell which window or tab is which.
|
|||
| Topic | |||||
| Viewing an invalid user gives blank page | Bug / Feature Request | Low | open - new |
Viewing an invalid user gets a page that is blank except for a couple of images. For example:http://www.freebase.com/view/user?id=/user/sadfIt's not a big deal, as people shouldn't be hand-editing URLs, but it would be better if it there were some sort of "user not found" message.
|
|
| Topic | |||||
| Want page like Wikipedia's "Recent Changes" and "My Watchlist" | Bug / Feature Request |
A problem with any large collaborative effort is knowing what is going on. Wikipedia has two features that help with that. I think both of these features are important for Freebase to implement
early on, as they help draw people into involvement and then help keep
them involved.
The first is Recent Changes. It is a link available in the
sidebar of pretty much every page on the site. It shows the last 50
changes to Wikipedia, and includes:Article title Change timestamp Who made the change...
|
|||
| Topic | |||||
| WYSIWYG editor generates non-working links if http omitted from URL | Bug / Feature Request | Medium |
Desired outcome: an external http URL link. Actual outcome: an internal freebase URL link because of the "other" type Example: Good URL Example: Bad URL Additional information: to edit the bad URL, the editor must delete the text, unless he knows about the apparently undocumented Microsoft-like Ctrl-K shortcut. Actions requested:
|
||
| Topic | |||||
| Would like an easy way to see what type a property is from | Bug / Feature Request |
For a topic with multiple types, it's hard to figure out how the topic gets a particular property. It'd be great if the pulldown next to the property said what type it was from, and had an option to view the type definition directly.
|
|||
| Topic | |||||
| Query editor: saved queries and multiple query tabs | Bug / Feature Request |
In using the query editor, it would be great to have multiple tabs so that I can have different queries going at the same time. I want this both when I'm trying to a mental stack push and when I want to compare the results from two different queries.I'd also like to be able to have a personal set of saved queries.
|
|||
| Topic | |||||
| Incorrect error message in query editor | Bug / Feature Request |
If I put in a query where I've forgotten a comma, the query editor says:"SyntaxError: missing } after property list"Since the query actually has the right number of braces, a better message would be, "comma missing between properties". It would be even better if it could say where in the query the comma were missing.
|
|||
| Topic | |||||
| Query editor should accept queries from documentation | Bug / Feature Request |
In the documentation, most of the examples are of the form:[{
"id|=":["/type/type", "/type/property", "/type/key"],
"id":null,
"/type/type/properties":[]
}]But to make them work in the query editor, you need to enter:{ "query":[{ "/type/type/properties":[], "id":null, "id|=":["/type/type","/type/property","/type/key"] }]}The query edtor should either accept or fix up queries pasted in from the documentation.
|
|||
| Topic | |||||
| Query editor doesn't propertly handle query errors | Bug / Feature Request |
If running a query causes some sort of internal error, the page title changes to indicate an error, but the interface otherwise looks like it is stuck running a query.Sorry I can't give more info on this, but it happened to me when the sandbox went down briefly; by the time I went to file the ticket, the sandbox was back up.
|
|||
| Topic | |||||
| png thumbnails fail to generate | Bug / Feature Request | open - new |
thumbnails for png image uploads seem to fail to generate. See Watt steam engine for example. I see only a little white rectangle, but the full image displays fine.
|
||
| Topic | |||||
| Various issues with history | Bug / Feature Request | Medium |
I see a few issues with the topic history screen:History doesn't show document changesIf you take a look at the history for this page, you should see several changes to this text, as I've edited in in a few passes, with changes to the other fields in between. However, it only shows the initial text creation in the history.Linked item on document history is mysteriousOn the line showing the creation of this text, there's a link to what I presume is the document itself. In this case, this link:...
|
||
| Topic | |||||
| App-friendly authentication API | Bug / Feature Request | Medium | open - new |
In thinking about applications I'd like to build, I'd don't want to make people authenticate through my app. There's no reason for people to trust me with their pasword, and I'd rather not even know it, so that I can't possibly leak it.In the web links, I've included a couple of links to auth APIs that work more in the style I'd like to see.
|
|
| Topic | |||||
| Type "user profile" contains properties also included in "person" that should be identical but are independent. | Bug / Feature Request | Low | open - new |
The type "user profile" contains properties, such as birthday, which are also in "person", a property of "user profile". These properties are independent and can be different. They should be synchronized or removed from "user profile".
|
|
| Topic | |||||
| Easy way to filter on non-empty value? | Bug / Feature Request | open - new |
There's probably some way to do it with wildcard syntax, but there have already been a few times when I wanted to filter a list of topics in a given type by ones that had a given field set to a non-empty value. (My motivation for this was to remove all values for that property from existing topics, so that I could change the expected type of that property.)This appears to be a bug. You should be able to just use * as a wildcard, and this works for non-autocompleting properties (e.g...
|
||
| Topic | |||||
| Link dialog in description editor should be prefilled with selected text | Bug / Feature Request | Low | open - new |
When editing a description, to add a link I highlight text and click the "link" icon. Usually I end up having to immediately retype the text I just selected into the metaweb link field. Seems like it might make sense to pre-fill that field with the selected text to save time (or even run a search on the selected text, and present the metaweb "I'm feeling lucky" result as one of the radio button options).
|
|
| Topic | |||||
| Random failures during article updates | Bug / Feature Request | Medium |
When updating article properties, the Ajax update indicator sometimes gets stuck. Refreshing the page seems to be the only way to clear the condition. Sometimes the database update has actually completed, and the refresh shows the new information. Sometimes it hasn't. Trying exactly the same thing a few minutes later can sometimes succeed. I am testing from Massachusetts over a 20Mbit down /2 Mbit up FiOS connection. The browser is IE 7, the OS is Windows XP SP2.
|
||
| Topic | |||||
| Can't link to users in text editor, favorite topics | Bug / Feature Request | Low | open - new |
I'd like to be able to link to users as internal Metaweb links. But at least when I try it for my two accounts ("/user/william" and "/user/querybuilder_bot") the autocomplete can't find them, both in the text editor link tool and in the "favorite topics" autocomplete.
|
|
| Topic | |||||
| Registrant who mistypes email cannot complete registration | Bug / Feature Request | Medium | open - assigned |
Steps to reproduce Current user invites new use: newguy@example.com New user receives email, clicks on link New user registers, but mistypes email as newguy@exampel.com New user receives no emailNew user returns to site to log in, is told "you must follow the instructions in the account activation email"I couldn't find a way out of this. At minimum, they should be told who to contact if the email never arrived.
|
|
| Topic | |||||
| RSS feeds for Discuss pages | Bug / Feature Request | Medium | open - assigned |
It would be great to have an RSS feed set up for each of the Discuss pages.
|
|
| Topic | |||||
| Unexpected list of irrelevant types |
|
Bug / Feature Request |
When I gave focus to "Where I grew up" and typed in the first few letters of the location, the system offered me the choices illustrated in the accompanying screenshot, the types include "Book", "Person", "Musical Artist" "Person, Deceased Person", none of which are pertinent to asserting a geographic location.
I haven't got round to reading the API yet but if it's possible to restrict the search domain to a specific type range then that restriction should be added to that particular form...
|
||
| Topic | |||||
| Terminological confusion |
|
Bug / Feature Request |
The image addition facility refers to the location of the image to be uploaded, e.g. "Freebase image", "Select an image on your drive. JPG, GIF, PNG formats preferred.", etc.
Once uploaded, the edit options include: "Image location". This is confusing when the upload dialogue has already created a contextualised meaning of the term "location" as the location of the image file. The same term is now used to refer to the location of the subject of the image.
Once again, the proffered list of...
|
||
| Topic | |||||
| MJT example fails with IE7, needs Allow Cookies set | Bug / Feature Request |
IE7 is blocking Freebase.com cookies.Using IE7, the MJT example which accesses Freebase fails witherror: browser could not contact the server you may need to sign in.Work-around:In IE7, Internet Options / Privacy / Sites / freebase.com = Always Allow cookies
|
|||
| Topic | |||||

