What does this mean, and what is the best way of dealing with it.
Here is the short version of what happened:
- Built a page in GUI, and custom coded some elements
- Some bugs occurred (large number of elements on page) with show/hide and expand/collapse functions.
- I decided to move to a slideshow instead to avoid this business of the bug
- Now when I deleted all the of the page code and rewrote it, I get this error. What’s the best thing to do here?
Hey!
Share a link here to the page where it happens. I think we should examine it with devs, looks like bug actually
I went ahead and solved this problem by removing that element. Sorry, page is due in 2 hours. I am just going to hope whatever is leftover in .js files behind is not going to cause any hiccups, so far, so good.
This is the trail-follow up page and results from this impossible post, I just had to report what went wrong for now and find a workaround given my deadline, until we/yall can do a deep dive if necessary in the future for this stuff.
I generally realized SLIDESHOWS and avoiding needless hidden items and as such extra SHOW commands greatly helps with my original issue in the above URL, however, in the process of reorganizing that page, it looked like some leftover .js files remain although page code has been removed and re-added completely differently.
I changed the ID of element in question and I also changed the on-click event for it, and it would not want to work anyway, it would not become clickable. I went ahead and just decided I do not need this item as I have my tabs anyway and there is no point in clicking to go back to previous large buttons.
page in question Practice Areas | Alexander J. Houthuijzen, Attorney-at-Law under project alex-the-defender. Liran has been trying very hard to help with my issues as well. But RIGHT NOW, I managed to get passed all the issues so far on this page.