I Updated to the latest meteor version and I'm also running the latest parsley.js version my validation has stopped working it seems that
$('#create-post').parsley().options.trigger = 'change';
$('#create-post').parsley().reset();
Is not firing in meteor (on render template) but works fine in JS Fiddle - https://jsfiddle.net/grbcwa9b/
Really not sure why it's not working anymore has anyone else run into this issues
I was finally able to get to the bottom of this I had create post id twice once in my navigation and once in form this was causing the conflict
<li class="{{isActiveRoute regex='create-post'}}">
<i class="glyphicon glyphicon-plus"></i><span class="title">{{mf 'create-post' 'Create Post'}}</span>
</li>
Related
I migrate wordpress version 5.2 from host to another one using all in one wp migration plugin.
firstly I installed new wordpress on the new host with latest version
afterthat I use th plugin to import exported file from old host all thing is goes well except
social icons and some images when inspect in page I saw
<i class="fafa-facebook"></i>
and it should be <i class="fa fa-facebook"></i>
and <imgclass="review__photo-img">
and it should be <img class="review__photo-img"> so how to solve this problem
I would suggest using find and replace to correct both of these instances, the issue with this approach is that you'll need to manually identify the errors to correct.
Depending what IDE you're using this should be an relatively easy task, below is a how this can be done with VS code:
https://code.visualstudio.com/docs/editor/codebasics#_find-and-replace
Just upgraded to latest angular2 version - however I am unable to just supply a normal link as per below:
<a [routerLink]="/home">Click it</a>
or
<a routerLink="/home">Click it</a>
The error is:
{outlets:{}} has to be the last command
I don't have a need for outlets, so just want to allow for a basic normal link - changing the hyperlink to a <button> works fine, it just seems to be on the hyperlink element.
I have not been able to find anything online with someone experiencing the same issue.
It was an existing project that was upgraded to latest angular, however I have a 2 others which went via the same process and they do not have this issue.
Any ideas?
when I start meteor like this:
meteor --production
I get a blank page where my app should be and the following error shows up in my browser console:
No such function: navClassName
However if I start meteor normally like this:
meteor
My app runs without problem.
What could be the problem? Do meteor template helpers need to be loaded differently during production?
Relevant files:
client/navigation/navigation.html:
<template name="navigation">
<ul class="nav navbar-nav">
<li class="{{navClassName 'home'}}">
home
</li>
<li class="{{navClassName 'blog'}}">
Blog
</li>
</ul>
</template>
client/navigation/navigation.js:
Template.navigation.helpers({
'navClassName': function (route) {
if (Router.current()) {
return Router.current().route.options.navbarSelected.search(route) != -1 ? "active" : "";
}
}
});
Move navigation.js to the client/lib directory, or at least the Template.navigation.helpers part and fix/remove any other JavaScript that is causing errors.
I wish I could elaborate more, but this issue seems to be related to the file load order. Files in the lib directory are loaded first and moving the helpers there solved the problem for me.
A typical file structure can be found in the documentation. See the comments in the Example File Structure to learn about some of the special behaviors.
While this may work for you, finer control over dependencies can most easily be achieved through packages, as explained in this other answer from SO. This is specially necessary for code that should be available to both client and server.
I created this simple nav bar, and everything is working great except the URLs for the links. When I click on the links, it just gives me "#" after the current page's url, so the links look great but go nowhere. So I assume that #node.Url isn't working for some reason. Any ideas?
<ul>
#{
var homeNode = Model.Content.AncestorOrSelf("Homepage");
}
#foreach (var node in homeNode.Children.Where("Visible"))
{
<li>
#node.AsDynamic().Name |
</li>
}
</ul>
This sounds like an issue directly related to the upgrade.
Assuming you took a backup of the code and database before performing the upgrade, I would recommend rolling back to the backups and updating again, being sure to follow the specific instructions supplied in the upgrade guide
The reason this was happening was because of a database error related to nested doctypes. The way I solved it was to completely reinstall Umbraco 7.2.2, and then download the dev version of the next Umbraco version. Then I had to build the dev version, in order to get the resulting umbraco.core.dll and copy it into my own /bin/ folder. After doing this, my code worked perfectly, as well as fixing a number of other errors. If anyone else is experiencing this, the steps to fix it may be found here: https://our.umbraco.org/forum/getting-started/installing-umbraco/60101-Upgrade-to-721-Document-Types-Break
I'm trying to get the Gumby.js library to work with Meteor, but cant get it to work.
I've tried both installing it manually in /client/lib folder and using 'mrt add gumby'.
The CSS part seems to work pretty fine with the grid working perfectly, but the JS modules dont work.
I'm setting a responsive Navbar just like this
<template name="nav">
<div class="row navbar centered" id="nav1">
<!-- Toggle for mobile navigation, targeting the <ul> -->
<a id="nav-toggle" class="toggle" gumby-trigger="#nav-ul" href="#"><i class="icon-menu"></i></a>
<ul id="nav-ul" class="eight columns">
<li>Quienes somos</li>
<li>Marcas</li>
<li>Servicios</li>
<li>Laboratorios</li>
<li>Contacto</li>
<li>Otros</li>
</ul>
</div>
</template>
but the menu just does not popup on mobile width. And other modules like Folders and skip dont work at all when defined.
you can see a sample here
any idea on how to get it up and running?
Not sure about the real situation, because the js files are packed in the website and it's hard for me to tell from the source code. However, there is some clue you may find useful.
I assume you want to run the js script after the template is rendered. In this case, you need to write like this.
Template.nav.rendered = function() {
// Run the js to render the dropdown or whatever.
}
This is the Meteor programming paradigm. If you simply run the js files directly, the template may not be ready when you run that part of the code. The "rendered" callback is the place you need to place some actions after this template is ready.
In addition, you can refer the official document here http://docs.meteor.com/#template_rendered