1 person found this helpful
You have a fair number of structural errors in your html that need to be addressed. HTML errors can cause all kinds of display issues. Run your page at http://validator.w3.org/nu to get a listing. The issue may clear up once the errors are fixed.
Another possibility, your browser (especially Chrome) could be caching your local page. Make sure to clear the browser cache and test again, or, in Chrome, hit F12 to turn on the developer tools, click the "Network" heading and check the box for "Disable cache" then reload (leave dev tools open) to see the page without cache.
First, do what Jon suggested.
Now, I'm not sure if you are comparing the same HTML, but I suspect you may not be working with the same code that is live. Above, you quoted the Spry script as:
In the code for your live home page, the code is:
Examining the two reveals a forward slash ("/") in front of the folder and file name, indicating a particular directory location. That could be what is throwing it off.
Finally, you do realize that Spry has been deprecated and is no longer supported?
The "structural errors" are already highlighted by DW. I'll try to correct it and see the result.
- Are you aware that there is no top navigation on tablet and mobile devices?
- On Line 58 of source code, you have a 2nd & older document type declaration that does not belong there.
- As Chris said, Spry is gone. Adobe hasn't done anything with Spry since 2006. On the web, that's an eon.
- I noticed you're using Skeleton framework. You might want to review this tutorial. https://webdesign.tutsplus.com/tutorials/building-html-page-structure-with-skeleton--cms-2 3253
Nancy & cdeatherage,
Before asking the question, cdeatherage I verified that it wasn't already answered someway in this forum. It was the case for the deprecated status of SpryEffects, but those continual changes presented as improvements are boring, so that I am not very eager to join the "movement". But in the sad perspective I should change my code anyway, what would be the best way to do it, Nancy? The most compact, standard and modular ? Via JQuery I felt like I had read it somewhere. About the forward "shas", It does not have any bad effect
cdeatherage: As for the "/", it has a bad effect only in the test version on Wampserver, so that I deleted it in all directory references in the code for testing on this Wampserver. Why this difference with the server I use www.danielpisters.be, where this forward slash has no effect? I guess not putting it is about making an absolute reference. Otherwise you have to write ".. / " etc.
. I work only for PC. Smartphone, tablet do not matter for me (for the moment at least, but I would prefer to avoid having to program for those child-toys).
. Line 58 of which file please?
. Spry is gone, perhaps, but spry is still a well working ghost, but when the ghost will be gone at its turn, I repeated my question:
Which the most compact (minimum of code), standard and modular method to replace it? Via JQuery I felt like I had read it somewhere. About the forward "slash", It does not have any bad effect with www.danielpisters.be server.
. Spry is a ghost, ok, but i'am not too reluctant to work with still working ghosts. When this ghost will disappear completely at its turn, I repeat my question: which is the most compact, standard and modular way to replace it? Via JQuery I felt like I had read it somewhere.
. I'll read building-page-structure-with-skeleton you advice me the reading, but could you give me in the meanwhile a clue to understand the defect of "my" skeleton?
2 people found this helpful
- I work on a local Wamp server. The root directory of that server is C:\wamp\www
- Branching from that root directory are my sites as in C:\wamp\www\mySite
- If I use a root relative link in mySite as in /aboutus.html, the server will look for that document in C:\wamp\www and we both know that it is in C:\wamp\www\mySite
- On the remote server, the root directory is (this varies according to the server setup) /www/
- Branching from this root directory are the documents as in /www/aboutus.html
- If I use a root relative link in /www/ as in /aboutus.html, the server will look for the document in /www/ and we both know that this is where the document is located.
To make the links work in both environments, it is better to use document relative links as in aboutus.html
As for Spry, I have a number of sites that use the framework. The only problem that I have found is related to the menubar which does not cater for touch screens. Apart from that, there is nothing wrong with using Spry and I lament its demise.
What is worrying about your site is expressed in this link, Showing results for http://www.danielpisters.be/ - Nu Html Checker. There is a need to rectify the Errors for the site to work properly. Nancy has already pointed to line 58, which is probably the worst of all of the errors.
1 person found this helpful
#1 Fix your code errors. The page is not fully loading properly until you do.
#3 More people use mobile & tablet devices now than ever before. Websites can't afford to ignroe them.
"there is nothing wrong with using Spry and I lament its demise." I too
It seems to me that I understand very well the skeleton approach such as it is presented in building-page-structure-with-skeleton.
People using smartphone and tablet, I can afford to ignore them momentarily in order to set my focus on other problems.
Spry is dead, what a pity. You don't still have answer to my question: how to replace it, by which method or component?
I am used to work according with an (at least) as so structured approach with VB6 (semi-oriented object), C++ & C#, using among others Design Patterns (from the Gang of Four). Sql-Forms 3.0 and Forms 4.5 (and more...) of Oracle, form generators working downstream from the CASE Designer, CASE Dictionary specifications and so forth. Skeleton approach seems to be rudimentary in comparison to what these case tools were offering as possibilities as well as in terms of the rigor of the approach. Web programming introduces something like a mess in comparison with all of that, hélas...
About SpryEffects.js, Adobe DW C6 integrated it still in its "framework" when I bought the product (in 2012). You learn me that it was already considered and pointed out as deprecated since 2006! Where is the logic in that?!
1 person found this helpful
Adobe removed Spry from DW in late 2012 -- 6 years after it was introduced.
I use jQuery framework instead of Spry. jQuery is in constant development by a large community of users. It's also very well documented.