Hey guys, I'm new to template editting. I'm trying to remove a table from the Amazon's WebStore template so i can start designing my own.
Anyone out there know how I can go about hiding/disabling/removing/bypassing it?
use jquery, include the jquery.js into the store via either site wide or per page custom script area.
and slowly find your way through their html chunk. include id if necessary and do any manipulation there :)
note, if possible try to use their html widgets as much as possible and use their id as much as possible so you don't get any weird bugs.
if you need help, please put the html chunk here and i think anybody in this site will be more than willing to help you sieve through it via the magical jquery.
Related
I'm currently working on a simple scroll website with nothing really difficult (I could almost use plain html/css/javascript but it's a bit of practicing and I will maybe add a blog). And as it is simple I was wondering how to do it properly with Django.
So here is my question, I have a homepage template that is actually the website and I don't really get how I split my different part in different apps.
For exemple I have a contact form, do I need to split it in another app and then include it in the basic template ? I want to add a galery with image in a database, do I create an app for that ?
And the other question that goes along is how do I code an app that is not returning httpresponse but just html to put it in another template and do I still need views ? I would like to do a bit like a standard form in django where you do :
form.as_p or form.as_table
so maybe:
galery.as_slideshow
So my questions are quite novice and open but someone could give me some reading to get going, I would be really happy !
This is a question a lot of people struggle with and it seems like there are a lot of varying opinions out there.
I've found that the best way to really determine the appropriate answer for each case is to really distill the feature into individual requirements and group them by feature sets while keeping an eye out for additional uses outside of the project actively being worked on.
There is nothing which says you can't build your project to include a single app containing all of the modules you would need. Doing so seems like it would make your development easier initially right? So, the question to ask then is "What if I want to reuse (insert feature set here) in another unrelated project a year from now after I've already forgotten about the weird stuff I did to make it work originally?". Asking yourself that question forces you to think about your features in a much broader context and I think 99% of the time you will realize that a "Contact Form" requirement can actually become quite complex and really should be split up into at least one separate app (i.e. User Creation, Profile Management, Email Subscription, etc...)
Here is a link to a video about this very topic which I found to be useful in figuring out my way through this question:
https://www.youtube.com/watch?v=A-S0tqpPga4
I know this is not really a hard-line answer to your question but I hope it helps point you in the right direction.
I know I am using the wrong search terms and that's why I haven't been able to suss out the answer myself. However, I cannot seem to figure out how to use the CGI module to pull what I think counts as a query string from the url.
given a url www.mysite.com/~usr/html/cgi.py/desired/path/info how would one get the desired/path/info out of the url? I understand GET and POST requests and know I can use CGI's FieldStorage class to get at that data to fill my Jinja2 templates out and such. But now I want to start routing from a landing page with different templates to select before proceeding deeper into the site. I'm hoping the context is enough to see what I'm asking because I am lost in a sea of terms that I don't know.
Even if it's just the right search term, I need something to help me out here.
Thanks for all the help on what was actually not to complicated a question. What I was looking for was a router/dispatcher that is usually handled by a framework fairly simply though an #route or something similar. Opting for a more efficient approach all I had to do was import os and then look at os.environ.get('PATH_INFO', '') for all the data I could possibly need. For anyone else following the path I was, that is how I found my way.
I'm new to ExpressionEngine and ModX, well I've barely started reading up on it and I need some encouragement before I dig dipper into learning either of them.
I've know they're both CMS utilities which allow you to create websites and manage them as wordpress would but I'd like to know if instead of building it completely from the ground up, if one can simply use a template, like one of those free HTML templates or a premium template and use one of those two CMS utilities to manage/update the content of the site.
I've looked around for some tutorials but the ones I've found only teach how to create a site from the ground up and I don't mind reading and learning as long as someone can tell me if it's possible to do what I mentioned before.
Thanks.
Yes, you can with MODx. You can use any HTML, css, javascript you want, no restrictions.
I don't know about ExpressEngine.
Yes you can use whatever HTML you like with ExpressionEngine, whether it's code you write yourself or whether it comes from a template.
I am trying to disallow certain parts of a site instead of the whole thing.
I am relatively new to this so if someone walk me through it I will appreciate it.
I know that you can Disallow: /page1.cfm from crawlers but what if I want to disallow just a part of that page such as a link or a contact form that exists on that page? Is this functionality even possible?
Based on some forums I was reading recently, the "nofollow" function is not really working anymore since the crawlers are becoming smarter. (i don't know how credible that forum was, so if anyone has a better source please share)
Any suggestions?
Don't use nofollow, you'll loose linkjuice on your page.
Robots.txt are just a hint for crawler, half of the time with disalow rules if they already have find the page they still visit it and index it.
Use .htaccess rules to ban or block the access to this pages.
Or crypt your link with a complex .js (base64_encode() + str_rot13() encoding should be enough to lost the crawler)
You can use the attribute "nofollow" in the meta tag to hide the information on the page. Google wrote that they do not pass on the links labeled "nofollow." More information about this and examples you can find here:Robots.txt tutorial and Google supportHope this helps
Suppose you are running a Django site, and have a legacy PHP forum to support and integrate into your site, since current Django forum solutions are not mature enough.
What is the best way to do this?
Currently I have a simple view, which renders a very simple template which extends my site's base template, and the content area has nothing but an <IFRAME> which holds the forum as its src. A small jQuery function is used to maximize the <IFRAME>'s height (once it finishes loading) so as to contain 100% of the forum content.
But all of this sounds pretty awkward. How would you go about this?
There are a few options. None are ideal (but mixing two platforms never is!)
Use iframes as you've suggested (bad as the address in the address bar is always that of the django page and if somebody copes a link off the forum, it will be the PHP forum, not the django holder)
Use iframes but instead of using the same src all the time, parse the URL and append the relative bit onto the src of the iframe. ie if django sees /forum/this-url, set the src to http://forum-address/this-url and make sure all your links target parent. This has the advantage of showing the correct link in the address bar at all times (rather than it always being /forum/). You'll need to hack your forum for this to work.
Proxy the content and inject it into the page properly. You'll need to pass cookies and it might get really messy but in most terms, this is a great way to integrate things because your links will always be correct. You'll need to butcher your forum theme to strip out everything outside and including the <body> tags.
Theme your forum in the same way as the Django site. This would give best performance but you might have issues if you use dynamic stuff in your django template. An option to get around this is by having the django template cache things to memcache and using php-memcache to pull them out into your forum template.
I have done both 3 and 4 in the past. I used 3 for a very simple form (so didn't have to deal with cookies and sessions as you will). I used 4 for integrating a FluxBB forum into a Wordpress install. Both PHP but it would be uber bloat to load FluxBB inside Wordpress. I cached the dynamic template things into memcache and pulled them out in the forum template.
For this, I would probably suggest going with #4. It's a pain in the arse having to maintain two themes but it's by far the fastest performing solution.
When I read the question summary I immediately thought that you would need some kind of script, which could be linked to a signal via the Dispatcher in Django, to syncronize the user database from your Django site to the forum. This would keep the authentication side of things in check - but you still need to do one of the things that Oli has suggested, to make them look the same.
Themeing will probably be the least hassle-free route, but that's not to say it will be easy!