resolve error on starting local host

Between hugo version 0.117.0 and 0.123.3, hugo became stricter about reference paths. In particular, including '/content' as a prefix is no longer allowed. This commit updates all references to the supported format This commit fixes #111 Commit-Message-Author: Skyler Grey <[email protected]>
CollaboraOnline · Mar 4, 2024 · 5718b6a · 5718b6a
1 parent c96b594
commit 5718b6a
Show file tree

Hide file tree

Showing 2 changed files with 10 additions and 10 deletions.
diff --git a/content/post/debug-code.md b/content/post/debug-code.md
@@ -97,7 +97,7 @@ If breakpoints alone are not sufficient for debugging, you can also make use of
 
 If you are trying to debug Collabora online using VSCode then probably first you need add this file in your .vscode code folder.
 
-* [launch.json]({{< ref "/content/snippets/darshan-launch.md" >}})
+* [launch.json]({{< ref "/snippets/darshan-launch.md" >}})
 * Note:
     * Inside launch file make sure url path will be same path as shown in terminal after `make run`.
     * Please replace the variable ${Your-Work-Directory} with your collabora project directory path.
@@ -106,11 +106,11 @@ If you are trying to debug Collabora online using VSCode then probably first you
 
 1. Do `make run`.
 
-1. First put break points in files where you want to see the values or action to be carried out after some events.
+2. First put break points in files where you want to see the values or action to be carried out after some events.
 
-1. Click on Run and Debug Icon :- You can find this icon in left side of your IDE.
+3. Click on Run and Debug Icon :- You can find this icon in left side of your IDE.
 
-1. Click on document type that you want to open and debug. For an example choose `writer`. It will then launch the document in browser.
+4. Click on document type that you want to open and debug. For an example choose `writer`. It will then launch the document in browser.
 
 {{< figure src="/images/run-and-debug.png" alt="Run And Debug Option">}}
 

diff --git a/content/post/ide.md b/content/post/ide.md
@@ -35,9 +35,9 @@ Please note this is a very rough page and any contribution is very welcomed. The
 #### Easy to grab setup (Pranam)
 Thanks [Pranam](https://github.com/lpranam) for making your configurations available:
 > I use vs code let me give you config file for vs with which people can debug or whatever they want in vs code without ever leaving it:
-* [c_cpp_properties.json]({{< ref "/content/snippets/pranam-c-cpp-properties.md" >}} "Pranam's config")
-* [launch.json]({{< ref "/content/snippets/pranam-launch.md" >}} "Pranam's config")
-* [tasks.json]({{< ref "/content/snippets/pranam-tasks.md" >}} "Pranam's config")
+* [c_cpp_properties.json]({{< ref "/snippets/pranam-c-cpp-properties.md" >}} "Pranam's config")
+* [launch.json]({{< ref "/snippets/pranam-launch.md" >}} "Pranam's config")
+* [tasks.json]({{< ref "/snippets/pranam-tasks.md" >}} "Pranam's config")
 
 #### gdb
 How to attach VS Code with gdb to the Online server:
@@ -71,7 +71,7 @@ Source: Anonymous
 An example of a `launch.json` configuration from [Gokay](https://github.com/gokaysatir)
 
 The file that i use for VS Code server side debugging:
-* [launch.json]({{< ref "/content/snippets/gokay-launch.md" >}} "Gokay's config")
+* [launch.json]({{< ref "/snippets/gokay-launch.md" >}} "Gokay's config")
 
 Source: [Gokay](https://github.com/gokaysatir)
 
@@ -100,7 +100,7 @@ https://wiki.documentfoundation.org/Development/Vim has some vim tips, navigatin
 Source: [Miklos](https://github.com/vmiklos)
 
 #### Ashod's .vimrc
-Thanks [Ash](https://github.com/Ashod) for making your configurations available: [.vimrc]({{< ref "/content/snippets/ash-vimrc.md" >}} "Ashod's .vimrc")
+Thanks [Ash](https://github.com/Ashod) for making your configurations available: [.vimrc]({{< ref "/snippets/ash-vimrc.md" >}} "Ashod's .vimrc")
 > I use Vim in the terminal (a lot) and I use Vim addon in VSCode. Always customize the colors, behavior of searching, highlighting, etc. for best experience. Also, add shortcuts for common actions (e.g. highlighting multiple words in different colors is very useful when reading logs or complex code with many variables, use F2, F3, etc. to highlight different words in different colors for readability).
 
 
@@ -148,7 +148,7 @@ Android Studio debugger for gdb users gdb commands, and their AS equivalent:
 
 I find it impossible to remember those keystrokes if I don't use them for 2 weeks :)
 
-source: [IRC]({{< ref "/content/post/communicate.md" >}} "Communicate page")
+source: [IRC]({{< ref "/post/communicate.md" >}} "Communicate page")
 
 
 ## Additional info