I just bought Alan Storm's new ebook, No Frills Magento Layouts, and completed all the exercises in chapters 1 and 2, but when I got to chapter 3, I was able to get the blank page by changing the 'current package name' and 'layout' in the admin panel, but after copying app/design/frontend/base/default/layout/page.xml to app/design/frontend/default/nofrills_layoutbook/layout/page.xml i was unable to get the page to render as in figure 3.3 on page 60. when viewing the listed url I still got the 'handles generated...' output as in the previous figure and without the modified layout, just a white background. I noticed that some other blocks are being rendered. Here is the entire output on the to the screen with path hints and block hints turned on:
Handles Generated For This Request:
default
STORE_default
THEME_frontend_default_nofrills_layoutbook
nofrills_booklayout_package_index
customer_logged_out
frontend/base/default/template/page/3columns.phtml
Mage_Page_Block_Html
frontend/base/default/template/page/html/head.phtml
Mage_Page_Block_Html_Head
frontend/base/default/template/page/js/cookie.phtml
Mage_Page_Block_Js_Cookie
frontend/base/default/template/page/html/notices.phtml
Mage_Page_Block_Html_Notices
frontend/base/default/template/page/html/header.phtml
Mage_Page_Block_Html_Header
Magento CommerceMagento Commerce
Default welcome msg!
frontend/base/default/template/page/template/links.phtml
Mage_Page_Block_Template_Links
frontend/base/default/template/page/switch/languages.phtml
Mage_Page_Block_Switch
frontend/base/default/template/page/html/breadcrumbs.phtml
Mage_Page_Block_Html_Breadcrumbs
frontend/base/default/template/page/html/footer.phtml
Mage_Page_Block_Html_Footer
frontend/base/default/template/page/switch/stores.phtml
Mage_Page_Block_Switch
frontend/base/default/template/page/template/links.phtml
Mage_Page_Block_Template_Links
Help Us to Keep Magento Healthy - Report All Bugs (ver. 1.10.1.1)
© 2009 Magento Enterprise Edition Demo Store. All Rights Reserved.
I'm running Enterprise 1.10.1.1 if you couldn't tell. Every other example in the book has worked flawlessly, but I'm wondering if there's a compatibility issue with this version considering that the url in figure 3.3 is 'magento1point4.2.dev/nofrills_booklayout/package/index'. Any advice would be appreciated.
I'm looking at older copies of Enterprise that I do have installed and it looks like (As part of the installation process), Magento sets the default theme to enterprise
System -> Configuration -> Design -> Default
So, anywhere the books says default/default, try substituting default/enterprise. Alternately, try removing the enterprise value from the admin to restore default not-configured system behavior.
Related
I've installed a theme (that i bought) that's mainly made with Elementor.
Since I've been running into some issues with customizing this theme, (and still refuse to also pay money for Elementor Pro) I decided it would be easier to create a custom template myself.
I have done this before when I used a custom theme I made myself from scratch (I thought I was saving myself some time this time around...).
So my problem: I saved this template called page-home.php to my Child theme (that I made of the purchased Theme) in a folder called page templates.
It is not showing in the drop down menu when creating a new page.
I then just copied it to the main theme, activated that...and still not showing.
Is this because the Theme is using a page builder like Elementor?
Or do you think the creator of the theme somehow disabled this option?
Thanks in advance for any help.
As far as I know Elementor ignores the most of the standard theme file. It does so i.e. with the header.php for sure. The question is what do you want to put in a theme file what you couldn't do with Elementor. Have a look at the
"Hello Theme" https://github.com/elementor/elementor/issues/14283 - it's a plain theme.
If you don't want to pay for Pro, I recommand the plugin "Elementor – Header, Footer & Blocks Template" (and for better editor handling: "Flexible Elementor Panel")
In Gitlab, I've been able to render an Entity Relationship Diagram with Mermaid in a Markdown file as specified here.
This is the Markdown I used:
```mermaid
erDiagram
CUSTOMER }|..|{ DELIVERY-ADDRESS : has
CUSTOMER ||--o{ ORDER : places
CUSTOMER ||--o{ INVOICE : "liable for"
DELIVERY-ADDRESS ||--o{ ORDER : receives
INVOICE ||--|{ ORDER : covers
ORDER ||--|{ ORDER-ITEM : includes
PRODUCT-CATEGORY ||--|{ PRODUCT : contains
PRODUCT ||--o{ ORDER-ITEM : "ordered in"
```
The mermaid interactive editor provides an example of configuration:
{
"theme": "default"
}
But I don't know where to locate that configuration information. I've tried putting it in the same directory, in a file called config.json or mermaid-config.json, but neither of those have worked. I also tried including it in the Markdown which defined the diagram, which only caused it to render incorrectly. Is there a way to specify the theme or other CSS elements for Gitlab?
Just tried it out and it worked
```mermaid
%%{init: { 'theme':'dark', 'sequence': {'useMaxWidth':false} } }%%
sequenceDiagram
alice ->> mark: Sent a flower
```
Edit: If you are using a recent enough version of GitLab (possibly 13.9.0 from February, 2021, which changes the shipped version of Mermaid from 8.5.2 to 8.9.0) you can use directives, as mentioned in the other answers:
```mermaid
%%{init: { 'logLevel': 'debug', 'theme': 'dark' } }%%
graph LR
%%{config: { 'fontFamily': 'Menlo', 'fontSize': 18, 'fontWeight': 400} }%%
A-->B
```
Note that Mermaid seems to be sensitive to newlines here. If I add a blank line between graph LR and the following %%{config line I get a syntax error.
Original answer for older versions of GitLab:
I don't believe you can, unless you want to self-host and modify the GitLab source code.
The Mermaid.js configuration in GitLab is largely hard-coded. It looks like it uses the neutral theme by default and switches to the dark theme if
the user is using dark or solarizedDark as their web IDE theme, and
if the user is on the IDE web page.
Unfortunately current GitLab uses mermaidjs version 8.5.2 as per merge request
From mermaid 8.6 onward you should be able to use directives to set the theme and/or other settings without touching the hard coded css. For example:
%%{init: { 'theme': 'forest' } }%%
erDiagram
...
I'm afraid we have to wait a little longer, until GitLab updates to this version. You can check in the meantime mermaids doc on the matter. You can includes this already in your markdown, as the %% is interpreted as comments and will not show up in the rendering. But when GitLab makes the move, your pages should immediately update.
I'm using an outdated Spotfire version (7.02) on a client and got stuck while trying to use an <iframe> element inside a Text Area.
This is the code that I used:
<iframe src="http://my.address.here.com" STYLE='width:90%; height:90%;'>
For some reason, instead of embedding the page in the dashboard, it just shows a blank space in the Text Area and automatically opens a new window/tab on my default browser with the address inside the src.
Spotfire 7.02
I tried the same code on Spotfire 7.11 and it worked perfectly.
Spotfire 7.11
Diving deeper in my research, I've found out that Spotfire 7.02 uses Internet Explorer 7 display engine, while 7.11 uses Chromium 60.
Even with Internet Explorer 7, it should be possible to use the without any issues.
Is there any way to check the display engine configurations for Spotfire 7.02 or even (long shot here) updating "just" the display engine for it?
Thank you very much
I've got a multilanguage ModX site. And noticed that when changing languages, it displays a different logo. WHat I need to do is to setup same logo for both languages. Basically:
English side showing: logo.png
Other language side showing: logo-new.png
I don't want to replace logo-new.png file with the correct image file on server in case another part of the site uses that file. So I'm left with actually editing the site header to show the correct logo.
When I go to ModX's site template, I see this code for the header:
<img src="[[++site_logo_img]]" itemprop="logo" class="site-logo">
So my question would be, where do I go to edit the ++site_logo_img value?
For web context try to look in system settings, for other contexts in context settings - https://rtfm.modx.com/revolution/2.x/administering-your-site/contexts
[[++site_logo_img]]
This is a MODX setting, these can be found in settings or in context settings.
Lets say you need a different logo for 2 MODX contexts, you can set a site_logo_img different setting in each context.
I am currently developing a site which is not supposed to expose its developer magento platform(Sorry about that ).
I thought the wappalyzer(Mozila addon),GTmetrix site is finding the cms names by its html format but when i saw a empty white page with that tools it still shows me like am using Magento(there is nothing in the source view - its white page), so now how they are finding that am using magento. Any idea about hw they are working? I checked headers but there nothing specially mentioned as magento. Same goes with wordpress/joomla - simply wappalyzer(Mozila addon),GTmetrix finds the site platform even there is no html source.
So I guess something with in header(i might missing something) or what it can be? please advice. Attached screenshot of it.
Thanks in advance
You can view Wappalyzer's source code: (Ctrl+F Magento):
https://github.com/ElbertF/Wappalyzer/blob/master/share/js/apps.js
Most likely Wappalyzer picked up on the "Mage" JavaScript variable. You can see this by clicking the DOM tab in Firebug.
They are finding it using the words like mage,varien,magento. If it finds any of these words inside css/js file class,#id,inside comment then it found it as magento.
Also gtmetrix does one more step , like it is checking the css/js url path - if it fins the url like skin/frontend then it says it as magento.
Dont forget cookies...
I use FireBugs. Go to main menu -> Cookies
There is frontend in cookies.