[
https://issues.apache.org/jira/browse/LUCENE-8987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17040515#comment-17040515
]
Uwe Schindler commented on LUCENE-8987:
---------------------------------------
I found 2 issues (only visible in dev console) on the website:
(1) I get on every page a error message (Chrome):
{noformat}
Uncaught TypeError: Cannot read property 'defaultValueActsAsHint' of null
at HTMLDocument.<anonymous> (search.js?v=dc722375:20)
at HTMLDocument.wrapper (prototype.js?v=dc722375:3966)
at fire (prototype.js?v=dc722375:4071)
at HTMLDocument._methodized [as fire] (prototype.js?v=dc722375:256)
at fireContentLoadedEvent (prototype.js?v=dc722375:4105)
at wrapper (prototype.js?v=dc722375:3966)
{noformat}
It looks like the change to Pelican changed the ID of search forms. No idea why
that returns NULL. My knowledge of prototype.js equals null (I am the jQuery
guy). So I have no idea what the code in search.js does. Do we need it at all?
It seems to work without it.
(2) The is an image referenced:
https://lucene.apache.org/theme/images/lucene/home-wrapper.png which returns
404. Its indeed not in the folder. It's referenced from the Lucene webpages
core.css file:
{noformat}
Request URL: https://lucene.apache.org/theme/images/lucene/home-wrapper.png
Request Method: GET
Status Code: 404 Not Found
Remote Address: [2a01:4f9:2a:185f::2]:443
{noformat}
That's the CSS:
{code:css}
/*HOME*/
body#home #wrap {
position: relative;
background: #fff url(/theme/images/lucene/home-wrapper.png) top center
no-repeat;
width: 945px;
margin: 0 auto;
text-align: left;
}
{code}
I see no visual problems, maybe we should just remove the background.
> Move Lucene web site from svn to git
> ------------------------------------
>
> Key: LUCENE-8987
> URL: https://issues.apache.org/jira/browse/LUCENE-8987
> Project: Lucene - Core
> Issue Type: Task
> Components: general/website
> Reporter: Jan Høydahl
> Assignee: Jan Høydahl
> Priority: Major
> Attachments: lucene-site-repo.png
>
>
> INFRA just enabled [a new way of configuring website
> build|https://s.apache.org/asfyaml] from a git branch, [see dev list
> email|https://lists.apache.org/thread.html/b6f7e40bece5e83e27072ecc634a7815980c90240bc0a2ccb417f1fd@%3Cdev.lucene.apache.org%3E].
> It allows for automatic builds of both staging and production site, much
> like the old CMS. We can choose to auto publish the html content of an
> {{output/}} folder, or to have a bot build the site using
> [Pelican|https://github.com/getpelican/pelican] from a {{content/}} folder.
> The goal of this issue is to explore how this can be done for
> [http://lucene.apache.org|http://lucene.apache.org/] by, by creating a new
> git repo {{lucene-site}}, copy over the site from svn, see if it can be
> "Pelicanized" easily and then test staging. Benefits are that more people
> will be able to edit the web site and we can take PRs from the public (with
> GitHub preview of pages).
> Non-goals:
> * Create a new web site or a new graphic design
> * Change from Markdown to Asciidoc
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
