I have a website that is running on Typo3 CMS, this was all setup by our developer, problem is he doesn't work for us anymore, all I want to do is change the url of our company logo located at the header section, I have basic knowledge of HTML and CSS, I manage to move things around in the backend, but I don't know how to change the url of our logo.
It's possible that your developer has set it in:
Typoscript (e.g. PAGE TS)
template-File (index.html in /filedmin or fileadmin/templates)
As Content Element (at the top of the Tree)
CSS
A Mix of all of the Possibilities...
Perhaps a solution:
Type the current url of the Image in the Searchbox at Top of Backend.
Another Way to find out is via Firebug (Firefox).
Related
I am trying to simply edit the format (float from left to center and remove two column layout into one column) of my about page on my Shopify site.
I have edited the html of the page directly using chrome dev tools (to confirm what I am doing is going to make the page look like I want it to).
My issue is that Shopify has a specific global section in the admin where you can edit just the content of the about page. Unfortunately, I cannot seem to find anything on that page that allows me to edit the pages code directly.
And when I look at the theme code for the main site, I cannot find any .liquid files that seem to be related to the about page.
Anybody with Shopify coding experience able to point me in the right direction?
Just finished learning Vuejs and after visiting a few websites that use Vuejs like;
a) https://coderstape.com
b) https://www.thenetninja.co.uk
c) https://laracasts.com
I noticed that by navigating around the websites we by clicking on navbar links and some other links then the pages refresh and I haven't been able to find out the reason online. Could someone kindly explain what's happening in that? Doesn't it go against the purpose of SPA?
For example the last site you specified: https://laracasts.com.
On its main page there is a white button "BROWSE COURSES". If you open Chrome DevTools panel(look at the picture with explanations), go to tab "Networks" (1) and then click on this white button, you can see GET request to "series?curated" (2). If you open its details, you can see that as response, new page is received in the form of an HTML code (3), not JSON for example, as is usually the case in SPA.
Also, if you look at what programming language is used on this site, for example, using service https://whatcms.org/?s=laracasts.com, you can see that this is a PHP, namely Laravel.
From all this, I can make the assumption that they use Vue.js only partially, maybe in several components, but the site navigation itself is presented in the form of traditional static pages, which is why the page reloads.
Also, for example, if you take a look at this website https://www.spendesk.com/, you can see that they use Vue.js+Nuxt.js, as well as Node.js, as indicated by service whatcms.org, and if you try to navigate to various pages on this site, you will see no page loading. I can say that this site is a true SPA in the form in which you mean it.
I heard that you can do a SPA with a Laravel backend, but I think that's another story.
I want to manage internal contextual link building in my articles, but somewhat in a well-managed and easier way. It is a pain to change all the link URLs in a text if we change a URL of a page which is linked to many pages in their content.
You shouldn't need to change them if you used the content picker to select the page you are linking to because it inserts a URL in the format {localLink:####} where ### is the id of the document the link is pointing to.
This is then parsed and replaced with the correct and current URL when the document is rendered, so it is always current and correct.
I am currently able to popup a modal window in DNN with dnnModal.show(Url, ...);.
When I view the Url (a page within the DNN website) as a separate page, everything looks as expected (all framework and custom CSS styles apply). When I view the Url in that popup window, all the CSS is gone.
I think the fact that the Url can be anything (even outside the domain) may answer why we lose the "local" CSS. Is there a way to "retain" the website's skin on what shows up on the popup if the Url is within the site?
As an aside question, is there a proper way to load a DNN module on a popup - not the Url as above (because that is actually the Url of the DNN page that the module was put on)? If possible, that might take care of the missing CSS problem.
You might want to take a look at the way &popup=true works in DNN6/7. If you pass &popUp=true as a querystring parameter (use ? if it is the first) DNN will load the popup.ascx skin from your SKINS folder, if you don't have a popup skin defined in your skin folder, it will use the default dnn one, I believe in darkknight/popup.ascx
You can then define what popup.ascx consists of
I was wondering whether exists any dashlet which allows you to explore a site's document library. As far as I know doesn't exist such dashlet out of the box, there only exists the "Site Content" dashlet but it is slightly limited.
I have been searching around and "googling" and I found these useful resources that could be useful as a starting point if I had to create my own:
http://ecmarchitect.com/archives/2012/05/08/1592
http://code.google.com/p/fme-alfresco-extensions/wiki/GalleryPlusDashlet2
Do somebody know more dashlets/resources targeting this issue? Any suggestion?
As a temporary solution, I'm also thinking in the possibility of taking advantage of the "Web View" dashlet, by configuring in it such URL that retrieves the documentlist region/component in the documentlibrary page. For example:, share/page/components/documentlibrary/documentlist or share/page/site/{site}/documentlibrary?region=documentlist. Maybe it is crazy or what I'm saying doesn't make any sense, but it is just an idea.
Another idea that have just came to my mind is the option of creating a custom Surf/Share page which includes the component/webscript that implements the explorer of the document library, specifically the documentlist component. Then configure the "Web View" dashlet giving the URL that points to the custom page created. Would it make sense?
Thanks in advance.
You are going to see a couple of site visualization and navigation dashlets on Alfresco Visualization Tools available on https://github.com/bhagyas/alfresco-visualization-tools. The project is still at it's initial phase, but you will find interesting snippets of code used to retrieve the document library content trees within the dashlets.
The project was presented by me at Alfresco DevCon in Berlin just a week ago to bring interactive navigation and content analytics. If interested, you can find the slides at the lightening talk slides in the DevCon 2012 site at Alfresco.
Cheers! =)
Hi I've done exactly the same, it was not really needed for a Dashlet but for to embed the documentlibrary of a site in an iframe for another site.
So what I did was indeed create a new page template embedded-documentlibrary.
I've copied first the following files and renamed them:
site-data/pages/documentlibrary.xml
site-data/template-instances/documentlibrary.xml
site-webscripts/org/alfresco/documentlibrary.ftl
If you rename file 3 or put it in another folder, you need to check the paths in file 1 & 2.
So to make only the documentlibrary appear instead of everyting I just removed everything in file 3 within the <div id="alf-hd"> tag.
If you remove the tag, the document-tree will also be removed and it gave some javascript errors. This should be fixed in the latest version, but haven't tied that.
So it's extremely easy to create your own page and instead of navigating to site/documentlibrary you just navigate to site/embedded-documentlibrary or your own name you've chosen.
And yes then you'll need to use the web-view Dashlet to show it.
The only thing you need to know is, that the links open within the iframe. So if you use the web-view Dashlet, you need to open the links in a new window.
For my situation I needed an iframe, in your case you could also just let the freemarker from your Dashlet render the components needed.
There is a document-liberary-display dashlet available in the alfresco add-on list which can be used to show all the documents from document-library on site-dashlet.
http://addons.alfresco.com/addons/document-library-display-dashlet