I wanted to try out bold cms on my localhost.
I have installed bolt cms on localhost/test (subfolder)
The admin section works great, but when I try to visit the actual site all the paths are incorrectly. Bolts tries to load different css and js files like this:
/test/public/test/public/theme/base-2016/css/theme.css
While it should be
/test/public/theme/base-2016/css/theme.css
Im sure this is easy to fix but for some reason i cant find a fix for this
Thanks in advance!
You need to put Bolt's public folder in your test folder. And put Bolt's other files one level up.
This is described in the docs where you can also find answers to other web server questions regarding Bolt.
Related
im new here..
right now im trying to make a change to to this specific website that im not the one making it, its kinda hard to understand someone else source code for a beginner like me..
what im trying to ask here is where do you usually find the main source code in this kind of web setup?
First Directory
Second Directory
Usually you can find the main source code in public_html directory.
if your using xampp than you want to create website folder in htdocs
so I've started dealing with PhalconPHP and I was going through some examples and I couldn't get the CSS working. So I downloaded this INVO sample application (https://github.com/phalcon/invo), put in the htdocs folder, loaded it in the browser and it is also missing the css, just blank text on a white screen. So there must be something wrong with my installation, any ideas what that might be?
Thanks!
Try clearing the baseUri value in app/config/config.ini from:
baseUri = /invo/
to
baseUri = /
I had an issue that looked the same as yours, then i noticed all links in the application are prefixed with "invo" as if my application would be in an "invo" subfolder, but it wasn't.
For the described situation I would say that your issue is similar to this question:
Image resources with Phalcon.
But since you have downloaded the INVO tutorial and it isn't working either I'd that's something to do within your Apache configuration. Please lead to this question: Friendly URLs in phalcon framwork is not working in Ubuntu
If none of these solutions solve your problems please let me know and provide more info.
I apologize in advance if this issue has been posted before. My problem is that my programmer had to bail on my project due to personal reasons and left me alone with a 95% finished site. I have some basic experience with ASP classic but PHP is fairly new to me.
FireFTP scr_shot: https://www.dropbox.com/s/9lws1u0sl8k93rg/fireftp_scr_shot.jpg
To shorten it up; (with Xampp installed) I have downloaded my site to the hard-drive and is now trying to get it work on 'localhost'. Immediately I sense the absence of an index-file.
Do I need to make one myself for the use in localhost? In that case, what am I looking for?
Thank you in advance.
First if you want to make an index-file of your current website, you have to put all your pages in a folder in
xampp/htdocs/
e.g
C:\Xampp\htdocs\mywebsite
then after you make a directory just visit the url like this:
localhost/mywebsite
, remember to put an index file inside the mywebsite folder.
It turned out that there was a MYSQL-database behind the site which I had no idea about or any knowledge of how to get around.
I had the database taken off and written the code into the site-files.
Afterwards everything worked as laid out above comments.
I am taking over a project from someone else that left. I'm currently trying to set up my environment. When I look at the application on the server, everything works fine. But when I download it and try to set up things locally, none of the stylesheets get read. None of the links work when I click on them either.
I think all of the paths just got thrown out of whack, but I'm not sure how to fix it. I'm using wamp and cake 2.0.
I also found a few things on cake's site that didn't seem to help .
If anybody can point me in the correct direction, I'd appreciate it.
So you have something to accept:
You forgot to copy your .htaccess file(s).
Make sure you delete the contents (leave the directories in place and delete the files) of /app/tmp/
I a new in Ubuntu and PHP frameworks. I had read the book about Yii name "Agile web application development with yii and php 5".
And this is the part of text:
Yii comes with a simple requirement checking tool. To invoke
the tool and have it verify the requirements for your installation, simply point
your browser to:
http://yourhostname/path/to/yii/requirements/index.php
I installed yii in /var/www/html/yii directory.
When I trying to open http://localhost/var/www/html/yii/requirements/index.php I get error message: Oops! This link appears to be broken.
Thanks for any help!
It depends on what your Apache server's "webroot" (localhost) is.
If your webroot is /var/www/html then el chief's answer would work:
http://localhost/yii/requirements/index.php
But your webroot is /var/www then you need to include the html part too:
http://localhost/html/yii/requirements/index.php
Basically "localhost" = /some/path (your Apache webroot), and when you are writing your URL you can just substitute the two.
So if "localhost" = /var/www instead of writing http://var/www/index.php you just write http://localhost/index.php
I hope this helps you with a higher-level understanding of what is going on.
This might help somebody, even though the question is already answered, since I had come searching here, even though the underlying issue was different.
I made the dumb mistake of extracting the downloaded yii archive into the www directory and accessing it via the http://localhost/yii/ URL, but took a while to realise that the extracted directory has the build#-release#, and once renamed to just "yii", things worked. Like I said, the problem you faced was different, but symptom was somewhat similar.
it should be http://localhost/yii/requirements/index.php
Also be aware that this book, while helpful, seems to have been rushed to publication. There's many fixes to be found on the Yii forums. I suggest you keep a tab open whenever you come across something that doesn't work or doesn't seem "right" in the book.