I've made asynchronous type pages. so I want to configure GTM for a virtual pageview.
I added nothing but only Tracking ID on the GA variable config and tried to override setting of each virtual page.
However, in preview mode, the settings were not applicable at all. Is there anything I missing?
extra desc:
I realized that 'GA settings' should not be filled for the overriding and It makes some changes. but fields settings are still not working
Related
I wonder if it is possible to automatically show the GTM debug bar when loading GTM with a specific environment and/or other GTM variable?
I have set up a new environment in GTM to be used for dev/testing purposes. When setting up this environment there is a checkbox with the option to "Turn on debugging when previewing". I first thought that this did just this, but no debug bar appears by default even though I checked it and is loading GTM with the code that the environment applies. What does this do then?
I actually can get what I want, sort of, by adding the parameter gtm_debug=x to the implementation code, however this feels hacky maybe, and also causes the console to log a weird 400 error to GTM:s api domain, which doesn't feel so good...
Does anyone know how I can achieve this?
I've came across a similar (or maybe even the same) problem. I've wanted to enable the QA team to access/show the GTM debug toolbar (i.e. enable/disable it) on their behalf and without going into tag manager.
This is the solution I came up with:
https://www.googletagmanager.com/set_cookie?uiv2
&id=GTM-XXXXXXX
>m_debug=x
>m_auth=AUTH
>m_preview=env-0
&url=https%3A%2F%2Fwww.example.com%2F
(enable debug)
where "GTM-XXXXXXX" has to be replaced with your container ID and "url" is an optional parameter.
This URL sets the necessary cookies to switch GTM into debug mode and also provides a link to leave debug mode again ("Exit preview and debug mode").
https://www.googletagmanager.com/set_cookie?uiv2
&id=GTM-XXXXXXX
>m_auth=
>m_preview=
>m_debug=
(leave preview and debug mode, i.e. remove cookie)
The values for "gtm_auth" and "gtm_preview" are different per container/environment and you can find them via "Get Snippet" from the "Actions" menu of each environment on the "Environments" view ("Admin" -> "Environments"). You can also get them for the two default environments, i.e. "Live".
When setting up this environment there is a checkbox with the option
to "Turn on debugging when previewing". I first thought that this did
just this, but no debug bar appears by default even though I checked
it and is loading GTM with the code that the environment applies.
What does this do then?
"Turn on debugging when previewing" is from the "Share preview" screen. On the "Environment Configuration" screen, it says "Enable Debugging by Default" and also Google's documentation suggests what you (and me) expect:
Optional: Check Enable Debugging by Default if you need the environment to always use preview mode.
But it doesn't work for me neither. :(
The preview & debug mode relies on 3rd party cookies (i.e. cookies on www.googletagmanager.com and even if the checkbox is checked they are not set. The missing cookies are also the reason for the 400 error you were mentioning.
I'm currently experimenting and configuring the entity embed module which I have just installed recently on Drupal 8. On the configuration, I do not see a checkbox to "Rendered Entity" as an option(see screenshot below). How can I enable the option "Rendered Option" on configuration? I have browse and search everywhere but I cannot seem to find a way to enable it.
Go to /admin/structure/display-modes/view and add new view mode for your media entity.
Go to /admin/structure/media/manage/{YOUR-MEDIA-TYPE}/display and enable newly added view mode in the Custom display settings section.
Then switch to this new view mode and configure fields you want to output.
Once done you will be able to use it WYSIWYG:
Refer to D8 Media Guide on how to configure an additional view mode in case I've miss something.
UPD: Adding button settings:
My formulas in Display --> visible seem to work while I am in Preview mode. But don't work when I access a Published version of the app.
Most likely it is somehow related to permissions configuration. In Preview mode you are always Admin. By default, when you create custom Deployment you are member of Admin role, but if you made some changes to default `Deployment' configuration it can result into the issue you are observing.
I am trying to create a custom module (as a content/node type) but it's malfunctioning.
Upon creating the desired .module and .info files, I go into Adminstrator/modules and enable the module. Upon enabling this module, all I see is the adminstrator view expand itself
Compare this with the regular administrator page that renders itself while carrying out administrative tasks:
It is expected to appear in the new Content types button but it does not, and when I look back into the Modules menu, the node is not enabled, even though I enabled it and saved configuration.
There are no error reports either and I am using the official Drupal documentation to create a module as a node_example...the code for the same can be obtained at this link:
http://drupalcontrib.org/api/drupal/contributions--examples--node_example--node_example.module/7
Anybody with any inputs on what's going wrong here? Most importantly this seems to be an error present in the official documentations for creating a module as a node type!
I have an ASP.Net website running on IIS7. The developers have created a CMS in the \admin folder, which allows the website admin to create/edit/delete pages.
They have said:
"The read/write permission should be given to the user that requires login access to the admin panel, not the anonymous user that has general public access to the website. The reason for the write permission is to allow the administrator to be able to upload images and files through the CMS, and make various changes to the navigation, style sheet, etc".
Also, they have said:
"Password protect the /admin folder and assign full rights to your admin user as it needs to update data (site files) accordingly as mentioned in the Folder level section above. For certain modules to work, such as the file manager, you would need to use Basic Authentication at the Directory Security level. The FCKeditor folder also should be protected so it has the correct permissions. "
Is this approach safe? I have tried assigning full rights to the Plesk protected folder user (the \admin folder is protected through Plesk), but Plesk keeps reverting back to its default settings. I am told this is a security measure, which makes sense.
What would an alternate way of accomplishing this be without rewriting any code?
If the application needs the ability to upload then it will always need read/write permissions to the directories it is going to upload to - no amount of rewriting will change this, it's part of the basic functionality. The same applies to editing stylesheets etc.
Reverting changes you make sounds like a very bad security measure - warning you would be fine, but generally you make these changes for a reason and want them to stay.
Hay try this...
Right-click the file and select Properties.
Click on the Security tab.
Click Advanced in the lower right.
In the Advanced Security Settings window that pops up, click on the Owner tab.
Click Edit.
Click Other users or groups.
Click Advanced in the lower left corner.
Click Find Now.
Scroll through the results and double-click on your current user account.
Click OK to all of the remaining windows except the first Properties window.
Select your user account from the list up top and click Edit.
Select your user account from the list up top again and then in the pane below, check Full control under Allow, or as much control as you need.
You’ll get a security warning, click Yes.
On some files that are essential to Windows, you’ll get a “Unable to save permission changes… access is denied” warning and there’s nothing that you can do about it to the best of my knowledge.
Reconsider why you’re using Windows.