Vendor directory cannot be created while installation. #1
Comments
|
You did everything right. My bad. Thanks for pointing out this error. I deleted the symbolic link. Latest version for saaze-example is v1.3. It should work now. Thanks for letting me know. Regards, Elmar Klausmeier. |
|
Noted. I am continuing with the installation. I am using FFI so I am ignoring step 6. In step 7, this is my line. I'm including the ending array delimter Assuming that the syntax is right, this it the output for The PHP fatal error seems concerning to me. In step 4, I installed the md4c library as follows:
|
|
Hello, again my bad, sorry again. The most recent version of Simplified Saaze uses a MD4C extension by default. In your case, though, you are using FFI, which is just fine and still works. You can fix that so: In file vendor/eklausme/saaze/MarkdownContentParser.php, line 648 uncomment, comment line 649. I should make this distinction a configuration flag, but haven't so far. Haven't seen your note earlier, so I am replying quite late. Regards, Elmar Klausmeier. |
|
Alright, that worked.
Well there are quite a few misses, but it's a young project. So no complaints.
That's fine too. I face two more issues as I continued. First: after
Clicking on I then realised that there is no Ideally, the root page should already be there out of the box like in any CMS. It is then easier to tinker around and learn the software. But I am sure it's a miss. Secondly, the link to the CSS file is broken. The source for
But the style sheet is located in the |
|
Hello, all your comments are correct. Thanks. As the saaze-example should address newcomers to Simplified Saaze, it really should be easier to set up. Expect a modified version in the next weeks If you want one or more pages at the top directory, one simple approach is to create another yaml Then in In my case I use NGINX as a web-server and configure any redirects to whatever is required. I use something like this: Another approach: Use a simple The For my website I use the dynamic mode of Simplified Saaze, as I change Markdown files all the time, read: multiple times a day. Some time ago I used the static file approach. In that case you need some deployment script, which takes care of copying CSS files, images, HTML files, etc. to your web-server root. Here is an excerpt of a deployment script: As you can see, the Regards, Elmar Klausmeier. |
This actually seems a bit odd and as a workaround. And a bad design too. In the upcoming update, will it be possible to use
Understood. I should have thought of that earlier. Thanks. |
|
Hello, regarding the If you want to make Nevertheless, I should have provided an If there would be a stray The initial design done by Gilbert Pellegrom says:
I generally think that this was a pretty neat idea. For example, in wendt I make heavy use of 19 collections, i.e., yaml-files. See Example Theme for Simplified Saaze: Wendt. Thanks. Regards, Elmar Klausmeier. |
|
I am thinking about a default yaml file, having its Markdown files directly under |
Design wise, even for a multi-blog or a content website with multiple categories, it makes sense to have a home page (that is either a special landing page, or listing of all posts, or a listing of a particular blog like in your case), about page, contact page, etc. Although you can play around with the urls, it is easier to manage the entire website if the same hierarchy is maintained in the Else, I would have to consider a sub directory inside
That's a work around. Yet I tried it. This creates a problem with the urls. Setting entry route back to
I am yet to understand Saaze concept. So forgive me for my misunderstandings (if any). It should render But the build throws an error. |
|
I added a landing page to saaze-example v1.4:
Valid point. I hadn't done so, as the saaze-example was essentially just my personal blog at some former time, and I did not and still do not use a landing page. However, my personal choice should not be "enforced" to any other users, who want that, and there are many. If you re-install saaze-example, watch out to uncomment three lines in So far I did not come up with a good approach to have separate Markdown files outside of collections, i.e., that would be your I can confirm that changing |
Glad to see you think that way. I am merely thinking from a general product design perspective. I am not specially looking at it as "this is what I want, so let's implement it", although a part of what I what happens to be the general design seen itself.
Yes, I am reinstalling and testing again. However, the directory |
|
Hmm. I cannot reproduce this. This is what I get: |
|
Sorry. My syntax was wrong. I was trying to name the project locally with the same command and I entered the command. instead of I will do the rest of the testing the coming week and update. Thanks. |
|
I reinstalled SS and built it with Now, I remember your earlier comment that the css file should be copied to the web server's document root. In my case (and in most cases), this is not possible because there are other projects too, which is why there is the concept called base url. This is there in SS too, as I see it from I see from the documentation that it is an environment variable. Just for clarity: is this the Linux environment variable or PHP. Knowing that would help me understand how to change it. That said, from the design perspective, the |
|
Your comments are correct. saaze-example was meant to be a an example. It does not show all possibilities. For example, it shows no MathJax, no galleries, etc. If you use, e.g., saaze-paternoster, you will see that there I indeed use My own blog also uses By the way, that was one of the reason to create Simplified Saaze, as the original Saaze from Gilbert Pellegrom did not have this functionality. See Saaze generates static files for root-directory only, relative positioning would be preferred #1 . Some examples: <?php $NO_CSS = getenv('NO_CSS') ? true : false; ?>
<?php if (isset($entry['prismjs']) && ! $NO_CSS) { ?>
<link href="<?=$rbase?>/jscss/prism.css" rel=stylesheet>
<?php } ?>
...
<div id=hamitems> <!-- (C) MENU ITEMS -->
<a href="<?= $rbase ?>/blog">Blog</a>
<a href="<?= $rbase ?>/aux/about">About</a>
<a href="<?= $rbase ?>/music" aria-label="Music"> ...So, You can go even further, you can use And for your question: Yes, |
|
Alright. |
Just trying out the software. I am installing the software following the steps in the documentation and I am getting an error while creating a project.
Note that I install composer from the Debian apt repository.
When I list the files inside the installation directory, I see that the
vendordirectory point to a directory in my home, which does not exist.What am I doing wrong?
The text was updated successfully, but these errors were encountered: