111–120 of 159 posts
Earlier quoted context omitted.
"A lot" lol.
What's that supposed to mean? They maintain MOST of it.
Earlier quoted context omitted.
Ok, as someone who's battled with this... feature... of WP I am super curious as to the very good reason for storing the domain in the DB. Why couldn't links be relative (no need to know the domain), or set only as a sitewide variable in wp-config.php? edit: and just discovered the 'guid' column on the posts table is hardcoded as the URL of the post -- the domain you're on at the time you create the content + the pos…
Because of this: 1) Users want to be able to update site-name (etc) from the admin interface. 2) We therefore need to store it somewhere. 3) We have a database! The alternatives are: - Storing in wp-config.php (which is also done...), but then it's not user-editable from the admin interface. - Storing in a INI or JSON or similar document, which has only marginal if any benefits over storing in the database. For deplo…
Not as easy as you make it sound.
Earlier quoted context omitted.
It also works because customers have heard of it and believe that they can edit the sites themselves (in spite of your warnings), so it's much easier to sell. "We'll just put you on WordPress!". Done. Of course, they never figure out how to edit the site, because the WYSIWYG editor is anything but, and even the text editor "enhances" the html you type in inexplicably. They don't know the difference between a post and…
> Of course, they never figure out how to edit the site, because the WYSIWYG editor is anything but, and even the text editor "enhances" the html you type in inexplicably. That hasn't been my experience with tens of sites and tons of clients I've known. Simple, non IT people, can edit the sites and change content VERY easily. Oh, and of course MILLIONS of people edit their own posts for their blogs in the hosted word…
Earlier quoted context omitted.
Because of this: 1) Users want to be able to update site-name (etc) from the admin interface. 2) We therefore need to store it somewhere. 3) We have a database! The alternatives are: - Storing in wp-config.php (which is also done...), but then it's not user-editable from the admin interface. - Storing in a INI or JSON or similar document, which has only marginal if any benefits over storing in the database. For deplo…
Certainly there are configuration options that are appropriate to store in the database, but I'm trying to understand why domain is one of them. The site knows what domain it is on by virtue of being hosted on that domain. Storing the domain in the DB may be reasonable if it's done once, but WP does it multiple times: WP_SITEURL ("the address where your WordPress core files reside"), WP_HOME ("the address you want pe…
Earlier quoted context omitted.
First, I should mention that I'm glad to see this dismissive and negative comment voted to the top. I was starting to worry that HN was losing its edge. Next, you mention: > Yet it's a blazing success in the CMS space, because of 3 things that are insanely overlooked by other CMS developers : - Ease of installation - It runs on a minimal PHP/Apache/Mysql setup (cheap hosting) - It has a great backward compatibly, unl…
This comes from developer and client feedback in poll after poll of WordPress users and developers. If you've never experienced anything else, of course what you have is always the best.
Earlier quoted context omitted.
Because of this: 1) Users want to be able to update site-name (etc) from the admin interface. 2) We therefore need to store it somewhere. 3) We have a database! The alternatives are: - Storing in wp-config.php (which is also done...), but then it's not user-editable from the admin interface. - Storing in a INI or JSON or similar document, which has only marginal if any benefits over storing in the database. For deplo…
Certainly there are configuration options that are appropriate to store in the database, but I'm trying to understand why domain is one of them. The site knows what domain it is on by virtue of being hosted on that domain. Storing the domain in the DB may be reasonable if it's done once, but WP does it multiple times: WP_SITEURL ("the address where your WordPress core files reside"), WP_HOME ("the address you want pe…
Any plans for Sensei plugin? My business depends on it and I am a little scared…
I'm fascinated by Wordpress success. It's an horrible peace of software, with horrible PHP code 4.x style, a db schema only a beginner could have come up with and an ecosystem with a lot of trash(not even talking about the admin which is hideous ). Yet it's a blazing success in the CMS space, because of 3 things that are insanely overlooked by other CMS developers : - Ease of installation - It runs on a minimal PHP/A…
First, I should mention that I'm glad to see this dismissive and negative comment voted to the top. I was starting to worry that HN was losing its edge. Next, you mention: > Yet it's a blazing success in the CMS space, because of 3 things that are insanely overlooked by other CMS developers : - Ease of installation - It runs on a minimal PHP/Apache/Mysql setup (cheap hosting) - It has a great backward compatibly, unl…
I'm fascinated by Wordpress success. It's an horrible peace of software, with horrible PHP code 4.x style, a db schema only a beginner could have come up with and an ecosystem with a lot of trash(not even talking about the admin which is hideous ). Yet it's a blazing success in the CMS space, because of 3 things that are insanely overlooked by other CMS developers : - Ease of installation - It runs on a minimal PHP/A…
> It's an horrible peace of software, with horrible PHP code 4.x style, a db schema only a beginner could have come up with and an ecosystem with a lot of trash [...] I must disagree with these statements. Although it is not the most elegant one I've seen, using the word "horrible" is simply out of place. Have you ever built some sites with it? Do you realize that WordPress is developed in open source with many talen…