-
Notifications
You must be signed in to change notification settings - Fork 20.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dead links for transaction call object #30214
Comments
This page was re-added as part of #30476. Thanks for reporting! |
@s1na Hi, I just looked at this again and the links are still broken (see reproduction in initial issue). When navigating via the menu on the left to "Interacting with geth" > "objects" it opens the page, but directly visiting the link forwards to /docs. So the page exists, but cannot be opened directly by clicking on a link. |
@Otto-AA Both links in the Eth namespace page are working for me. Can you share the exact link that is failing? |
This link does not work: https://geth.ethereum.org/docs/interacting-with-geth/rpc/objects (redirects to https://geth.ethereum.org/docs) It can be accessed via the menu navigation, but not when navigating to it with the url. $ curl https://geth.ethereum.org/docs/interacting-with-geth/rpc/objects
Redirecting to /docs |
@corwintines It is a strange issue. I could reproduce it. Can you please take a look? Basically clicking on the objects link from the navigation menu goes to the page correctly. However once there if I simply refresh the page it will go to "docs index" page. |
Describe the bug
In several places the link https://geth.ethereum.org/docs/interacting-with-geth/rpc/objects is used to link to the transaction call object, but it does not exist anymore.
I could not find correct destination, where it describes this information, so I can't make a PR myself to fix it.
To reproduce
Expected behavior
It should display information about the transaction call object.
Screenshots
No response
Desktop (please complete the following information)
No response
Smartphone (please complete the following information)
No response
Additional context
No response
Would you like to work on this issue?
The text was updated successfully, but these errors were encountered: