Split View not working with PHP code

(Note: "<<>>" below means new patragraph.) Yes indeed, Nancy. That is a very nice and comprehensive article to which you have pointed me. I actually bumped into it last night; but all the Windows stuff up front in the text got me to stop reading! So thanks. <<>> The exposition on MacOS application that comes along later in the text is very good; but it is quite a bit more complex than what I have used to produce the same successful interpretation of PHP code inside Dreamweaver that your screen shot shows (i.e., after seeing your first reply to me, I got a very similar screen shot from my effort today). <<>> So all is well here, except for communications strategy and tactics by the Adobe people. A person purchasing Dreamweaver CC today needs to have this article prominently put in their faces as an important resource since we now so often have to deal with pages that mix up PHP, Javascript and HTML. <<>> The MacOS related text should be set apart as a separate article with its own big title and META declarations to help with SEO. And I think it could be made less “geeky”, However, this is a minor point, as long as the accompanying tutorial screen shots are very detailed. As I said, this is a minor point — the article is good enough now. <<>> Cheers!

Hello Nancy! No I did not. From Mamp Pro, the following command brings up the correct page to my screen: “http://localhost:8888/wordpress_new/“. As you no doubt known my computer port 888 is used by Mamp Pro to talk to Apache. I then started Dreamweaver CC-2019, and here is the setup that produces the same screen inside Dreamweaver: Local Site Folder: /Applications/MAMP/htdocs/wordpress_new Connect using: Local/Network Server Folder: /Applications/MAMP/htdocs/wordpress_new Web URL: http://localhost:8888/wordpress_new/ At this point my only critique is that getting to the right setup is far too demanding in your clients ‘geekiness’. I found a couple of helpful Youtube videos on the detailed steps but they were poorly done, and none emphasizes that it is best to first get your usual route to PHP execution (in my case MAMP Pro etc.) working properly. (I even started PHPMyAdmin and brought up the correct database before starting up Drfeamweaver). Semi-finally, please give me an education here; because I have been wondering how the Dreamweaver development team got this software to interpret PHP code. Your question, and what I now achieved with your help, suggest to me that the Dreamweaver code relies (sort of) upon an another software (MAMP Pro, e.g.) first waking up the Apache interpreter (on the Mac) and then somehow the interpreter will respond to a ‘call’ from Dreamweaver to interpret a block of PHP code. And the setup of Dreamweaver parameters must be exactly right, in terms of following the same route that MAMP Pro laid down. Do I have this right? In any event, you saved me from the decision to more or less abandon Dreamweaver (except for occasional code structure analyses); because I am into stuff now where there is a great deal of mixture HTML and PHP within the same file. The Adobe software documenters should lay out the procedure very slowly and carefully (concrete example, step-by-step slowly), and the developers should aim to streamline to process of getting the right input parameters specified as we try to get Dreamweaver to execute PHP code. You can do a lot better (in terms of effective pedagogy) than that two relevant Youtube videos that gave me help. Cheers!