Jump to content


  • Content count

  • Joined

  • Last visited

About BrowserBugs

  • Rank

Users Experience

  • Experience
  • Area of Expertise
    I'm Learning

Profile Information

  • Gender
  • Location
    Surrey, UK

Recent Profile Visitors

17,214 profile views
  1. Rewrite URL in htaccess to hide certain characters

    Sorry for the delay. I'm 99% sure this is because WordPress shoves everything via index and works it out from there. Chances are then that in WordPress there is some kind of rewrite settings you could play with, I think they are your permalinks, see https://codex.wordpress.org/Using_Permalinks.
  2. Caching for Google Maps?

    My rule of thumb is if it's a 3rd party script, e.g. Google api, I just make sure the page speed is 100% excluding it and imo everything that can be done about things has been
  3. New project?

    I'm freelance mate, this project is just something I 'potter' with when I get time. I'm an avid Heroes of the Storm player, projects like this can often grow into something bigger, for example sites like Icy Veins generate huge traffic as they are actually useful, never know where a sweet idea can come from
  4. Rewrite URL in htaccess to hide certain characters

    Hey mate, In htaccess it's pretty simple, but not 100% what WordPress is doing, it routes everything via index it appears. I would hazard a guess at ... RewriteRule ^coffee/([^/]*)$ /coffee/?rid=$1 [QSA,NC] ... this would make /coffee/?rid=ABC123 display as /coffee/ABC123. You can tighten the regex to only accept number and letters etc but i'm not sure on the possible options for 'rid', see https://httpd.apache.org/docs/2.4/rewrite/intro.html. Duplicate Content Warning: Both pages would return the same page under different urls, canonical or something. WordPress Warning: I've zero experience with the magic of WordPress, this might knock its nose out of joint. Health Warning: Don't drink and drive, you'll spill your drink
  5. New project?

    I'd say find something you have an interest in. I play Marvel Contest of Champions, built a guide and team builder tool because first I would use it and second I got to work out a few bits I'd not done before. The site makes pocket change in ads but hey, was fun building it and still use it today
  6. I think people are scared of reciprocal as it was hammered by the engines as dubious, high heels exchanging links with bakers and the like, but with a real world example an official ford dealership would be linked and listed on ford.co.uk with a `Visit the Dealer's website` link, and an individual dealer linking to their official brand website would be normal too, nothing untoward is going on and Google knows this. Edit: As for where to get links, really depends on the industry, official stockist of X would get links from their suppliers as a distributor, local plumbers in an area linking to electricians and other callout services etc - even Rand at Moz has his own list of recommended professionals
  7. background-size works not trustly

    So for a simple answer with only your example code to go by its because you are missing the closing } for the #content class. I assume the rest of the page is irrelevant.
  8. Bang on mate, so long as there are reasonable grounds there's no problem.
  9. Page extensions

    Page extensions in the old way of thinking used to hold some value, it's why so many used to rewrite and serve php pages via an .html extension, essentially creating a physical page to the search engines even though it was dynamically generated. Now, the extension on the page is pretty much irrelevant imo, with search engines really only concerning themselves with urls and headers for html pages. For me I choose to drop them all together, simply down to url management and scope for changes without needing a bunch of 301 redirects. For example if I made /contact.html then it would get indexed, then I want a form so I make /contact.php and 301 the old page in. Oh, but now I want to swap to Windows and use aspx; so I make /contact.aspx and forward /contact.php there. All this would have been saved if I used /contact from the beginning, never needing to 301 ever again. Just my 2 pence worth as always
  10. If someone already has a website then they have hosting. You 'could' build the new site in their space so long as you're careful not to overwrite the live site, but it's risky for sure. I'd suggest getting some cheap space of your own to develop the new site in. If you setup the hosting under their domain you could either use a sub domain based on their domain as an alias, build the site and then migrate it to their live server once ready. Option 2 without a sub domain would be the same but instead of using a sub domain you could use your hosts file to view the new site in your browser when the rest of the world would get their current live site, this is safer as there is no chance of a duplicate site (e.g. both sub and main urls are being indexed). Either way you cut it you will need development space or be extremely careful in their live hosting. As many point out there's some dirt cheap hosting out there ideal for developing multi-sites, e.g. TSO has host 3 sites for £4.58 per month, just cancel the hosting when you're done.
  11. Front end before or after backend?

    Back end first if complex. Generally the nips and tucks behind the scenes will dictate the UI requirments, at the end of the day it needs to function first and look pretty / ux later.
  12. Not a wordpress site

    Most security flaws will be with regards to variables your page accepts. Security attempts are made by trying to manipulate the variables, either via the url parameters or posted form fields with something else. I'm 99% sure PHP only listens to the variables given however this is where validation, sanitation and checks are vital. It's also down to selecting the right choice for each variable with php, $_GET (Requests data from a specified resource), $_POST (Submits data to be processed to a specified resource) or $_REQUEST (Could be $_GET, $_POST or $_COOKIE data - more open to manipulation) are the three options. An example of $_REQUEST is both /yourpage.php?name=Jim and a form input <input type="text" value="Jim" name="name"> posted would work, but if you were expecting a form input call it by name using $_POST. With a contact form the process should be $_POST['name'], then validate the content, in the case of a name you could validated to exclude anything not used for someones name like @, ?, etc. Final step is sanitise, so if storing it escape the string and use prepared statements. With the validation step you can get really creative, the idea being regular people inputting regular stuff sail through and anyone trying to manipulate your php gets caught in the validation steps.
  13. The end of the 'listicle'?

    I think i'm "10 best" blind these days, like google ads when they first started appearing people looked, now it's just white noise
  14. What is your preferred way of building Websites?

    The one thing I have learned is to try and gauge client commitment from as early as possible in the planning stage. Often they will want 'gallery', 'blog' or 'showcase' sections yet once complete and the site is live they either lose interest or are too busy to keep it up-to-date ... and if not kept up to date these sections serve as a thorn in their side rather than the goal of "feature rich quality content". It's better to hire a writer to create some timeless copy and run a static site. How I tend to develop sites for my clients is to assume everything is static e.g. nice content about their service etc. Then for things like price from, testimonials, opening hours, adding a showcase and other things like that would be controlled from a simple CMS, essentially form to database which i scratch write (or use pre written modules of my own) depending on requirements. With this approach rather than letting them have WYSIWYG gives you as the designer more control over the overall look, you can add validations before publishing e.g. everything must have a title and description etc, all this combined helps keep the quality of the site high. Here's an example, one of my clients is a tuning company with a showcase controlled by simple forms to database. When they input the starting power and torque then their tuned power and torque we now use the data to form charts. It's this sort of thing I love to build in, their showcases are feature rich and generate leads of people wanting similar, all from a minimal CMS.
  15. They have their uses, their benefits although marginal offer visitors an index to the site and search engines a clearer picture to the structure of your site, coupled with breadcrumbs it makes the search engines job easier to apply site wide and section scope terms, the parent and sibling structure they tend to like. HTML site maps have no negative effects if made correctly, so a safe bet to include one. Instead of a site map I tend to treat them as the index of a book. In the instance of xml sitemaps these once connected with Google search console are integral to understanding what's you've requested to be indexed vs Googles actual index count. I've seen many a web master assume it's just to 'make google index these pages' rather than to spot possible problems, grave mistake, if Google has 3412 indexed pages and your xml map says there should be 256 then alarm bells should be ringing.