GitHub user soralee opened a pull request:

    https://github.com/apache/zeppelin/pull/1984

    [HOTFIX] Change the screenshot path in custome page document

    ### What is this PR for?
    After merging [PR1804](https://github.com/apache/zeppelin/pull/1804), the 
following screenshot path is fault.
    
![image](https://cloud.githubusercontent.com/assets/8110458/22681668/cb9184c4-ed51-11e6-8984-e8811f81e9aa.png)
    
![image](https://cloud.githubusercontent.com/assets/8110458/22681769/627c22ea-ed52-11e6-9bf9-b1c2080d0a25.png)
    
    I fixed to change from absolute path to relative path.
    
    ### What type of PR is it?
    [Bug Fix | Hot Fix]
    
    ### What is the Jira issue?
    * None
    
    ### How should this be tested?
    1. Run website locally
    2. Please check [Show note list in your custom 
homepage](http://localhost:4000/manual/notebookashomepage.html#show-note-list-in-your-custom-homepage)
    
![image](https://cloud.githubusercontent.com/assets/8110458/22681862/eceef222-ed52-11e6-9ff9-9a2560c54e45.png)
    
    ### Questions:
    * Does the licenses files need update?
    * Is there breaking changes for older versions?
    * Does this needs documentation?


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/soralee/zeppelin notelist_png_path

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/zeppelin/pull/1984.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1984
    
----
commit ea6f51fb0ee224c74dab5562a3c35c938ed9fc2b
Author: soralee <sora0...@zepl.com>
Date:   2017-02-07T07:20:59Z

    change png path

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to